- Home
- Resources
- Integrations
- MotionTools
MotionTools Zapier integrationAutomate MotionTools with Zapier.
The MotionTools Zapier integration connects your delivery bookings to the rest of your tools. Zapier lists 5 triggers, 2 actions and 0 searches for MotionTools: every trigger is instant, and both actions create bookings.
Verified Trustpilot reviews · AI, automation & growth agency
What the MotionTools Zapier integration does for you
MotionTools is a platform for running a workforce and its deliveries. Linked to Zapier, it can report what happens to bookings and packages to your other tools, and take new bookings from them, so nobody copies a delivery by hand from one screen to another.
Three results you can build. A status message to the right person each time a booking moves on: Booking Status Update starts the Zap and your messaging tool sends the note. A delivery log kept up to date without effort, with a spreadsheet row for every Booking Created. And orders taken elsewhere that turn into MotionTools bookings on their own, through Create 1-Stop Booking or Create 2-Stop Booking depending on how many stops the trip has.
All five triggers are instant. MotionTools tells Zapier itself when something happens, so the interval of your plan never delays these Zaps, even on Free.
What Zapier does not do here. Every trigger is only available with a MotionTools admin account, so check the level of your account before planning around them. The two actions create bookings with one or two stops; there is no action to change, cancel or look up an existing booking, and no search at all. To weigh other options, see our n8n vs Zapier comparison or our Make vs Zapier comparison.
Zapier words, in plain language
Seven Zapier terms come up on this page. Each one is defined here once.
- Zap
- The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap, like a package being created in MotionTools. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that creates, writes or sends something, such as a new MotionTools booking.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan's figure counts those and nothing else.
- Polling vs instant
- Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier the moment the event happens. MotionTools is instant.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What MotionTools Zaps really cost
MotionTools is not a premium app, so it works on the free plan. You pay in tasks, and only for actions that go through.
- MotionTools statusNot premium, works on the free plan
- Free plan100 tasks a month, unlimited Zaps, two steps each
- MotionTools triggers5, all instant, admin account required
- MotionTools actions2, both create bookings
The trigger never costs a task, however many bookings or packages it reports. Each successful action counts as one task: one booking created is one task, one row added after a status change is one task. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below does not apply to the MotionTools triggers, which are all instant; it would only concern a polling trigger from another app, for instance one that feeds Create 1-Stop Booking.
Connect your MotionTools account to Zapier
- 01
Open Apps and add a connection
In Zapier, open Apps and click + Add connection. Search MotionTools by name in the dialog and pick it. You need a MotionTools account before you start, and an admin one if you want the triggers.
- 02
Sign in to MotionTools
Click Add connection and sign in to MotionTools in the tab that opens. Use an account with read or write access on anything you do not own yourself and want the Zap to touch.
- 03
Grant access
Allow Zapier to access the account. The connection is saved once and reused by every MotionTools step, whether the Zap starts on a package update or ends on a new booking.
Your first Zap: log each new booking in a spreadsheet
GoalEach time a booking is created in MotionTools, a row with its details lands in your spreadsheet.
- 01
Create the Zap
Start a new Zap, pick MotionTools as the app and Booking Created as the event, then choose the MotionTools connection you added with an admin account.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent bookings of the connected account, so you map from a real booking rather than from a guess.
- 03
Add the spreadsheet row
Add your spreadsheet app as the action with its add-row event, then map the booking values from the test into your columns.
- 04
Optional message (paid plan)
A message after the row turns the Zap into a multi-step one, which needs a paid plan, and each successful action is counted as its own task.
- 05
Test and publish
Test each action once and read what came back. Then publish the Zap to switch it on. Bookings created before publishing are not picked up.
MotionTools triggers on Zapier
5 events start a Zap when something happens in MotionTools, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.
Booking Created
Instant triggerIn Zapier“Triggers when a booking gets created. Only available if you have a MotionToolsadmin account”
Starts your Zap each time a new booking appears in MotionTools. It is the entry point for anything that must know about a delivery from the moment it exists.
Booking Status Update
Instant triggerIn Zapier“Triggers when the status of an existing booking updates. Only available if you have a MotionToolsadmin account”
Reacts whenever the status of an existing booking changes. Zapier puts this one forward on the MotionTools page, and it is the one to pick when you care about progress rather than creation.
Booking Stop Status Update
Instant triggerIn Zapier“Triggers when the status of the stop of an existing booking updates. Only available if you have a MotionToolsadmin account”
Goes one level deeper than the booking: it fires when the status of a single stop inside an existing booking changes, which matters on trips with more than one address.
Package Created
Instant triggerIn Zapier“Triggers when a package gets created. Only available if you have a MotionToolsadmin account”
Runs when a new package is added in MotionTools. Use it when your process tracks parcels rather than whole bookings.
Package Status Update
Instant triggerIn Zapier“Triggers when the status of an existing package updates. Only available if you have a MotionToolsadmin account”
Fires when the status of an existing package changes, so the life of each parcel can be followed outside MotionTools as well.
MotionTools actions on Zapier
MotionTools gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create 1-Stop Booking
ActionIn Zapier“Creates a booking that has just 1 stop.”
Creates a MotionTools booking with a single stop from data another app sent, so an order taken elsewhere becomes a delivery without retyping.
Create 2-Stop Booking
ActionIn Zapier“Creates a booking that has just 2 stops.”
Builds a booking with exactly two stops, for trips that go from one address to another, using values mapped from an earlier step.
When a MotionTools Zap breaks
Zapier attaches no help article to MotionTools, and no limit specific to the app is documented. The cases below come from how Zaps work in general, plus the two requirements the operations themselves state.
Four situations to know before you publish. When a run does not do what you expected, see our Zapier troubleshooting guide.
Triggers need an admin account
Each MotionTools trigger is only available with an admin account. Make sure the account behind your connection is an admin one before you build the Zap.No backlog
A Zap only reacts to what happens after you switch it on. Bookings and packages that already existed are not picked up; moving them is a separate job.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches can start itself again and again and burn through tasks. Keep the source and the destination apart.The payment method must match
Both booking actions require a Payment method enabled for your tenant and available in the booking's service area. Check the value on a test run before publishing.
Need help automating MotionTools with Zapier?
A person reads every message.



