HR integration guide
Deel + UbiGrowth workflows
Deel is a global employment platform covering contractors, EOR employment, and international payroll. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make Deel part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a HR workflow around Deel with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Worker, Contract, Invoice, Payment, Entity, Compliance Document, and Time Off. Deel's primary object is the Contract, not the person: the same worker can hold several contracts across entities and countries, each with its own compliance position.
Deel is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
HR systems hold the most sensitive data in the company and are usually the least connected, for good reason. Anything reading Deel is reading personal data, and the default answer to a casual integration request should be no.
That caution has a cost, though. People-operations work is full of repetitive coordination — onboarding checklists, access requests, candidate scheduling, document collection — that stays manual because the systems that could automate it are the ones nobody wants to connect broadly.
You're likely here because
- Onboarding and offboarding run on a manual checklist
- Candidate or employee coordination consumes disproportionate time
- People data cannot be connected without a privacy review nobody has scheduled
Record model
What a Deel integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are Deel's.
Identity and matching
Deel's primary object is the Contract, not the person: the same worker can hold several contracts across entities and countries, each with its own compliance position.
Start here
Read Contracts with expiring compliance documents and route the renewal before the worker is blocked from being paid, since the block is enforced per entity and surfaces only at the payment run.
What this will not do
It will not standardise global employment. The variation between countries is real; the integration surfaces what each contract needs.
The constraint to plan around
Employment rules differ per country and Deel enforces them per entity, so a workflow that treats all workers alike produces actions that are invalid in some jurisdictions.
Build notes
What you actually have to reason about in Deel.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| contract id | the primary object; one worker can hold several across entities and countries |
| contract type | EOR, contractor, or direct employee, each with different rules |
| compliance document status | expiry blocks payment, enforced per entity |
| entity / country | decides which employment rules apply |
| invoice / payment cycle | the timing that makes a compliance gap urgent |
Authentication
OAuth or API token with scopes per resource, organisation-scoped. Worker personal data access should be minimised to the fields the workflow needs, given the jurisdictions involved.
Events and delivery
Webhooks cover contract and payment lifecycle events. Compliance expiry is the event worth acting on before it blocks a payment run.
Workflow
How the Deel workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Complete the privacy review
The data-protection assessment happens before the connection exists, and defines what is in and out of scope.
Step 02
Connect at the narrowest scope
Only the Deel fields the named workflow requires are connected, with sensitive categories excluded by explicit decision.
Step 03
Coordinate, do not decide
The workflow tracks tasks, sends reminders, and schedules, while every decision affecting an individual stays with a person.
Step 04
Surface status without exposing detail
Progress is visible to the people who need it without opening the underlying personal records more widely than the workflow requires.
Design decisions
The HR decisions this connection forces.
Each of these has to be settled before the Deel workflow is allowed to write anything.
Step 01
Scope to one workflow, not to the system
Connect Deel for a specific workflow with the narrowest access that supports it. Employee data should never be connected broadly because it might be useful later.
Step 02
Exclude sensitive categories deliberately
Compensation, health, performance, and disciplinary data should be excluded by explicit decision rather than by assuming a scope will not reach them.
Implementation path
How to implement the Deel workflow.
- 01
Complete the privacy and data-protection review before connecting anything; this is a prerequisite, not a follow-up task.
- 02
Pick one workflow — coordination, scheduling, or status — and scope the Deel connection to exactly what it needs.
- 03
Document which data categories are explicitly excluded and confirm the scope cannot reach them.
- 04
Once expiry routing works, add onboarding-time tracking per country so the hiring plan reflects real lead times.
Governance
Controls that matter.
Control 01
Employment decisions stay with people. Automation coordinates and prepares; it does not evaluate or decide.
Control 02
Access is scoped to a named workflow, reviewed on a schedule, and revoked when the workflow ends.
Control 03
Compensation, health, performance, and disciplinary data are excluded unless there is a specific, reviewed reason to include them.
Failure modes
How a Deel integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
A worker is blocked from payment unexpectedly.
Cause
A compliance document expired and the block surfaces only at the payment run.
Fix
Monitor document expiry ahead of the cycle rather than reacting to the block.
Symptom 02
A contract change is rejected in one country and accepted in another.
Cause
Employment rules differ per entity and Deel enforces them.
Fix
Branch on entity and contract type rather than applying one rule set.
Symptom 03
A worker appears several times in reporting.
Cause
They hold several contracts across entities.
Fix
Report at contract level and aggregate to person deliberately.
What changes at scale
Volume scales with contractor count. Compliance document expiry is date-driven, so a scheduled check suits it better than event handling.
Examples
What a working Deel workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Global workforce workflows
With Deel connected at a narrow scope, a coordination workflow can run from real records instead of a manually-maintained checklist.
Onboarding coordination
Tasks, access requests, and document collection are tracked as records with owners and status, so the checklist is not held in one person's head.
Limitations and considerations
What to validate before you depend on this.
- Employment rules differ per country and Deel enforces them per entity, so a workflow that treats all workers alike produces actions that are invalid in some jurisdictions.
- Contract changes affect someone's employment terms across jurisdictions with different legal requirements. A change valid in one country may be invalid in another, and the platform enforces per entity.
- When a single global employment model is assumed. The variation between countries is real and Deel exists because of it.
- Deel holds personal data. Connecting it requires a privacy and data-protection assessment before, not after, implementation.
- Employment decisions are legally regulated in most jurisdictions. Automated assistance must keep the human decision explicit and documented.
FAQ
Deel integration questions.
What records does a Deel integration actually work with?
The primary records are Worker, Contract, Invoice, Payment, Entity, Compliance Document, and Time Off. Deel's primary object is the Contract, not the person: the same worker can hold several contracts across entities and countries, each with its own compliance position.
What should the first Deel workflow be?
Read Contracts with expiring compliance documents and route the renewal before the worker is blocked from being paid, since the block is enforced per entity and surfaces only at the payment run.
What will a Deel integration not do?
It will not standardise global employment. The variation between countries is real; the integration surfaces what each contract needs.
What is the main constraint to plan around?
Employment rules differ per country and Deel enforces them per entity, so a workflow that treats all workers alike produces actions that are invalid in some jurisdictions.
What changes about a Deel integration at scale?
Volume scales with contractor count. Compliance document expiry is date-driven, so a scheduled check suits it better than event handling.
How does authentication work for Deel?
OAuth or API token with scopes per resource, organisation-scoped. Worker personal data access should be minimised to the fields the workflow needs, given the jurisdictions involved.
Does Deel support webhooks, and can they be trusted?
Webhooks cover contract and payment lifecycle events. Compliance expiry is the event worth acting on before it blocks a payment run.
What is the risk of writing to Deel?
Contract changes affect someone's employment terms across jurisdictions with different legal requirements. A change valid in one country may be invalid in another, and the platform enforces per entity.
When is connecting Deel the wrong call?
When a single global employment model is assumed. The variation between countries is real and Deel exists because of it.
What should a Deel integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require Deel to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Is it safe to connect Deel?
Only at a narrow, reviewed scope for a specific workflow, after your own privacy assessment. Employee data should not be connected broadly on the chance it becomes useful.
Can this screen or evaluate people?
No. Employment decisions stay with people. These workflows coordinate, schedule, and track — they do not evaluate individuals.
What data should be excluded?
Compensation, health, performance, and disciplinary data unless there is a specific, reviewed reason to include it. Exclusion should be an explicit decision.
How this access is governed
What ARIA is allowed to do in Deel, and who decides.
Connecting Deel is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.