Deel Integration
Send an accepted offer straight into Deel as a new hire for global payroll and onboarding — and import your Deel people into the ATS talent pool.
For teams hiring across borders, the recruiting system and the payroll system are usually run by different people in different countries — which makes the gap between "offer accepted" and "person exists in payroll" wider than anywhere else. The Deel integration closes it: connect your own Deel account once, and any hired candidate can be pushed into Deel as a direct employee with their name, email, role title, and start date — ready for Deel's own onboarding, contracts, and payroll flows to take over.
The connection is also readable: the "Import your people" action pulls your existing Deel workforce into the ATS candidate database, deduplicated by email and marked as imported — useful for internal mobility and for agencies that also run payroll for placed contractors. Deel is a trademark of its owner; Expertini ATS is an independent product that connects to your own Deel account through its official API, with your explicit sign-in.
Pe această pagină
01Connecting your Deel account
An owner or admin opens Connectors and clicks Connect on the Deel card. You approve the connection on Deel's own site — credentials never touch Expertini — and the card flips to Connected. From that moment the Screening & HRIS page gains Deel as a push target, and the auto-push rule can be switched on per organisation.
02Pushing a new hire into Deel
Pick the hired candidate from the type-ahead on the Screening & HRIS page and push. The ATS sends the fields Deel's direct-employee contract expects — first and last name, email, start date, country when known, and job title — and surfaces Deel's own response verbatim, success or failure. Deel validates strictly (that's a feature: payroll data should be validated), so if your Deel workspace requires an extra field, the error tells you exactly which one. Ticking Deel under "Auto-push on hire" makes every accepted offer create the Deel record automatically, and every push — manual or automatic — is logged on the app's activity page.
03Importing your Deel workforce
"Import your people" reads your Deel people list and adds each person with a work email to the ATS candidate database — matched by email so re-runs never duplicate, marked as imported, fully editable afterwards. Records carry conservative privacy defaults, since these people never used an application form.
04Where it fits in the hiring flow
The push is the last step of the offer workflow: offer accepted → placement confirmed → new hire exists in Deel. Combined with interview scheduling and e-signature earlier in the funnel, the whole path from first interview to payroll-ready employee runs inside one subscription — with Deel handling what Deel is best at, on your own Deel contract.
Arhitectura platformei și operațiuni
A1Connection architecture
The connection uses OAuth 2.0 against the vendor's own consent screen. The authorisation request names the minimum scopes the features need — the exact scope list is shown in the security-flow panel below, pulled from the same provider registry the application uses. The code-for-token exchange happens entirely server-side (HTTP Basic client authentication, per the vendor's token endpoint contract); tokens are stored encrypted at rest and are never rendered back to any screen — connection pages show presence, not values.
Token lifecycle is handled at a single chokepoint: expiry triggers an automatic refresh, rotated refresh tokens are persisted, and a refresh that the vendor rejects surfaces as a visible reconnect prompt — never as silently broken features. Revocation works from either side: disconnect here, or revoke in the vendor's own security settings.
A2Write semantics and data flow
Every data movement is an explicit action with a logged result. Writes happen on your click — or automatically only where you enabled a rule (auto-push on hire is off by default, per-provider). Reads — imports of people, accounts, or files — run when you press Import, deduplicate against what you already have (clients by name, people by email), skip rather than overwrite, and report created-versus-skipped honestly, which is why re-running any import is safe by design.
Each action writes a row to the app-activity journal (ats_app_activity): what ran, when, for which record, and the outcome — including the vendor's own error text verbatim when something fails. Usage reporting inside the ATS aggregates that same journal, so integration reporting and integration reality cannot diverge.
Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.
A3Operational considerations
Connections are organisation-level and gated to owner and admin roles; recruiters use the features a connection powers but cannot connect, disconnect, or reconfigure. Disconnecting removes stored credentials immediately and stops the dependent features visibly, not silently. Data already imported stays yours and editable.
Imported people arrive marked as imported with conservative privacy defaults — no consent is assumed for anyone who never filled in your application form, and retention defaults apply. Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.
A4Placement in the integration topology
This integration is live in the registry today. One connection per provider unlocks every feature it powers, and the topology grid below shows the neighbouring connectors in the same capability area — statuses come from the same registry that drives the in-app hub, so this page can never claim more than the product does. For anything the catalogue does not cover, Webhooks and Zapier are the generic, documented escape hatch.
Harta de dependență
Schieța interfeței pentru
Flux de interacțiune — stări, validări, feedback
flux de securitate OAuth 2.0 — Deel
Neighbouring connectors — Background Checks
Întrebări frecvente
Which Deel fields does the push fill in?⌄
Does this replace Deel onboarding or contracts?⌄
Can hires be pushed automatically?⌄
Is Expertini affiliated with Deel?⌄
Is there an extra charge?⌄
Pe scurt
- Accepted offer → Deel direct employee in one click or automatically
- Sends name, email, start date, title, and country
- Deel's own validation messages surfaced honestly — no silent failures
- Import your Deel workforce into the searchable talent pool
- Email dedupe, safe re-runs, full activity log
- Your own Deel account and contract — no middleware, no markup
Vedeți deel integration în propriul proces de angajare.
Aduceți o descriere reală a jobului la o demonstrație de 30 de minute — proba gratuită inclusă.
Programați o prezentare