Resources · Make integration

Tookan Make integrationAutomate Tookan with Make.

Can a new order in another tool turn into a Tookan delivery job without anyone retyping it? The Tookan Make integration gives you 36 modules: 24 actions and 12 searches. This page shows how to link your account, build a first dispatch flow and pick the right module.

Try the Tookan integration on Make See the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can you automate with the Tookan Make integration?

The Tookan Make integration lets Make create, assign, update and look up Tookan tasks, agents, teams, managers and customers inside a scenario, the automation you build in Make as a chain of modules. Each module is one brick of that chain, and your Tookan account is linked once through a connection that every Tookan module reuses.

Dispatch without copy and paste. A paid order or a filled form in another app hands its data to Create a Delivery Task or Create a Pickup Task, then Auto Assign a Task puts a driver on it. Your dispatcher only steps in when something looks wrong.

Keep your customer book in one place. When a client signs up in your CRM or shop, Create a Customer adds the same person to Tookan, and Update a Customer follows their changes later.

Report on the field team. List Agents, List an Agent's Ratings and List an Agent's Activity feed a sheet or a chat message so a manager sees who worked and how customers rated them.

One limit shapes every design: the Tookan app in Make has no trigger, so a Tookan event cannot start a scenario on its own. The flow starts on another app's trigger or on the schedule you set in Make. If you also weigh n8n, the n8n vs Make comparison lays out the criteria, Make pricing explains how operations are counted, and Make training helps a team learn the editor.

Connect

How do you connect Tookan to Make?

01
Generate your Tookan API key
Log in to your Tookan dashboard, open the settings section, then the keys section. Generate a new key or reuse an existing one, and copy it. You need an active Tookan account for this.
02
Add a Tookan module in Make
In your Make scenario, click the + and search for Tookan. Pick any module, for example Create a Delivery Task, and click Create a connection. You can type a label in Connection name so you recognize it later.
03
Paste the key and save
Paste the API key you copied from Tookan into the connection window and confirm. Every Tookan module in your scenarios can now reuse this connection, so you do this once per account.

First scenario

Your first scenario: turn a new order into an assigned delivery

GoalWhen a new order lands in another app, Make creates a Tookan delivery task and lets Tookan assign an agent.

01
Create the scenario
On the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where orders arrive, such as your shop or form tool, and connect it.
02
Add Create a Delivery Task
Click the + on the right of that first module, search Tookan and choose Create a Delivery Task. Select your Tookan connection, then map the address and customer details from the order bundle.
03
Add Auto Assign a Task
Add Auto Assign a Task after it and map the task created by the previous module. Tookan then picks an agent for the job instead of leaving it in the unassigned list.
04
Test with Run once
Click Run once, place a test order, and open the bundles each module received. Check in Tookan that the task exists and carries an agent before going further.
05
Schedule and switch on
Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each new order now becomes a dispatched delivery, one operation per module run.

Modules

Every Tookan module in Make, and when to reach for it

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

Tookan1

Assign an Agent to a Task

Action

In Make“Used to assign an agent to your task.”

Puts the driver you chose on a job that already exists, so the task leaves the queue with a named person attached.

When to use it

your dispatcher decides who goes in another tool, such as a sheet or a form, and you want Tookan to follow that choice.

Watch out

Make has to know which agent you mean, so a List Agents module earlier in the flow gives you agents to map.

Tookan2

Assign a Task

Action

In Make“Used to assign/reassign an unassigned/assigned task or an assigned task to the Agent.”

Hands a task to an agent whether it is still unassigned or already sitting with someone else, which makes it the module for reassignments.

When to use it

a driver calls in sick and their jobs must move to a colleague without anyone reopening each task by hand.

Watch out

on an assigned task this replaces the current agent, so test it with Run once on a sample job first.

Tookan3

Auto Assign a Task

Action

In Make“Used to auto-assign an unassigned/assigned task.”

Lets Tookan choose the agent for you, so a fresh job gets someone on it without a dispatcher picking a name.

When to use it

right after Create a Delivery Task or Create a Pickup Task in a flow where orders arrive from a shop or a form.

Watch out

Make does not choose the agent here, Tookan does; pick Assign a Task when you want a specific person on the job.

Tookan4

Block/Unlock an Agent

Action

In Make“Used to block/unblock the Agent in your account.”

Switches an agent's access to your Tookan account off or back on, so a person you pause stops receiving work.

When to use it

an HR tool marks a contractor as inactive or returning, and you want Tookan to match that status.

Watch out

blocking touches a real person's ability to work; keep a filter before this module so only confirmed changes get through.

