My Track Path Zapier integrationAutomate My Track Path with Zapier.
The My Track Path Zapier integration gives you 0 triggers, 2 actions and 0 searches. So My Track Path never starts a Zap: another app does, and My Track Path receives the order or hands back what it holds about one. Here is what that costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the My Track Path Zapier integration does for you
My Track Path plans delivery routes and follows the last mile. Linked to Zapier, it becomes the receiving end of an automation: a record appears somewhere else, and an order gets created in My Track Path without anyone typing it twice. You can also ask it for the details of an order it already has. If Zapier itself is new to you, start with our Zapier review.
Orders that write themselves. With Create Order, a new row, a form entry or any record in another app becomes an order in My Track Path, with the buyer's name, the address, the priority and the service type filled from that record.
Returns logged the same way. The same action carries a Return setting: 0 for a delivery, 1 for a return. Map it from the record, or set a fixed value when the source only ever holds one kind.
An order looked up on demand. Get Order takes an order number and brings back what My Track Path holds about it, so a later step in the same Zap can reuse those values. Check at test time exactly which values come back.
What Zapier does not do here. My Track Path has no trigger on Zapier: nothing that happens inside it (a new order, a delivery done) can start a Zap. There is no search step either, and no action to update or delete an order. If you need the reverse direction, Zapier is not the tool for it with this app today. To weigh the other platforms on criteria, see n8n vs Zapier.
Zapier words in one minute
Seven terms come back on this page. Here is each one in plain words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. My Track Path offers none.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like creating an order.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer; an instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it needs a paid plan.
What a My Track Path Zap really costs
My Track Path is not reserved for paid plans: it works from the free plan. What you pay for is tasks.
- Free plan100 tasks a month, unlimited Zaps of two steps
- TriggerNever billed
- Each successful action1 task
- Failed actionNot counted
The trigger in the other app costs nothing, however often Zapier checks it. Each Create Order or Get Order that goes through counts one task; one that fails is not counted. Chain both in one Zap and each order costs two tasks, and the Zap becomes multi-step, so it needs a paid plan. The free plan stops at two steps: one trigger, one action. The interval grid below concerns the trigger of the app that starts your Zap, since My Track Path has no trigger of its own.
Connect My Track Path to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your My Track Path account linked once, then reused by every step that uses it.
- 02
Find My Track Path
Type My Track Path in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens, this time on the My Track Path side.
- 03
Sign in and grant access
Sign in to My Track Path in that tab and grant Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: a spreadsheet row becomes an order, and the team hears about it
GoalEach new row in your spreadsheet creates an order in My Track Path, then posts a message in your team chat.
- 01
Create the Zap
Start a new Zap. Since My Track Path has no trigger, the first step comes from the tool where orders are typed in, here a spreadsheet and its new-row event.
- 02
Test the trigger
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the fields on a real row rather than a blank one.
- 03
Add Create Order
Add an action step, choose My Track Path and Create Order, then pick your connection. Map the order number, buyer name, address and area from the row.
- 04
Set the coded fields
Priority, Return and Type of service take numbers: 0 or 1 for the first two, 0, 1 or 2 for the third. Map a column that already holds those values, or type a fixed one.
- 05
Add the message, test, publish
Add a second action with your team chat and write the message with the order number. Two actions make it a multi-step Zap, so it needs a paid plan. Test each step, then click Publish. For a guided start, see our Zapier training.
The 2 My Track Path actions
My Track Path gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Order
ActionIn Zapier“create an order in the system on behalf of the customer”
Puts a new order into My Track Path on behalf of a customer, with who receives it, where it goes and how fast it must leave.
Get Order
ActionIn Zapier“consult the information of a previously added order”
Reads back an order that was added earlier, from its order number alone, so the next steps of the Zap can use its details.
When a My Track Path Zap breaks
Zapier publishes no help article and no specific limit for My Track Path. What can go wrong comes from how Zapier works in general.
Four cases are worth knowing before you publish. If a Zap stops behaving, our Zapier troubleshooting page is the place to start.
Old records stay where they are
A Zap only reacts to what happens after it is switched on. Rows or entries that existed before are not picked up; moving that backlog into My Track Path is a separate job.A Zap that feeds its own trigger
As a general precaution: a Zap that writes into the very place its trigger watches can set itself off again and again and burn through tasks.A bulk import at the source
If the app that starts the Zap suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back.The same record, once
On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating My Track Path with Zapier?
A person reads every message.
