Overview
This node integrates with the Motion API to update an existing task within a workspace. It allows users to modify various attributes of a task such as its title, description, project assignment, assignee, due date, status, and priority. This is useful in scenarios where task details need to be changed dynamically based on workflow conditions or external inputs.
For example, you might use this node to:
- Change the status of a task from "To Do" to "In Progress" when work begins.
- Reassign a task to a different user automatically.
- Update the due date or priority based on changing project timelines.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to update. |
| Update Fields | A collection of fields to update on the task. Options include: |
| - Title | The new title of the task. |
| - Description | The new description of the task. |
| - Project ID | The ID of the project to assign the task to. |
| - Assignee ID | The ID of the user to assign the task to. |
| - Due Date | The new due date of the task (date and time). |
| - Status | The status of the task. Possible values: "To Do", "In Progress", "Done". |
| - Priority | The priority level of the task. Possible values: "Low", "Medium", "High", "Urgent". |
Output
The node outputs JSON data representing the updated task object returned by the Motion API after the update operation. This includes all current properties of the task reflecting the changes made.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Motion API via an API key credential.
- The node uses HTTP requests to communicate with the Motion API endpoint at
https://api.usemotion.com/v1. - Proper configuration of the API key credential in n8n is necessary for authentication.
Troubleshooting
Error: "Please specify at least one field to update"
This error occurs if no update fields are provided. Ensure that at least one property under "Update Fields" is set before executing the node.Authentication errors
If the API key is invalid or missing, the node will fail to authenticate. Verify that the API key credential is correctly configured and has the necessary permissions.Invalid Task ID
Providing a non-existent or incorrect Task ID will result in an error from the API. Confirm the Task ID is correct and exists in the specified workspace.API Rate Limits or Network Issues
Temporary failures may occur due to rate limiting or connectivity problems. Retrying the operation after some time or checking network settings can help.
Links and References
- Motion API Documentation (for detailed API endpoints and data models)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are handled)