[ Productivity ]
Motion integration for your workflows.
Connect Motion to Collabase once and use 7 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.
Motion in Collabase
Connect Motion to Collabase once and use 7 actions and 1 trigger in your workflows. No code needed, hosted in Switzerland.
How to connect it
- Open the integrations in the workspace settings.
- Choose Motion and connect your account.
- Add a trigger or an action to the workflow.
Motion triggers
| Name | Description | Fields |
|---|---|---|
| Task CreatedChecks at intervals | Triggers when a new task is created. |
|
Motion actions
| Name | Description | Fields |
|---|---|---|
| Create Task | Creates a new task. |
+ 4
|
| Update Task | Update an existing task in Motion |
+ 5
|
| 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 |
+ 3
|
[ Productivity ]
Related integrations
Tools that often share a workflow.
Questions about Motion
What can I automate with Motion in Collabase?
Motion brings 7 actions and 1 trigger, for example Create Task, Update Task, Create Project, Get Task and 3 more. You combine them in a workflow without code and mix them with every other integration.
How do I connect Motion to Collabase?
You open the integrations in the workspace settings, choose Motion and connect your account once, using an API key. After that all triggers and actions are available in the workflow.
Can Motion start a workflow?
Yes. Motion provides 1 trigger, for example Task Created. The workflow runs as soon as the event happens.
Does the Motion integration cost extra?
No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.
Test it against your own content. A proof of concept is ready within days.
We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.