Tookan5

Cancel a Task

Action

In Make“Used to change the status of a task that has already been created to "canceled".”

Moves an existing task to the canceled status, so the driver no longer sees a job the customer has dropped.

When to use it

a refund or an order cancellation in your shop should call off the matching Tookan delivery.

Watch out

the task stays in Tookan, now marked canceled; choose Delete a Task only when you want the record gone.

Tookan6

Create a Customer

Action

In Make“Creates a new customer in Tookan under the specified data source.”

Adds a new customer record to Tookan, so the next task for that person starts from saved details instead of a blank form.

When to use it

a signup in your CRM, booking tool or online store should give the delivery team the same client file.

Watch out

run List Customers before it when the same person may sign up twice, otherwise duplicates pile up.

Tookan7

Create a Delivery Task

Action

In Make“Creates a new delivery task in Tookan.”

Opens a delivery job in Tookan straight from the data of another app, which removes the retyping step between order and dispatch.

When to use it

a paid order, a quote accepted or a form submitted means something has to reach a customer's door.

Watch out

the task starts unassigned unless you follow it with Auto Assign a Task or Assign an Agent to a Task.

Tookan8

Create a Manager

Action

In Make“Creates a new manager in Tookan under the specified data source.”

Gives a new manager an account in Tookan, so the people who supervise dispatch are set up from the same source as the rest of your tools.

When to use it

a new supervisor is added to your HR or staff directory and needs Tookan access on their first day.

Watch out

a manager account is created as soon as the scenario runs, so place a filter before it if onboarding data is not always checked.

Tookan9

Create a Pickup Task

Action

In Make“Creates a new pickup task in Tookan.”

Books a collection job in Tookan, the reverse trip of a delivery, so an agent goes to fetch something instead of dropping it off.

When to use it

a return request, a repair drop or a donation form means an item has to be collected at an address.

Watch out

this module builds pickups only; a job that goes to the customer's door comes from Create a Delivery Task.

Tookan10

Create a Team

Action

In Make“Creates a new team in Tookan under the specified data source.”

Sets up a new team in Tookan, handy when your field staff is split by city, client or shift and the structure lives elsewhere.

When to use it

opening a new zone or signing a new account in your CRM should create the matching group of agents.

Watch out

a team created twice is two teams; check with List Teams or Get a Team first.

Tookan11

Delete a Customer

Action

In Make“Deletes the specified customer object and all its associated data.”

Removes a customer from Tookan together with the data attached to it, which keeps your client list clean after an erasure request.

When to use it

a privacy request or an account closure in your main system must reach Tookan too.

Watch out

the associated data goes with it and nothing in Make brings it back; test on a dummy customer with Run once.

Tookan12

Delete a Manager

Action

In Make“Deletes the specified manager object and all its associated data.”

Takes a manager and their associated data out of Tookan, closing access when someone leaves the operations team.

When to use it

an offboarding event in your HR tool should end that person's Tookan account the same day.

Watch out

deletion is final; if you only need to pause someone's work, an agent can be blocked instead, but a manager record simply disappears.

Tookan13

Delete a Task

Action

In Make“Deletes the specified task object and all its associated data.”

Erases a task and everything linked to it, useful for clearing test jobs or entries created by mistake.

When to use it

you ran a scenario on test data and want Tookan back to a clean state without clicking through each job.

Watch out

a real delivery that was called off belongs in Cancel a Task, which keeps the job in Tookan with a canceled status.

Tookan14

Delete a Team

Action

In Make“Deletes the specified team object and all its associated data.”

Removes a whole team and its associated data from Tookan once that group no longer exists in your organization.

When to use it

a zone closes or a client contract ends, and the matching team should disappear from dispatch.

Watch out

move the agents you keep to another team first, and remember that nothing restores the deleted data.

Tookan15

Get an Agent's Profile

Action

In Make“Returns the agent's profile.”

Fetches one agent's profile, so the rest of your scenario can use that person's details without a lookup in the dashboard.

When to use it

a task was just assigned and you want to send the customer a message naming the driver who is coming.

Watch out

it reads one agent at a time; for the whole roster, List Agents returns every agent as separate bundles.

Tookan16

Get a Task

Action

In Make“Returns agent's task details.”

Pulls the details of a single task into the scenario, which lets you check where a job stands before acting on it.

When to use it

a support ticket mentions an order and you want the task's current state copied into the ticket.

Watch out

you need to know which task you want; when you are hunting through many, List Tasks is the better start.

Tookan17

Get a Team

