Motion
Create, schedule and query Motion tasks, projects, recurring tasks, comments and custom fields.
About
Motion ships in the w6w first-party pack. It declares 27 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.motion- Version
- 0.1.2
- Author
- w6w
- Licence
- MIT
- Categories
- Productivity · Project Management · Calendar & Scheduling
Overview
Motion is an AI-driven calendar and task manager that decides when your work actually happens, and this app covers the whole of Motion’s public API: tasks, projects, comments, recurring tasks, custom fields, and the workspaces, users, statuses and schedules everything else is addressed by.
Task management covers the full lifecycle — creating, updating, moving between workspaces, unassigning and deleting — plus dedicated recurring-task definitions with Motion’s own flexible scheduling grammar for things that repeat weekly, monthly or on a custom pattern. Projects can be created against a template with matching stages, and comments let a workflow leave context on a task or project for a human to see. Custom fields extend both tasks and projects with account-specific data, addressed consistently whether you’re reading, setting or clearing a value.
Because Motion assigns work to people by their internal user id rather than an email address, this app’s directory actions — listing users, workspaces, task statuses and schedules — exist mainly to resolve the ids other actions need. A live reachability check backs Motion’s own status page, which currently reports only on its web app rather than the API this app calls.
Build with Motion
Three routes to the same 27 actions. The Workflow tab is generated from Motion's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Delete Custom Field
custom-field-delete Delete a custom field DEFINITION from a workspace. To clear one task's value instead, use Delete Custom Field Value From Task.
List Custom Fields
custom-field-list List a workspace's custom field definitions. Their ids are what the set-value actions need — a task's customFieldValues is keyed by field NAME instead.
Delete Custom Field Value From Project
custom-field-value-delete-project Clear one custom field value from a project. Removes the value only — Delete Custom Field removes the definition from the whole workspace.
Delete Custom Field Value From Task
custom-field-value-delete-task Clear one custom field value from a task. Removes the value only — Delete Custom Field removes the definition from the whole workspace.
Set Custom Field Value On Project
custom-field-value-set-project Set the value of a custom field on a project.
Set Custom Field Value On Task
custom-field-value-set-task Set the value of a custom field on a task.
Create Project
project-create Create a project in a workspace, optionally from a project definition (template).
Create Recurring Task
recurring-task-create Create a recurring-task definition. Assignee is required, and priority and deadline type take narrower value sets than a one-off task.
Delete Recurring Task
recurring-task-delete Delete a recurring-task definition. Motion publishes no update endpoint for one, so changing a frequency means delete and recreate.
List Schedules
schedule-list List the key owner's schedules. A schedule NAME is what the auto-schedule and recurring-task endpoints take; every user has "Work Hours".
List Statuses
status-list List a workspace's statuses. Task status is set by NAME, so this is where a valid value comes from; isDefaultStatus and isResolvedStatus are per-workspace facts.
List Tasks
task-list List tasks, optionally filtered by workspace, project, assignee, label or name.
Move Task
task-move Move a task to a different workspace, optionally reassigning it at the same time.
Unassign Task
task-unassign Remove a task's assignee. The only way to clear an assignee — omitting assigneeId on an update leaves the existing one in place.
Update Task
task-update Update a task. Motion documents the full create body here, so name and workspace are required and the call restates the task rather than patching one field.
Get My User
user-get-me Fetch the user who owns this API key. Its `id` is the assigneeId for assigning work to the connection's own owner.
List Users
user-list List users in a workspace or team. The source of the user id that task assignment needs — Motion never accepts an email address as an assignee.
List Workspaces
workspace-list List the workspaces this API key can see, each with its labels and statuses. The source of the workspace id every write endpoint needs.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Motion's real ids.
{
"manifestVersion": "2",
"name": "motion-example",
"steps": [
{
"id": "comment-create",
"uses": {
"app": "io.w6w.motion",
"action": "comment-create",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"taskId": "<taskId>"
}
}
]
}Here are some of the things you can do
-
Create Comment
performcomment-create -
List Comments
searchcomment-list -
Create Custom Field
performcustom-field-create -
List Custom Fields
readcustom-field-list -
Set Custom Field Value On Project
performcustom-field-value-set-project
+22 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Motion, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Motion. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "task-create",
payload: {
name: "<value>",
workspaceId: "<value>",
// projectId: "<value>",
// assigneeId: "<value>",
// description: "<value>",
// priority: "<value>",
// status: "<value>",
// dueDate: "<value>",
// duration: "<value>",
// autoScheduled: "<value>",
// labels: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action task-create --payload '{"name":"<value>","workspaceId":"<value>"}'Give an AI agent Motion — without giving it Motion's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.motion#comment-create",
"input": {
"taskId": "<taskId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Motion connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Motion's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Motion itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Motion declares its own checks, so its health is a property of the app rather than something the host guesses at.
Motion platform status
Better Stack status page at status.usemotion.com/index.json. Informational only: the page carries a single component, `Webapp`, and no component covering api.usemotion.com — see the `api` check for the API itself.
Motion API reachable
Unauthenticated GET https://api.usemotion.com/v1/users/me. A 401 {"message":"Unauthorized"} passes — it proves the router and the auth guard are serving. Credential validity is the derived auth:* check's job, and Motion's status page covers no API component.