Resources · Make integration

Motion Make integrationAutomate Motion with Make.

Tasks that land in Motion without anyone retyping them. The Motion Make integration gives you 16 modules: 2 triggers, 11 actions and 3 searches. This guide shows how to link your account, build a first scenario and pick the right module for each job.

Try the Motion integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Motion Make integration automate?

The Motion Make integration links your Motion workspace to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. A module is one brick of that chain. With Motion, those bricks read, create and change tasks, recurring tasks, projects and comments.

Requests become tasks on their own. A form reply, a new CRM deal or a row in a sheet can feed Create a Task, so the work shows up in Motion with its name and context already filled in. If the request starts a bigger piece of work, Create a Project opens the container first.

Comments reach the people who need them. Watch New Comments spots each new comment in your workspace, and the next module can pass it to the chat tool or inbox your client team actually reads.

A clean list stays clean. Search Tasks and List Recurring Tasks find what already exists, then Update a Task, Unassign a Task or the delete modules tidy it up without clicking through Motion item by item.

Know the limits before you start. Both Motion triggers are scheduled, so Make checks for new items on the scenario's timing rather than hearing about them the second they happen, and nothing in the list watches a task that gets edited or finished. When a listed module falls short, Make an API Call reaches other parts of the Motion API with the same connection. To see how Make fits your stack, read our Make review; if you are weighing another tool, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains what an operation costs you.

Connect

How do you connect Motion to Make?

  1. 01

    Generate an API key in Motion

    You need an active Motion account first. In Motion, open the Settings tab, choose the option that creates an API key and copy the key that appears on screen. Keep it in a safe place for the next step, since it is the only credential Make asks for.

  2. 02

    Add a Motion module and open the connection

    In your scenario, add any Motion module and click Create a connection. A connection is your Motion account linked to Make once, then reused by every Motion module. You can type a label in the Connection name field, which helps when you run several workspaces.

  3. 03

    Paste the key and save

    Paste the API key you copied from Motion into the credential field and confirm. Make now knows your workspace, so the module can offer your projects and tasks instead of making you hunt for identifiers by hand.

First scenario

Your first scenario: turn a request into a Motion task

GoalWhen a new request lands in another app, Make creates the matching task in Motion.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle becomes the first module, the one that starts every run.

  2. 02

    Pick the app where requests arrive

    Search for the tool that collects your requests, such as a form app or a sheet, and choose its watch module. Link its account the same way you will link Motion, then point it at the form or sheet you use.

  3. 03

    Add Create a Task

    Click the + on the right of the first module, search for Motion and pick Create a Task. Select your Motion connection, or click Create a connection if you have not linked the account yet.

  4. 04

    Map the request into the task

    Fill the task fields by clicking the data from the first module: the request title for the task name, the message for its description. Each request travels as a bundle, one item passed from module to module.

  5. 05

    Test with Run once

    Send a test request, then click Run once. Make runs the scenario a single time and shows the bundles each module received. Open Motion and check that the task looks the way you expect.

  6. 06

    Schedule it and switch it on

    Open the clock on the first module and set the schedule; a new scenario checks every 15 minutes by default. Then switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

What starts a Motion scenario?

2 modules start a scenario when something happens in Motion. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Motion as soon as it happens.

Motion1Watch New Comments

Watch New Comments

Scheduled trigger

In Make“Triggers when a new comment is created.”

Watch New Comments hands each fresh comment from your Motion workspace to the rest of the scenario, so a remark left on a task can travel beyond Motion. Every comment it finds becomes its own bundle.

How it fires
it is a scheduled trigger, so Make checks Motion on the scenario's schedule and collects the comments posted since the last check.
When to use it
a client or a teammate leaves feedback on a task and the account manager lives in another tool, so the comment has to follow them there.
Watch out
it only sees new comments, not edits to older ones, and each comment it pulls counts as an operation.
Motion2Watch New Tasks

Watch New Tasks

Scheduled trigger

In Make“Triggers when a new task is created.”

Watch New Tasks gives your scenario a starting point every time someone adds a task in Motion, whether they typed it by hand or another tool created it. The task arrives as a bundle the next modules can read.

How it fires
scheduled, so Make polls Motion at the interval set on the scenario and picks up all the tasks created in between.
When to use it
a new task should also open a ticket, notify a channel or be logged in a sheet the moment the next check runs.
Watch out
a task that is only updated or completed will not trigger it; the module reacts to creation alone.
Modules

What can Make do in Motion?

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

Motion1

Create a Comment

Action

In Make“Creates a new comment.”

Create a Comment writes a note on a Motion task for you, so the context behind a piece of work sits right where the assignee will look. It saves copying details from an email or a ticket.

When to use it
a customer replies to a support thread and the answer should appear on the related task in Motion.
Watch out
pairing it with Watch New Comments in the same workspace can echo comments back and forth, so filter carefully.
Motion2

Create a Project

Action

In Make“Creates a new project.”

Create a Project opens a new project in your Motion workspace, ready to hold the tasks that follow. You get a home for the work before the first task is even written.

When to use it
a deal is signed in your CRM and the delivery team needs a project waiting for them, named after the client.
Watch out
run a search with List Projects first if the same client can come back, or you will end up with duplicate projects.
Motion3

Create a Recurring Task

Action

In Make“Creates a new recurring task.”

Create a Recurring Task sets up a task that Motion repeats by itself, so a routine job never needs to be recreated by hand. Make builds it once and Motion handles the repeats.

When to use it
onboarding a new client comes with standing follow-ups, and you want them in Motion as soon as the contract is signed.
Watch out
this is different from Create a Task; if the job happens only once, the recurring version will keep coming back.
Motion4

Create a Task

Action

In Make“Creates a new task.”

Create a Task drops a new task into Motion from anything that happens elsewhere: a form, an email, a new row. The request becomes scheduled work without anyone retyping it.

When to use it
inbound requests arrive in another tool and each one should turn into a single task in the right project.
Watch out
if the same request can reach the scenario twice, add Search Tasks before this module so you do not create the task a second time.
Motion5

Delete a Recurring Task

Action

In Make“Deletes an existing recurring task.”

Delete a Recurring Task removes a repeating task from Motion, so the routine stops coming back. It keeps the workspace free of routines that no longer apply.

When to use it
a client contract ends and the standing check-ins tied to that account should disappear.
Watch out
treat a delete as final; find the exact recurring task with List Recurring Tasks and test with Run once before you switch the scenario on.
Motion6

Delete a Task

Action

In Make“Deletes an existing task.”

Delete a Task removes one task from Motion for good. It is the cleanup step when work was created by mistake or when the source that asked for it has been cancelled.

When to use it
an order is refunded in your shop and the fulfillment task that came with it no longer makes sense.
Watch out
treat the delete as final and make sure a filter or a search points to the right task before this module runs.
Motion7

Get a Project

Action

In Make“Retrieves an existing project.”

Get a Project fetches the details of one project you already know, so later modules can reuse its name or other information in a message or a report. It reads, it changes nothing.

When to use it
a new task comes in and you want to tell the team which project it belongs to, by name rather than by identifier.
Watch out
it needs one specific project; to browse or pick among several, reach for List Projects instead.
Motion8

Get a Task

Action

In Make“Retrieves an existing task.”

Get a Task reads one Motion task in full, which is handy when the trigger only gives you part of the picture. The next modules can then use what the task holds.

When to use it
Watch New Comments hands you a comment and you want the task behind it before you forward it to a client channel.
Watch out
it returns a single task; for a set of tasks that match a condition, Search Tasks is the right choice.
Motion9

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Motion API from your scenario, using the same connection as the other modules. It covers what the ready-made modules leave out.

When to use it
you need a Motion feature that none of the other 15 modules offers, and a teammate comfortable with API docs can set up the request.
Watch out
this module expects you to know the endpoint and the format of the request; start with the ready-made modules whenever one fits.
Motion10

Unassign a Task

Action

In Make“Unassigns an existing task from the user.”

Unassign a Task takes a person off a task while leaving the task itself in place. The work stays visible in Motion, simply waiting for a new owner.

When to use it
someone goes on leave or changes team, and the tasks they held should go back to the pool so a lead can reassign them.
Watch out
it removes the assignment but gives the task to nobody; add Update a Task afterward if a new owner is already known.
Motion11

Update a Task

Action

In Make“Updates an existing task.”

Update a Task changes a task that already exists in Motion, so it follows what happens in your other tools without a manual edit. What changed at the source can follow into Motion.

When to use it
a ticket changes in your help desk and the matching task in Motion should reflect the new situation.
Watch out
you need the right task first, usually from Search Tasks or Get a Task earlier in the scenario.
Motion12

List Projects

Search

In Make“Lists all projects in the workspace.”

List Projects returns every project in your Motion workspace, one bundle per project. It is the quick way to see what exists before you create or update anything.

When to use it
a new client request arrives and you want to check whether a project already carries their name before you open another one.
Watch out
each project comes out as its own bundle, so the next module runs once per project and uses one operation each time.
Motion13

List Recurring Tasks

Search

In Make“Lists all recurring tasks in the workspace.”

List Recurring Tasks pulls all the repeating tasks of your workspace into the scenario. It gives you an overview of the routines Motion keeps rescheduling for your team.

When to use it
an account closes and you need to spot its recurring check-ins before you remove them with Delete a Recurring Task.
Watch out
the result can hold zero, one or many bundles; add a filter so later modules only act on the ones you meant.
Motion14

Search Tasks

Search

In Make“Searches for tasks or lists them all.”

Search Tasks finds the tasks that match what you are looking for, or lists them all when you leave the search open. It is the lookup step behind most update and cleanup flows.

When to use it
before creating a task from a request, you check whether one with the same name already sits in Motion.
Watch out
the result can hold zero, one or several bundles, so check that the modules after it expect that before you switch the scenario on.
Need help

Need help automating Motion with Make?

A person reads every message.

FAQ

Motion and Make: common questions

01Is the Motion Make integration free?
Yes, on the Make side. Motion is a standard app, so you can use it from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. You still need your own active Motion account, and every module run counts as an operation on your Make plan.
02What do you need to connect Motion to Make?
An active Motion account and an API key. You create the key in Motion by opening the Settings tab and choosing the option to generate one, then you copy it from the screen. In Make, add any Motion module, click Create a connection, give it a name if you like and paste the key. That one connection then serves all 16 Motion modules, so you only do this once per workspace.
03Does the Motion trigger in Make work in real time?
No. Watch New Comments and Watch New Tasks are both scheduled triggers: Make checks Motion on the scenario's schedule and collects what appeared since the previous check. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans can go down to 1 minute. Motion offers no instant trigger in Make, so a comment or a task waits until the next check before the scenario picks it up.
04What if the Motion module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Motion API with the connection you already set up, so a feature missing from the other 15 modules is still within reach. You will need to read the Motion API documentation to know which request to send. Keep in mind that the Make doc for Motion is marked as AI-generated and may contain mistakes, so double-check anything important with Motion directly.
05Should you use Make or n8n for Motion?
It depends on where the rest of your automations live. In Make, Motion comes with 16 ready-made modules, including 2 scheduled triggers and Make an API Call for anything else, and it works from the Free plan. n8n often has a node for the same apps, so check its catalog if your team already builds there. Neither tool is ranked here: compare the modules you need, how your team likes to work and which platform already runs your other scenarios.
Same platform

Other docs you might need on this stack.

Browse all integrations