Action

In Make“Retrieves a team object from your Tookan account.”

Returns one team from your Tookan account, a quick way to confirm it exists and read its data before touching it.

When to use it

before Update a Team or Delete a Team, to make sure the scenario points at the right group.

Watch out

it answers about a single team; List Teams is what you want when the scenario has to loop over all of them.

Tookan18

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Tookan API from your scenario, using the same connection as the other modules, when no listed module does the job.

When to use it

you need a Tookan feature that none of the ready modules covers.

Watch out

you write the request yourself from the Tookan API documentation, so it asks more reading than a ready module.

Tookan19

Send Notification

Action

In Make“Used to send push notifications to the logged-in agent(s).”

Pushes a notification to the phone of agents who are logged in, so a message reaches the field without a separate chat tool.

When to use it

a road closure, an urgent order or a change of depot needs every active driver's attention.

Watch out

only logged-in agents receive it; anyone offline misses the message, so send critical news another way too.

Tookan20

Start a Task

Action

In Make“This module is used to change the status of a task that has already been created to "start".”

Sets an existing task to the started status, so your records show the job is under way even when the change comes from outside the agent app.

When to use it

a scan at the warehouse door or a partner system confirms the job has begun.

Watch out

this module only starts a job; calling one off is the work of Cancel a Task.

Tookan21

Update a Customer

Action

In Make“Updates a customer object in your Tookan account.”

Changes an existing customer record in Tookan, so a new phone number or address reaches the drivers without anyone editing it twice.

When to use it

your CRM or shop is the reference for client data and every edit there should flow into Tookan.

Watch out

find the right customer first with List Customers, or you may overwrite someone else's details.

Tookan22

Update an Agent's Tags

Action

In Make“Used to update the agent's tags.”

Rewrites the tags on an agent, so the labels attached to that driver match what your other tools know about them.

When to use it

a driver passes a training or gets a new vehicle recorded in another tool, and their tags should reflect it.

Watch out

read the current tags with List an Agent's Tags first if you want to add one rather than replace the set.

Tookan23

Update a Task

Action

In Make“Used to force update the status of a task.”

Forces a new status on a task, which fixes jobs stuck in the wrong state or aligns Tookan with what happened on the ground.

When to use it

another system knows the real outcome, such as a signed delivery note, and Tookan should show it.

Watch out

the status is forced; for the usual start or cancel steps, Start a Task and Cancel a Task say more clearly what you mean.

Tookan24

Update a Team

Action

In Make“Updates a team object in your Tookan account.”

Edits an existing Tookan team, so a rename or a change in your organization shows up where dispatchers work.

When to use it

a region is renamed or reorganized in your main tool and Tookan should follow.

Watch out

pair it with Get a Team or List Teams so the scenario targets the team you meant, not the first one it finds.

Tookan25

Get an Agent's Location

In Make“Returns agent's location details.”

Tells you where an agent is, returning their location details for the rest of the flow to use.

When to use it

a customer asks where their driver is and a support tool or chat can answer with that position.

Watch out

as a search it can return zero bundles, so add a route or filter for the case where no location comes back.

Tookan26

Get an Agent's Stripe Details

In Make“Returns agent's stripe account details.”

Reads the Stripe account details tied to an agent, useful when payments to contractors are tracked outside Tookan.

When to use it

a finance sheet or accounting tool needs to check that each contractor has payment details on file.

Watch out

this is payment data; send it only to places your finance team controls and keep it out of shared chats.

Tookan27

List Agents

In Make“Returns all the agent items.”

Returns your whole agent roster, one bundle per agent, ready to copy into a sheet or loop over in later modules.

When to use it

building a staff report, or finding the agent to pass to Assign an Agent to a Task.

Watch out

each agent becomes its own bundle, and every module after it runs once per bundle, which counts operations.

Tookan28

List Agents Near a Customer

In Make“Rerurns available agent's near customers.”

Finds the available agents close to a customer, a shortlist for sending the nearest driver.

When to use it

an urgent order arrives and you want to pick among nearby drivers before calling Assign an Agent to a Task.

Watch out

no one may be nearby; a search can return zero bundles, so plan a fallback such as Auto Assign a Task.

Tookan29

List an Agent's Activity

In Make“Returns agent's daily activity timeline.”

Brings back an agent's daily activity timeline, so you can see how their day unfolded without scrolling the dashboard.

When to use it

a manager reviews a disputed delivery and wants the agent's sequence of events in a document.

Watch out

every entry arrives as a bundle; add an aggregator if you want one summary instead of many rows.

