Actions68
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Workspace Actions
Overview
The node integrates with the Magnet Customer API to update existing tasks within a CRM or project management context. It allows users to modify task details such as title, description, status, ownership, and associations with other entities like organizations, contacts, or deals. This node is useful for automating task management workflows, keeping task information up-to-date based on external triggers or data changes.
Practical examples include:
- Automatically updating task statuses when a related deal progresses.
- Changing task ownership based on workload distribution rules.
- Adding descriptive notes or deadlines to tasks created by other systems.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "API Token" or "OAuth2". |
| Task ID | The unique identifier of the task to update (required). |
| Title | The new title of the task. |
| Description | A textual description or observation about the task. |
| Expectation of Closing | The expected date and time by which the task should be completed. |
| Task Slug or Name or ID | The type of the task, selected from active task types. If omitted, the task is assigned to the authorized user. |
| User Name or ID | The user to whom the task will be assigned. If omitted, defaults to the authorized user. |
| Status | The current status of the task. Options are "Pendente" (pending) or "Concluída" (finished). Defaults to "open" if not provided. |
| Date Of Finished | The date and time when the task was finished. |
| Associate With | The type of entity to link this task to: "Organization", "Contact", or "Deal" (required). |
| Organization ID | The ID of the organization associated with the task (shown only if "Associate With" is "Organization"). |
| Contact ID | The ID of the contact associated with the task (shown only if "Associate With" is "Contact"). |
| Deal ID | The ID of the deal associated with the task (shown only if "Associate With" is "Contact" — likely a UI configuration issue; logically should be "Deal"). |
Note: Several hidden properties related to "Life Cycle" and "Source" exist but are not exposed for user input in this operation.
Output
The node outputs an array of JSON objects representing the updated task(s) returned from the Magnet Customer API. Each output item corresponds to one input item processed and contains the full task data after the update.
If the API supports binary data for tasks (e.g., attachments), it would be included accordingly, but this node primarily handles JSON task data.
Dependencies
- Requires access to the Magnet Customer API.
- Requires credentials configured in n8n for authentication, either via an API token or OAuth2.
- The node uses internal helper functions to make HTTP requests to the API endpoints corresponding to tasks.
- No additional external dependencies beyond the Magnet Customer API and proper credential setup.
Troubleshooting
Common issues:
- Invalid or missing Task ID will cause the update to fail.
- Providing invalid IDs for associated entities (organization, contact, deal) may result in errors.
- Incorrect authentication credentials will prevent successful API calls.
- Status values outside the allowed options ("pending", "finished") may cause rejection.
Error messages:
- Errors from the API typically include messages indicating missing required fields or invalid references.
- Network or authentication errors will manifest as connection failures or unauthorized responses.
Resolutions:
- Ensure all required fields, especially Task ID, are correctly set.
- Verify that associated entity IDs exist and are valid.
- Confirm that the chosen authentication method is properly configured with valid credentials.
- Use the "Continue On Fail" option in n8n to handle individual item errors gracefully.