Actions104
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Meeting Actions
- Meeting Room Actions
- Meeting Type Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Ticket Actions
- Treatment Actions
- Treatment Type Actions
- Workspace Actions
Task → Get Many
AI-generatedOverview
This node interacts with the Magnet Customer API to retrieve multiple task records. It supports pagination through 'page' and 'limit' parameters, allowing users to control which page of results and how many tasks per page are returned. This is useful for workflows that need to process or analyze batches of tasks from the Magnet Customer system, such as task reporting, synchronization, or automation based on task data.
Use Case Examples
- Retrieve the first 15 tasks to display in a dashboard.
- Fetch tasks page by page to process large sets of tasks in batches.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for the API requests, either API Token or OAuth2. |
| Page | Specifies the page number of task results to retrieve, useful for paginated data fetching. |
| Limit | Sets the maximum number of task results to return per request, with a minimum of 15. |
Output
JSON
_id- Unique identifier of the task.title- Title or name of the task.description- Detailed description of the task.status- Current status of the task.dueDate- Due date of the task.assignedTo- Identifier of the staff member assigned to the task.createdAt- Timestamp when the task was created.updatedAt- Timestamp when the task was last updated.
Dependencies
- Magnet Customer API
Troubleshooting
- Ensure the API credentials (API Token or OAuth2) are correctly configured and valid.
- Check that the 'page' and 'limit' parameters are set to valid numbers; 'limit' must be at least 15.
- If the node fails to retrieve tasks, verify network connectivity and API endpoint availability.
- If custom fields are enabled to be resolved, ensure the custom fields exist and the API user has permission to access them.