Motion Zapier integrationAutomate Motion with Zapier.
The Motion Zapier integration offers 0 triggers, 3 actions and 1 search. Another tool starts the Zap, then Motion creates a project, adds or updates a task, or finds an existing task so a later step can change it in place.
Verified Trustpilot reviews · AI, automation & growth agency
What the Motion Zapier integration actually does
Connecting Motion to Zapier is about getting work into Motion without retyping it. Motion is the planner that uses AI to prioritize your tasks and fit them into the calendar; Zapier brings it the requests, deals and tickets that land in your other tools.
Three typical results, each tied to a real operation. A request turned into a scheduled task: a form response goes through Create Task, and Motion can then place it in someone's week. A project ready on day one: when a deal is won in your CRM, Create Project opens the matching project in the right workspace. A task kept in sync: Find Task locates the existing task, then Update Task changes it when the source changes.
What Zapier does not do for Motion matters just as much. There is no trigger: a task completed or a meeting booked inside Motion cannot start a Zap. So the flow only goes one way, into Motion. And there is no ready-made action to create a project and its tasks in one go; that takes several steps, which means a multi-step Zap.
For the platform question, the n8n vs Zapier comparison sets out the criteria, and the Zapier agency page is there if you would rather have the Zap built for you.
Zapier vocabulary in one minute
Eight words come back on every Zapier page. Here they are, once, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Motion offers no trigger.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, like creating a Motion task.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Not to be confused with a task in Motion.
- Polling vs instant
- Zapier checks a polling trigger 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.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes one, and it needs a paid plan.
What a Motion Zap really costs
Motion is not one of the apps Zapier reserves for paid plans: it runs from the free plan. The question is how many steps your Zap needs.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap size2 steps: one trigger, one action
- Reserved for paid plansNo
- Find, then updateMulti-step Zap: paid plan
The trigger never costs a task, and the checks Zapier runs to look for new items cost nothing either. Each Motion action that succeeds counts as one task; a failed one is not counted. On the free plan, one form response turned into one task stays within the two-step limit. But updating a task means finding it first: Find Task plus Update Task is a search plus an action, a multi-step Zap, so a paid plan.
Connect Motion to Zapier in 3 steps
- 01
Open your connected apps
In Zapier, go to the Apps page and click + Add connection. You need a Motion account, plus access to any workspace you do not own but want the Zap to write into.
- 02
Choose Motion
Search for Motion in the dialog, select it, then click Add connection. A new tab opens on the Motion side, and that is where you sign in to your account.
- 03
Sign in and allow access
Log in to Motion in that tab and grant Zapier access to the account. The connection is saved once, then reused by every Motion step in every Zap you build later.
Your first Zap: a won deal opens a Motion project
GoalEach deal marked as won in your CRM opens a project in the client delivery workspace, only above a set amount.
- 01
Create the Zap and pick the trigger
Start a new Zap and choose your CRM with its won deal event. Motion cannot be this first step, since it has no trigger of its own.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent deals from the connected account; pick a real one to map the next steps from.
- 03
Add a filter
Click the plus icon, choose Filter, and fill the three boxes: the amount field, a number rule, and your threshold. A text rule would never pass on a number.
- 04
Add Create Project
Add Motion with Create Project. Choose the Workspace ID, then map the deal or client name into Project Name so each project is easy to spot.
- 05
Test, then publish
Test the step, check that the project appears in Motion, then click Publish. With its filter, this Zap is multi-step and runs on a paid plan.
The 3 Motion actions
Motion gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Project
ActionIn Zapier“Creates a new Motion Project”
Opens a new project in a Motion workspace, so the work for a client or an initiative has its own place from the start.
Create Task
ActionIn Zapier“Creates a new Motion Task”
Adds a task to Motion from what arrived in the trigger, ready for Motion to fit into someone's calendar.
Update Task
ActionIn Zapier“Updates an existing Task”
Changes a task that already exists in Motion, so it follows what changed in the tool where the work started.
The Motion search, and what happens when it finds nothing
1 search step looks for data that already exists in Motion, so a later step can use it.
A search step looks up something that already exists, then hands it to the next step. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what the Zap does with the result.
Find Task
SearchIn Zapier“Finds an existing Motion task from its properties”
Looks up an existing Motion task from its properties, so the next step can work on that exact task.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds no task stops the Zap there and skips the steps that depended on it. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?On apps that offer it, this box turns a search into a find-or-create. Find Task has no such variant on Motion: create the task with Create Task in its own Zap.
- If multiple search results are found?Three ways out when several tasks match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Motion Zap breaks
Most problems here come from how Zaps work in general, and they look the same on every app. One comes from the Motion search itself.
Four cases come up again and again. None of them needs code, but each one is easier to prevent than to untangle in a crowded calendar. If a Zap still misbehaves, the Zapier troubleshooting page goes through the usual causes.
Old requests are never picked up
A Zap only reacts to what happens after it is switched on. Requests already sitting in your form tool will not become Motion tasks: moving that backlog is a separate job.A Zap that keeps restarting
If a later step writes back into the place your trigger watches, the Zap sets itself off again and again and burns through your task count.A sudden batch is held back
After a bulk import, the trigger app can return a huge batch at once. Zapier's flood protection may hold it rather than create hundreds of Motion tasks.Find Task comes back empty
With the default setting, a search that finds nothing stops the Zap, and Update Task never runs. Check the workspace and the statuses included before blaming Motion.
Need help automating Motion with Zapier?
A person reads every message.
