Motion

Create tasks that Motion's AI calendar schedules automatically: agents add work with priority, due date, and duration, manage projects and workspaces, and read users and schedules to drive assignment logic.

10 actions API key available

Motion website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A client request arrives by email with a deliverable and a deadline

The agent parses the request into a task: name, description, due date, and an estimated duration

List Users and List Schedules resolve who owns this kind of work and whether their working hours can absorb it before the deadline

The agent compares the assignee's current open tasks from List Tasks against the new duration

If the deadline cannot fit the assignee's schedule, the request escalates to the team lead, who reassigns, renegotiates the date, or bumps priority

Create Task adds the work, and Motion's scheduler slots it into the assignee's calendar

The requester gets a confirmation with the committed date, and the task link posts to the team channel

What This Integration Enables

Motion's premise is that a task without scheduled time is a wish, and its AI calendar makes the schedule automatically from priority, due date, and duration. FlowRunner supplies what that scheduler cannot see: the work arriving in email, forms, chat, CRMs, and meeting bookings. Agents translate incoming requests into properly shaped tasks, check capacity before commitments are made, and keep external trackers mirrored, so the calendar Motion maintains reflects everything the team actually owes, not just what someone remembered to type in. The scheduler is only as honest as its inputs, and agents are how the inputs stay complete. - Create tasks from emails, form submissions, and bookings, with due dates and durations that enable auto-scheduling - Read users, workspaces, and schedules to drive assignment logic that respects working hours and time zones - Keep external project trackers in sync by listing and updating Motion tasks on a schedule - Group intake into projects and escalate capacity conflicts to a human before the commitment is made

Without FlowRunner

Requests become sticky guilt Work arrives by email and chat, gets acknowledged, and lives nowhere the calendar can see

Capacity discovered at the deadline Whether this week's commitments actually fit was never checked, only hoped

The tracker and the calendar disagree The project tool says one thing, the calendar another, and reconciling them is itself a task

With FlowRunner

Every request becomes scheduled time Agents create tasks with due dates and durations, and Motion's AI calendar places them into real working hours

Overcommitment surfaces before the yes Schedules and open-task lists are read before work is accepted, and a human handles the conflict while it is still negotiable

One synced picture of the week External systems mirror Motion through list and update operations, so the tracker and the calendar stop being rivals

Use Case Scenarios

The inbox that stops leaking commitments

A follow-up lands in [Gmail](/integrations/gmail) with "by Friday" in it. The agent creates a Motion task with the deadline, a 90-minute duration, and the email linked in the description. Motion schedules it into the owner's Thursday morning. Nothing depended on the owner transcribing their own inbox, which is the failure mode that used to cost one commitment a week.

Meeting prep that schedules itself around the meeting

A [Calendly](/integrations/calendly) booking fires for a prospect demo. The workflow creates two Motion tasks: an hour of prep due before the meeting and a follow-up block due the day after, both with durations. Motion slots the prep ahead of the demo automatically. When the booking reschedules, Update Task moves the due dates and Motion re-places both blocks without anyone dragging calendar entries.

The daily snapshot that shows the real workload

Each morning, an agent pages through List Tasks per workspace and writes a snapshot to [Google Sheets](/integrations/google-sheets): open tasks by assignee, status, and due date. The ops lead sees whose week is oversubscribed while there is still time to rebalance, and the weekly report assembles itself from snapshots instead of a Friday scramble. A [Slack](/integrations/slack) summary flags anyone whose open durations exceed their scheduled hours.

Human-in-Loop Highlight

Delete Task removes the task and its scheduled time from the assignee's calendar in one irreversible call, and in a sync workflow that is exactly where the danger concentrates. A mirroring agent that misreads an external tracker, a row deleted in the spreadsheet, a status mapping that treats "on hold" as "gone", will happily delete real commitments, and what disappears is not just a record but the calendar blocks protecting the time to do the work. The deadline, meanwhile, survives. So FlowRunner sync agents never delete on inference. When the external source says a task should go, the agent collects the Motion task's details with Get Task, presents what will vanish, name, due date, scheduled duration, assignee, and a person confirms before Delete Task runs. Creating and rescheduling flow freely, because Motion can always re-plan time. It cannot restore a task that no longer exists.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

10 actions

Tasks

List Tasks Retrieves tasks filtered by workspace, status, or assignee, paginated via meta.nextCursor. Workspace filtering is recommended. The read behind capacity checks, snapshots, and sync mirrors.
Get Task Retrieves one task's full details by ID: name, description, status, priority, due date, duration, assignees, project, and workspace. The evidence-gathering step before updates and gated deletions.
Create Task Creates a task in a workspace. With a due date and duration supplied, Motion's AI scheduler slots it into the assignee's calendar automatically. The operation that turns incoming requests into scheduled time.
Update Task Updates only the fields provided, leaving the rest untouched. Changing priority, due date, or duration prompts Motion to re-schedule the task.
Delete Task Permanently deletes a task, removing it from the workspace and from the assignee's scheduled calendar. Cannot be undone, and gated by this page's human check in sync workflows.

Projects

List Projects Retrieves a workspace's projects, the grouping layer for related tasks, paginated via meta.nextCursor.
Create Project Creates a project in a workspace with just a name required. Used to give intake streams and initiatives a home before tasks flow in.

Workspace Context

List Workspaces Retrieves the workspaces the API key can access, with their IDs, names, and configured task statuses and labels. The mapping step that keeps status translations correct in sync workflows.
List Users Retrieves a workspace's members with IDs, names, and emails. The resolution step for assignment logic.
List Schedules Retrieves the account's configured schedules: the working hours and time zones Motion uses when auto-scheduling. The capacity context behind escalate-before-commit logic.

Frequently Asked Questions

What can FlowRunner do with Motion?

FlowRunner agents can run List Tasks, Get Task, and Create Task in Motion, plus 7 more actions.

Does connecting Motion to FlowRunner require OAuth?

No. Motion connects to FlowRunner with an API key, no OAuth flow required.

Can Motion trigger a FlowRunner workflow automatically?

Motion doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Motion

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us