Actions30
Overview
This node integrates with the SignifyCRM API to manage CRM data. Specifically, for the Task - Create operation, it allows users to create new task records in the SignifyCRM system. This is useful for automating task creation workflows such as assigning follow-ups, scheduling activities, or tracking work items related to sales, support, or project management.
Practical examples include:
- Automatically creating a task when a new lead is added.
- Scheduling a follow-up call task after a meeting.
- Creating tasks linked to specific accounts or projects for team collaboration.
Properties
| Name | Meaning |
|---|---|
| Subject | The title or name of the task being created. |
| Status | The current state of the task. Options: Completed, Deferred, In Progress, Not Started, Pending Input. |
| Priority | The importance 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 deadline or due date for the task completion. |
| Additional Fields | A collection of optional extra fields to add more details to the task. Includes: |
| Assigned To Name or ID | The user responsible for the task. Can be selected from a list or specified by ID via expression. |
| Related To | Links the task to another module record (e.g., Account, Case, Contact, Lead, Opportunity, Project, Ticket, etc.) with module name and record ID. |
Output
The output JSON contains the response from the SignifyCRM API after creating the task. It typically includes the newly created task's details such as its unique ID and all submitted fields.
If the node supports binary data output, it is not applicable here since this operation deals with structured JSON data representing CRM records.
Dependencies
- Requires an API key credential for authenticating with the SignifyCRM API.
- The node uses internal helper functions to fetch user IDs and picklist options dynamically.
- Network access to the SignifyCRM API endpoint is necessary.
Troubleshooting
Common issues:
- Missing required fields like "Subject" or "Status" will cause the API request to fail.
- Invalid user IDs or related record IDs may result in errors or failed linkage.
- Date/time fields must be in a valid format recognized by the API.
- Insufficient permissions or invalid API credentials will cause authentication errors.
Error messages:
- API errors returned from SignifyCRM usually contain descriptive messages about missing or invalid parameters.
- Network or timeout errors indicate connectivity problems.
Resolutions:
- Ensure all required properties are set correctly.
- Verify that referenced user and related record IDs exist in the CRM.
- Confirm API credentials are valid and have sufficient permissions.
- Use expressions carefully to provide dynamic values.
Links and References
- SignifyCRM API Documentation (example placeholder link)
- n8n Expressions Documentation
- SignifyCRM Official Website
This summary is based on static analysis of the node's source code and provided property definitions, focusing on the Task resource's Create operation only.