Resources · Make integration

Detrack Make integrationAutomate Detrack with Make.

What if new jobs showed up in Detrack without anyone typing them in? The Detrack Make integration gives you 8 modules: 6 actions and 2 searches. This page shows how to link your account, build a first scenario and pick the right module for each job task.

Try the Detrack integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Detrack Make integration do for you?

The Detrack Make integration lets Make read and change your Detrack jobs for you. You build a scenario, the automation you set up in Make, from modules: each module is one brick, like an action on a job or a search through your jobs. Once it runs, jobs are created, updated or cleaned up without copy and paste.

Jobs created from the tools you already use. Put the trigger of another app first, such as a form or a store, then add Create a Job. Each new entry becomes a Detrack job with the details mapped from the previous module.

Jobs kept in sync when plans change. Look up the right record with Search Jobs or Get a Job, then pass it to Update a Job. When several jobs move together, Update a Batch acts on the batch instead.

A list you can send elsewhere. List Jobs returns your jobs as bundles, one item per job, ready to be written to a sheet or a report in another app.

One limit to know: Detrack has no trigger in Make. A scenario never starts on its own from a Detrack event; it starts on its schedule or from another app. For anything the 8 modules skip, Make an API Call reaches the rest of the Detrack API with the same connection. If you want to learn the editor properly, the Make training is a good start, and Make pricing explains how operations are counted. Deciding between tools? Read n8n vs Make.

Connect

How do you connect Detrack to Make?

  1. 01

    Generate your API key in Detrack

    You need an active Detrack account. In Detrack, open Settings in the top bar, pick API Key from the dropdown, click Generate API Key and copy the key shown on screen.

  2. 02

    Add a Detrack module in Make

    In your scenario, add any Detrack module and click Create a connection. A connection is your Detrack account linked to Make once, then reused by every Detrack module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied from Detrack, or follow the instructions Make shows in the window, then save. The module can now read your Detrack jobs and list what it finds.

First scenario

Build your first scenario with Detrack

GoalWhen a new order lands in another app, Make creates the matching job in Detrack.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your orders or requests arrive and choose its trigger.

  2. 02

    Add Create a Job

    Click the + on the right of that first module, search for Detrack and pick Create a Job. Select your connection, or click Create a connection if this is your first Detrack module.

  3. 03

    Map the job details

    Fill the module fields by mapping data from the first module: pick, in the list Make shows, the values each field needs. Each bundle, one item passing from module to module, turns into one Detrack job.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open the bubble above each module to read the bundles it received, then check in Detrack that the job looks right.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on so each new order becomes a job without you touching it.

Modules

Every Detrack module in Make

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

Detrack1

Create a Job

Action

In Make“Creates a job.”

Create a Job adds a new job to Detrack from data that reached your scenario, so nobody has to type it twice. It is the module most Detrack scenarios end on.

When to use it
right after the trigger of your store, form or CRM, when a new order or request should become work in Detrack.
Watch out
each bundle creates one job, so a module that returns several items upstream will create several jobs.
Detrack2

Delete a Job

Action

In Make“Deletes a job.”

Delete a Job removes a job from Detrack, which keeps your list free of orders that were cancelled at the source. Feed it the job you found with a search.

When to use it
when an order is cancelled in the app that created it and the matching job should disappear too.
Watch out
the module acts on your real Detrack jobs, so test with Run once on a single job first.
Detrack3

Get a Job

Action

In Make“Gets a job.”

Get a Job fetches one specific job, giving the next modules its full details to work with. You already know which job you want; this module simply reads it.

When to use it
when the previous step hands you a job reference and you need the rest of that job before updating it or sending it on.
Watch out
it returns one job, not a list; to look for jobs you do not know yet, use Search Jobs.
Detrack4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Detrack API from your scenario, with the same connection as the other modules. It covers what the 7 named modules leave out.

When to use it
when the task you need is not among the listed modules and the Detrack API offers it.
Watch out
you write the request yourself, so keep the Detrack API documentation open while you set it up.
Detrack5

Update a Batch

Action

In Make“Updates a batch.”

Update a Batch changes a Detrack batch in one step, rather than touching jobs one at a time. That keeps a grouped set of work consistent after a change of plan.

When to use it
when the change you need applies to the batch as a whole and not to a single job.
Watch out
for a single job, Update a Job is the right module; pick the one that matches what you actually change.
Detrack6

Update a Job

Action

In Make“Updates a job.”

Update a Job edits an existing job so Detrack reflects the latest details from your other tools. Pair it with Get a Job or Search Jobs to target the right record.

When to use it
when a customer changes an address or a date in your store or CRM and the job has to follow.
Watch out
check that it targets the right job, and test on one job with Run once before switching the scenario on.
Detrack7

List Jobs

Search

In Make“Lists jobs.”

List Jobs returns your Detrack jobs as a set of bundles, one per job, so later modules can go through them. Think of it as pulling the list out of Detrack.

When to use it
when you want to copy your jobs into a sheet, a report or another app.
Watch out
every job returned runs the next modules once, and each run counts as an operation, one execution of one module that Make counts on your plan.
Detrack8

Search Jobs

Search

In Make“Searches for jobs.”

Search Jobs looks for the Detrack jobs that match what you are after, so you can act on the right ones without knowing their reference. It returns zero, one or several jobs.

When to use it
before Update a Job or Delete a Job, when all you have is information from another app.
Watch out
an empty result stops that path, and several results mean the next module runs several times.
Need help

Need help automating Detrack with Make?

A person reads every message.

FAQ

Detrack and Make: common questions

01Is the Detrack Make integration free?
Yes, Detrack is a standard app in Make, so it is available on the Free plan. That plan gives you 2 active scenarios, a minimum of 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 lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your Detrack subscription is separate and follows Detrack's own pricing page.
02What do you need to connect Detrack to Make?
You need an active Detrack account and an API key. In Detrack, go to Settings in the top bar, choose API Key, click Generate API Key and copy the value. In Make, add a Detrack module, click Create a connection, give it a name if you want, and paste the key. That single connection then serves all 8 Detrack modules in every scenario you build. No key yet? Nothing works until you click Generate API Key in Detrack, so start there.
03Does the Detrack Make integration react in real time?
No, because Detrack has no trigger module in Make, nothing in Detrack can start a scenario by itself. You have two ways to start one. Put the trigger of another app first, so the scenario runs when that app reports something new. Or let the scenario run on its schedule, set on the first module, which is every 15 minutes by default and as short as 1 minute on paid plans. In both cases the Detrack modules act as the following steps.
04What if a Detrack module is missing in Make?
Use Make an API Call. It calls any endpoint of the Detrack API from your scenario and reuses the connection you already created, so there is no second setup. The 7 other modules handle creating, reading, updating, searching, listing and deleting jobs, plus updating a batch. Anything beyond that goes through the API call, with the Detrack API documentation at hand. Also note that Make labels its Detrack documentation as AI generated, so verify key details with Detrack.
05Should you use Make or n8n for Detrack?
It depends on your setup. Many apps have both a Make app and an n8n node, so check what exists on the n8n side for Detrack before choosing. In Make, you get 8 ready modules covering jobs and batches, plus Make an API Call for the rest of the API, and no trigger. If your other automations already run in one of the two tools, keeping Detrack there is usually the simplest choice, since your connections and habits stay in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations