Productivity · Integration
Motion
Add Motion to your product for your customers, and give your AI agents governed access to it.
Motion is a task manager that also owns the calendar, and the difference from every other task tool is that you do not choose when something happens. You describe the work, how long it will take, when it is due and how urgent it is, and the scheduler places it into the person's day and moves it again when something more important arrives. An integration should be written with that in mind: your product supplies duration, deadline and priority rather than a time, and reads back where the work actually landed. The objects are workspaces, projects inside them, and tasks with assignees, statuses, labels and recurrence. Because a write can cause a reshuffle of somebody's whole day, this is a connector where a duplicate create is genuinely disruptive rather than merely untidy. fastn keeps each user's key per tenant and maintains the connector.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Motion account so work created in your product is scheduled into a real day.
Create a task with its duration, deadline and priority and let Motion decide the slot, rather than forcing a time.
Update a task when the underlying work changes, so the schedule reshuffles around what is now true.
Read where a task was placed so your product can tell somebody when their work is actually going to happen.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports what Motion has scheduled for a person today and what it pushed out to make room.
An agent creates the tasks a piece of work implies, with realistic durations, each creation attributed.
An agent flags deadlines the scheduler cannot fit and explains what is in the way.
Example prompt
Add these three pieces of work with their deadlines and tell me when Motion has scheduled each of them.
Set up Motion in 4 steps
- 01Enable the Motion connector in your fastn dashboard.
- 02Have each customer supply the API key from their own Motion account and authorise it.
- 03Choose the workspaces and projects your product writes into, and map duration, deadline and priority.
- 04Call it from your product and expose the same governed connection to your agents.
Why teams use the Motion integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Motion integration without building it. Your customers connect their own Motion account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Motion update is not your on-call problem.
- One integration serves your product and your agents. The same governed Motion connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Todoist
AsanaWorks well with
Google CalendarOften used alongside
Tools the same teams tend to run next to Motion, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceMotion integration FAQ
How do I add a Motion integration to my product?
Enable the Motion connector in your fastn dashboard, then let each customer authenticate their own Motion account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Motion client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Motion account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Motion account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Motion integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports what Motion has scheduled for a person today and what it pushed out to make room.
Who maintains the Motion integration?
fastn does. When Motion changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Motion automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Motion can trigger your workflows in return.
Does it adapt to each team's own Motion setup?
Yes. However a team has configured Motion, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Motion integration?
A common starting point: let each customer connect their own Motion account so work created in your product is scheduled into a real day. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Motion integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Motion does not change your per-connector cost. You can start free with 3 connected accounts.
Add Motion to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.