Tookan30

List an Agent's Logs

In Make“Returns Agent logs.”

Collects the logs recorded for an agent, a trace you can archive or search outside Tookan.

When to use it

an audit or a quality review asks for the records behind an agent's work to be stored in a shared drive.

Watch out

logs and the activity timeline are separate modules; pick List an Agent's Activity for a day view.

Tookan31

List an Agent's Ratings

In Make“Returns the agent's overall rating and reviews are given by customers.”

Returns an agent's overall rating and the reviews customers left, which turns feedback into data you can share.

When to use it

feeding a team dashboard, or alerting a manager when reviews for a driver come in.

Watch out

reviews are about real people; decide who can see the output before you post it in a group channel.

Tookan32

List an Agent's Tags

In Make“Returns the list of agent tags.”

Shows the tags currently set on agents, so your scenario knows who has which skill or vehicle before deciding anything.

When to use it

before Update an Agent's Tags, or to route a fragile parcel only to agents tagged for it.

Watch out

a search can come back empty; handle the no-tag case so later modules do not fail.

Tookan33

List Customers

In Make“Returns all the customer items.”

Pulls every customer from Tookan as separate bundles, the base for exports, checks and deduplication.

When to use it

comparing Tookan with your CRM, or checking a person exists before Create a Customer.

Watch out

a large client base means many bundles and many operations downstream; filter early to spare your plan.

Tookan34

List Managers

In Make“Returns all the manager items.”

Returns all the managers in your Tookan account, a clear view of who holds supervision rights.

When to use it

an access review compares Tookan managers with the staff list in your HR tool.

Watch out

spotting a leaver here is only half the job; Delete a Manager removes their data too, so confirm before chaining it.

Tookan35

List Tasks

In Make“Returns all the order items.”

Retrieves your Tookan tasks, one bundle each, to feed reports or to find jobs that need follow-up.

When to use it

a scheduled scenario copies tasks into a sheet so the office sees the workload without a Tookan login.

Watch out

without a trigger in Tookan, this search on a schedule is how you notice new jobs; keep a filter to process each one once.

Tookan36

List Teams

In Make“Returns all team items.”

Lists every team in Tookan, which lets a scenario loop through your groups or match them with another system.

When to use it

syncing zones or client accounts from your CRM, or checking a team exists before Create a Team.

Watch out

for one known team, Get a Team is lighter and spends a single operation.

Need help

Need help automating Tookan with Make?

A person reads every message.

FAQ

Tookan and Make: common questions

01Is the Tookan Make integration free?

Yes, Tookan is a standard app in Make, so it works on the Free plan. That plan has its own limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. You still need an active Tookan account on the Tookan side.

02What do you need to connect Tookan to Make?

You need an active Tookan account and an API key. In the Tookan dashboard, open settings, then the keys section, and generate a key or reuse one you have. In Make, add any Tookan module, click Create a connection, optionally name it, and paste the key. The connection is then shared by all 36 Tookan modules in your scenarios, so there is no need to repeat the step for each module or each scenario you build later.

03Does the Tookan Make integration react in real time?

No. The Tookan app in Make has no trigger, neither scheduled nor instant, so a change in Tookan cannot start a scenario by itself. You have two ways to begin a flow. Start on the trigger of another app, such as your shop or form tool, and let Tookan modules act after it. Or start on a schedule set in Make, every 15 minutes by default, and use a search like List Tasks to pick up what changed. On paid plans the schedule can go down to 1 minute.

04What if the Tookan module you need is missing in Make?

It depends on the feature, but Make an API Call usually covers it. That module reaches any endpoint of the Tookan API with the same connection as the other modules, so you are not limited to the 24 actions and 12 searches listed. You write the request from the Tookan API documentation. Also note that the Make documentation for Tookan is flagged as AI-generated from vendor material and may contain errors, so check important details against Tookan and contact Tookan directly for questions about their documentation.

05Should you use Make or n8n for Tookan?

It depends on the tool your team already builds in. On the Make side, Tookan comes with 36 ready modules for tasks, agents, teams, managers and customers, plus Make an API Call for the rest, and the Free plan is enough to try it. Many apps also have an n8n node, so compare what each side offers for Tookan before committing. Judge on the modules you actually need, how your team reads a scenario, and how usage is counted, rather than on the brand of the tool.

Generate your Tookan API key

Add a Tookan module in Make

Paste the key and save

Create the scenario

Add Create a Delivery Task

Add Auto Assign a Task

Test with Run once

Schedule and switch on

Need help automating Tookan with Make?