Resources · Zapier integration

Detrack Zapier integrationAutomate Detrack with Zapier.

The Detrack Zapier integration has 0 triggers, 1 action and 0 searches. One move, then: an order, a form or a row lands somewhere else, and a delivery job appears in Detrack without anyone on the team retyping the address.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Detrack Zapier integration actually does

Detrack tracks last-mile deliveries and collects proof that each parcel arrived. Zapier, a tool that links apps without code, can push work into it: a step called Create Job opens a new delivery in the Detrack Dashboard every time something happens in another app you use.

Three results people usually chase with it. First, a shop order that turns into a delivery job on its own, so the dispatcher stops copying addresses from one screen to the next. Second, a booking form for a pickup or a drop-off that lands straight in the driver's list. Third, a row added to a shared sheet by the sales team that becomes a scheduled job. All three rely on the same step, Create Job, fed by a different starting app.

Now the honest part. On Zapier, Detrack only writes. It cannot start a Zap: there is no event like "delivery completed" or "proof of delivery received" to react to. It cannot look up an existing job either, and it cannot edit or close one. If the plan was to send a text when a parcel is signed for, this integration will not get there.

That limit shapes the setup. The Zap always begins in another tool (Shopify, Typeform, Google Sheets, your CRM) and ends in Detrack. The Detrack Make integration page covers the same app on Make. And if Zapier itself is new to you, the Zapier review is a decent place to weigh it first.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line below. Here they are, in plain English.

Zap
The automation you build: one starting event, then one or more steps that run each time that event happens.
Trigger
The event that starts a Zap, such as a new order. Once the Zap is on, Zapier waits for it. Detrack offers none.
Action
What the Zap does after it starts: it writes, sends or moves something. Here, Create Job is the only one.
Task
The unit Zapier bills. One action that completes successfully equals one task, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval and keeps what it has not seen.
Instant trigger
A trigger the source app reports itself, the moment the event happens. Nothing waits for the next timed check.
Filter
A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
Multi-step Zap
Any Zap with more than one trigger and one action. A filter or a second action turns it into one, and it then needs a paid plan.
Cost

What a Detrack Zap costs you

The good news first: Detrack is not a premium app, so it works on the free plan.

  • Premium appNo, free plan works
  • Free plan100 tasks a month
  • Steps on free2 (trigger + action)
  • Cost per created job1 task

The trigger in the other app costs nothing, however often Zapier checks it. Each job Detrack accepts counts as one task. A job that fails is not billed. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter to skip some orders and you need a paid plan. How fast the Zap starts depends on the trigger app, using the grid below when that trigger is polled.

Connect

Connect your Detrack account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Detrack account linked once, then reused by every Zap that touches it.

  2. 02

    Find Detrack

    Type Detrack in the search box of the dialog, select it, then click Add connection. You need an existing Detrack account at this point, since Zapier only links accounts that already exist.

  3. 03

    Sign in and grant access

    Sign in to Detrack in the tab that opens and allow Zapier to reach the account. If the account belongs to a colleague, make sure yours has write access, or Create Job will have nowhere to put its jobs.

First Zap

Your first Zap: Shopify orders straight into Detrack

GoalEvery paid Shopify order that needs shipping becomes a delivery job in Detrack, with no copy and paste.

  1. 01

    Create the Zap

    From your Zapier dashboard, start a new Zap. Pick Shopify as the starting app and New Order as the event, then connect your store.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent orders of the store, so you map fields on a real order instead of an empty template.

  3. 03

    Add a filter (paid plan)

    Add a Filter step and point it at the value in the test order that tells local delivery apart from pickup. Pick a text rule for text. On the free plan, skip this step.

  4. 04

    Add Create Job

    Add Detrack as the next step, choose Create Job, and fill each field it asks for with values from the Shopify order you tested.

  5. 05

    Test, then publish

    Test the Detrack step and check that the job really shows up in the Dashboard. If it does, click Publish to switch the Zap on.

Actions

The Detrack action on Zapier

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

1

Create Job

Action

In Zapier“Creates a Job in the Detrack Dashboard”

