Actions30
Overview
This node integrates with the SignifyCRM API to update existing tasks in the CRM system. It allows users to modify various attributes of a task such as its subject, status, priority, start and due dates, and additional related fields. This is useful for automating task management workflows, keeping task information up-to-date, or synchronizing task data from other systems.
Practical examples include:
- Automatically updating task statuses based on external triggers.
- Changing task priorities or deadlines programmatically.
- Linking tasks to other CRM modules dynamically during updates.
Properties
| Name | Meaning |
|---|---|
| Task ID | The unique identifier of the task to update (required). |
| Subject | The new subject or name/title of the task. |
| Status | The current status of the task. Options: Completed, Deferred, In Progress, Not Started, Pending Input. |
| Priority | The priority level of the task. Options: (empty), High, Medium, Low. |
| Start Date | The date and time when the task is scheduled to start. |
| Due Date | The date and time by which the task should be completed. |
| Additional Fields | A collection of extra optional fields: |
| Assigned To Name or ID | The user assigned to the task, selectable from a list or via expression. |
| Related To | A related module record linked to the task, defined by: |
| Module Name | The CRM module type related to the task (e.g., Account, Contact, Lead, Opportunity, etc.). |
| Module Name or ID | The specific record ID or name in the related module, selectable or set via expression. |
Output
The node outputs JSON data representing the updated task entry as returned by the SignifyCRM API. This typically includes confirmation of the update and the current state of the task fields after modification.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the SignifyCRM API using an API key credential configured in n8n.
- The node depends on internal helper functions to fetch user IDs and picklist options dynamically.
- Proper API authentication credentials must be set up in n8n before using this node.
Troubleshooting
Common issues:
- Invalid or missing Task ID will cause the update to fail.
- Providing invalid values for enumerated fields like Status or Priority may result in API errors.
- Related module references must be valid and existing records; otherwise, the update might not link correctly.
- Network or authentication failures can prevent successful API calls.
Error messages:
- Errors from the API usually indicate missing required fields or invalid data formats.
- Authentication errors suggest misconfigured or expired API credentials.
- "Item not found" or similar errors mean the specified Task ID does not exist.
Resolutions:
- Ensure all required fields are provided and valid.
- Verify API credentials and connectivity.
- Confirm that related module IDs exist in the CRM.
- Use expressions carefully to avoid passing empty or malformed values.
Links and References
- SignifyCRM API Documentation (example placeholder, replace with actual URL if available)
- n8n Expressions Documentation - for using expressions in property fields.