Resources · Make integration

Deel Make integrationAutomate Deel with Make.

Can Make react to what happens in your Deel account? Yes. The Deel Make integration gives you 7 modules: one instant trigger, five actions and one search. This guide is for HR and operations people who want to link Deel to their other tools, and it walks you from the API key to a live scenario.

Try the Deel integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Deel Make integration do for you?

The Deel Make integration links your Deel account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes data in one app. With Deel, a scenario can start the moment an event you picked happens in your account, then read, create, update or delete records there.

Keep other tools in step with Deel. Watch Records fires as soon as the event you selected happens, and Get a Record fetches the full details so the next module in your scenario can pass them to a spreadsheet, a chat channel or your CRM.

Push data into Deel from elsewhere. When a form, a table or another app holds the information first, Create a Record or Update a Record writes it into Deel, so nobody retypes it by hand.

Look things up before acting. Search Records returns the records that match your criteria; put it in front of an update to act on the right entries only.

What the listed modules do not cover, Make an API Call can reach through the same connection. Deel's own documentation page in Make warns that it is AI-generated from the vendor docs, so check anything important with Deel. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make pricing page explains what the plans include. For a guided start, see the Make training.

Connect

How do you connect Deel to Make?

  1. 01

    Generate an API key in Deel

    You need an active Deel account and API credentials. In Deel, open Apps and Integrations, then Developer Center and the Organization tokens tab. Click Generate New Token, name it, pick the users:read scope, click Generate and copy the key.

  2. 02

    Add a Deel module in Make

    In your scenario, add any Deel module and click Create a connection. A connection is your Deel account linked to Make once; every Deel module in your scenarios reuses it afterwards. The Connection name field is optional but helps when you manage several accounts.

  3. 03

    Paste the key and save

    Enter the credentials you copied from Deel, or follow the instructions shown on screen, and confirm. Once the connection is saved, the module fields become available and you can pick what the module should work on.

First scenario

Your first scenario with Deel

GoalWhen the event you chose happens in Deel, Make fetches the full record so you can send it on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Deel and pick Watch Records as your starting module.

  2. 02

    Link your account

    Click Create a webhook, then Create a connection, and paste the API key generated in Deel. Choose the event the scenario should listen for in the module fields.

  3. 03

    Fetch the details

    Click the + on the right of Watch Records and add Get a Record. Map into it the record ID that Watch Records passes on, so each event brings back the complete record.

  4. 04

    Test with Run once

    Click Run once, then cause the event in Deel. Open the bubble above each module to read the bundles it received: a bundle is one item passed from a module to the next.

  5. 05

    Switch it on

    When the test looks right, add the module that sends the data where you need it, then switch the scenario on. From now on, Deel calls Make each time the event happens.

Triggers

What starts a Deel scenario

1 module starts a scenario when something happens in Deel. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Deel as soon as it happens.

Deel1Watch Records

Watch Records

Instant trigger

In Make“Triggers when selected event occurs.”

You get a scenario that starts by itself when the event you selected happens in Deel, with the record data ready for the next module. It is the only Deel module that can open a scenario on its own.

How it fires
instant: Deel calls Make through a webhook as soon as it happens, so there is no polling interval to set.
When to use it
any flow that should follow a change in Deel, such as copying new information into another tool or alerting a team.
Watch out
create the webhook before the connection, then test it with Run once and a real event.
Modules

What the Deel modules can do

Deel gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Deel1

Create a Record

Action

In Make“Creates a new record.”

This one writes a brand new entry into Deel from data your scenario already holds, so information collected elsewhere lands in Deel without copy and paste.

When to use it
a form or another app captures the details first and Deel should receive them.
Watch out
run a Search Records first if the same entry might already exist, or you will create duplicates.
Deel2

Delete a Record

Action

In Make“Deletes a record by its ID.”

Removes one Deel record, identified by its ID, which keeps your account clean when an entry is no longer wanted.

When to use it
a cleanup step at the end of a flow, once you know exactly which record must go.
Watch out
treat a deletion as final; test with Run once on a record you can afford to lose.
Deel3

Get a Record

Action

In Make“Retrieves the details of a record by its ID.”

Hands you every detail of a single record when you already know its ID, so later modules get the full record, not just what the trigger passed on.

When to use it
right after Watch Records or Search Records, when you need the full picture of one entry.
Watch out
it needs an ID; without one, start with Search Records instead.
Deel4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the whole Deel API to your scenario through the connection you already set up, for anything the other six modules do not offer.

When to use it
you need an endpoint that has no dedicated module in the list.
Watch out
you write the request yourself, so keep the Deel API documentation open and check the scope your token was given.
Deel5

Update a Record

Action

In Make“Updates a record by its ID.”

Changes an existing Deel record, found by its ID, so the values in Deel follow what changed in another tool.

When to use it
a status or a detail moves in your source app and Deel must match it.
Watch out
pair it with Search Records or Get a Record so the ID you pass points to the right entry.
Deel6

Search Records

Search

In Make“Lists records by search criteria.”

Returns the Deel records that match the criteria you set, which lets a scenario act on a filtered set instead of one known entry.

When to use it
before an update or a deletion, to find which records are concerned.
Watch out
a search can return zero, one or many bundles, and every module placed after it runs once per bundle, which adds operations.
Need help

Need help automating Deel with Make?

A person reads every message.

FAQ

Deel and Make: common questions

01Is the Deel Make integration free?
Yes, on the Make side. Deel is a standard app, so it works from the Free plan, which allows 2 active scenarios, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans raise the limits, with unlimited active scenarios and runs of up to 40 minutes. Make counts usage in operations, one per module run on one bundle. You still need an active Deel account with API access, which is covered by Deel's own subscription.
02What do you need to connect Deel to Make?
An active Deel account and an API key. In Deel, go to Apps and Integrations, then Developer Center, open the Organization tokens tab and click Generate New Token. Give the token a name, select the users:read scope, generate it and copy the key. In Make, add a Deel module, click Create a connection, optionally name it, and paste the key. For Watch Records, create the webhook first. The same connection then serves every Deel module you add later.
03Does the Deel trigger in Make run in real time?
Yes. Watch Records is an instant trigger: Deel calls Make through a webhook as soon as the selected event happens, so the scenario does not wait for a schedule. That is different from scheduled triggers, which Make checks at an interval, every 15 minutes by default on a new scenario. There is no polling interval to set on this trigger, and Run once lets you check it with a real event before switching on. Once it is on, each new event starts a run, and every module in the run counts as an operation.
04What if a Deel module you need is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Deel API with the same connection as the other modules, so you are not limited to the seven listed ones. Deel's page in the Make documentation notes that its content is AI-generated from vendor docs and may contain mistakes, so for anything critical check the Deel API reference or ask Deel directly. If you would rather not write requests, a search followed by Get a Record often covers the need.
05Should you use Make or n8n for Deel?
It depends on the tool your team already works in. In Make, Deel comes with an instant trigger, five actions, a search and an API call module, all set up through one connection and a visual editor. The same app often has an n8n node too. Compare the modules each side offers for your exact flow, then choose the editor your team will actually maintain. If you already run other flows in Make, keeping Deel there means one editor and one place to check your runs.
Same platform

Other docs you might need on this stack.

Browse all integrations