Opens a new delivery job in the Detrack Dashboard from data that arrived in an earlier step, so drivers see it without anyone typing it in.

When to use it
a webshop, a booking form or a shared sheet already holds the address and the customer, and dispatch keeps retyping them.
Watch out
it only creates. It will not update a job you edit later, so a changed address still has to be fixed by hand in Detrack.
When it breaks

When a Detrack Zap breaks

Zapier attaches no help article to Detrack, so the traps below are the general ones. They still bite.

Most surprises come from the trigger side, not from Detrack. Read these before the first busy day, and keep the Zapier troubleshooting page handy for the rest.

  • Old orders never arrive

    A Zap only reacts to what happens after you switch it on. Orders placed yesterday stay out of Detrack. Moving that backlog is a separate job.

  • A bulk import gets held back

    If the trigger app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of creating a job for each.

  • The same order twice

    On a polling trigger, Zapier remembers what it has already seen, so one order does not start the Zap twice. A duplicate job usually means two Zaps watch the same source.

  • Tasks vanish fast

    A Zap that writes back into the place its own trigger watches sets itself off over and over. Keep the trigger and the output in different spots.
Need help

Need help automating Detrack with Zapier?

A person reads every message.

FAQ

Detrack Zapier integration: frequently asked questions

01Is the Detrack Zapier integration free?
Yes, as long as the Zap stays at two steps. Detrack is not a premium app, so it runs on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the step limit: one trigger and one action, nothing more. A Shopify order going straight into Create Job fits. The same Zap with a filter that keeps only local deliveries does not, because the filter makes it a multi-step Zap, and that requires a paid plan. Price tiers are not listed here because they change too often to stay accurate.
02How many tasks does a Detrack Zap use?
One task per job Detrack accepts. The trigger in the other app is free, and so is every check Zapier runs to look for new orders, rows or form entries. If Create Job does not go through, that run is not billed. Things change once you add steps: in a Zap with two actions, each action that succeeds is counted on its own. So a Zap that creates the job and then posts a message somewhere eats two tasks per order, twice what a single Create Job would.
03Does Detrack on Zapier work in real time?
It depends entirely on the starting app, because Detrack has no trigger of its own. If the app that starts the Zap reports events itself, through an instant trigger, the job appears as soon as the event happens, on any plan. If that trigger is polled, Zapier checks on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. The app page on zapier.com shows which kind each trigger is, and an instant one carries a lightning bolt in the editor.
04What does it take to connect Detrack to Zapier?
A Detrack account that already exists, and a Zapier account. From the Apps page, click + Add connection, search for Detrack, click Add connection, sign in to Detrack in the tab that opens and allow access. If the Detrack account you plan to write into belongs to someone else on the team, check first that your login has write access to it. Without that, Create Job has no right to drop jobs there. Once linked, the connection is reused by every Zap that touches Detrack, so this happens only once.
05Can Zapier update a Detrack job after it is created?
No. The only Detrack operation on Zapier is Create Job, so a Zap can open a job but never touch it again. If a customer changes the address after ordering, the Zap will not carry that change over, and running it again would create a second job rather than fix the first. The same goes for cancellations. Any later edit has to be done by hand in the Detrack Dashboard, which is worth telling the dispatch team before going live, so nobody assumes the two systems stay in sync.
06What if the Detrack operation you need is not on Zapier?
Then it is not available through this integration, and no setting in the editor will reveal it. Zapier lists one visible Detrack operation, Create Job, with no trigger and no search. Anything that reacts to a delivery status, reads an existing job or edits one falls outside what Zapier offers for Detrack today. The practical answer is to keep those steps inside Detrack itself, and use Zapier only for the part it covers: getting new jobs in without retyping them from another tool.
07Zapier, Make or n8n for Detrack?
Judge it on a few criteria rather than on a ranking. If the Zap stays at one trigger and one Create Job, the free plan with its 100 tasks a month covers it. If you need a filter or a second action, budget for a paid Zapier plan. Then count your volume: each created job is one task, so a busy month of deliveries sets the plan. Finally, check the starting app: an instant trigger makes speed a non-issue. Run the same checklist against the other two tools before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations