Overview
This node integrates with the Motion API to manage workspaces and tasks. Specifically, for the Workspace - Get All operation, it retrieves a list of workspaces accessible via the connected Motion account. This is useful when you want to fetch all available workspaces or filter specific ones by their IDs. Common scenarios include synchronizing workspace data into other systems, listing workspaces for selection in workflows, or performing bulk operations on multiple workspaces.
Example use cases:
- Automatically fetching all workspaces to display in a dashboard.
- Retrieving specific workspaces by ID to process or analyze their data.
- Paginating through large sets of workspaces using cursors.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional parameters to refine the request: |
| - Cursor | A pagination cursor string to continue fetching from a previous paginated response. |
| - IDs | Comma-separated list of workspace IDs to retrieve; if omitted, all workspaces are returned. |
Output
The node outputs an array of workspace objects in the json output field. Each object represents a workspace as returned by the Motion API's /workspaces endpoint. The exact structure depends on the API but typically includes workspace identifiers, names, and related metadata.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Motion API.
- The node makes HTTP requests to
https://api.usemotion.com/v1/workspaces. - Ensure the API key has sufficient permissions to read workspace data.
Troubleshooting
- Empty results: If no workspaces are returned, verify that the API key is valid and has access to any workspaces. Also, check if filtering by IDs is too restrictive.
- Invalid cursor: Using an incorrect or expired cursor value may cause errors or empty responses. Use the cursor exactly as provided by previous API responses.
- API authentication errors: If the API key is missing or invalid, the node will fail with authentication errors. Confirm the API key is correctly configured in n8n credentials.
- Rate limits: Excessive requests may trigger rate limiting by the Motion API. Implement delays or handle retries accordingly.
Links and References
- Motion API Documentation (for detailed API endpoint info)
- n8n HTTP Request Node Documentation (for understanding HTTP request options)