Motion currently provides 1 trigger that can start a workflow and 7 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Task Created
Triggers when a new task is created.
Create Task
Creates a new task.
Update Task
Update an existing task in Motion
Create Project
Create a new project in Motion
Get Task
Get details of a specific task by ID.
Move Task
Moves a task to a different workspace.
Find Task
Finds an existing task.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Motion event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
Task Created
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Motion action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Task
Combine Motion with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
Task Created
Finishes with
Create Task, then preserve the outcome in Coherence
The exact authentication fields depend on Motion. The workflow structure stays straightforward:
Authorize the Motion account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Motion or provide a complementary trigger or action.
Motion currently provides 1 trigger that can start a workflow and 7 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Motion currently lists 1 trigger and 7 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Motion triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
