Overview
This node integrates with the Motion API to manage tasks within workspaces. Specifically, the "Task - Create" operation allows users to create a new task inside a specified workspace. This is useful for automating task creation workflows, such as adding tasks from form submissions, syncing tasks from other tools, or programmatically generating tasks based on triggers.
Practical examples:
- Automatically create a task in a project management workspace when a new support ticket is received.
- Generate follow-up tasks after a meeting is scheduled.
- Add tasks with specific priorities and due dates based on business rules.
Properties
| Name | Meaning |
|---|---|
| Workspace ID | The unique identifier of the workspace where the task will be created. |
| Title | The title or name of the task to be created. |
| Additional Fields | Optional extra details for the task: |
| - Description | A detailed description of the task. |
| - Project ID | The ID of the project within the workspace to assign the task to. |
| - Assignee ID | The ID of the user who will be assigned the task. |
| - Due Date | The deadline or due date for completing the task (date-time format). |
| - Priority | The priority level of the task. Options are: Low, Medium, High, Urgent. Default is Medium. |
Output
The output JSON contains the newly created task's data as returned by the Motion API. This typically includes fields such as the task's unique ID, title, description, workspace association, project assignment, assignee, due date, priority, status, creation timestamp, and any other metadata provided by the API.
No binary data is output 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
- Missing Required Fields: If "Workspace ID" or "Title" is not provided, the node will fail because these are mandatory for task creation.
- Invalid API Key: Authentication errors may occur if the API key is invalid or expired. Verify the API key credential setup.
- API Rate Limits: Frequent calls might hit rate limits imposed by the Motion API, resulting in errors. Implement retry logic or reduce request frequency.
- Incorrect Field Formats: Ensure that date fields like "Due Date" are in the correct ISO 8601 format; otherwise, the API may reject the request.
- Empty Additional Fields: While optional, providing empty or malformed additional fields could cause unexpected behavior; verify input correctness.
Common error messages:
"Unauthorized"or"Invalid API key": Check API key validity."Bad Request": Usually indicates missing or invalid parameters; review required fields and their formats."Not Found": Could mean the specified workspace or project ID does not exist.
Links and References
- Motion API Documentation – Official API reference for endpoints and data models.
- n8n HTTP Request Node – For understanding how HTTP requests are made within n8n nodes.