Actions30
Overview
This node integrates with the SignifyCRM API to update existing lead records in the CRM system. It allows users to modify various fields of a lead, such as personal details, status, and other custom attributes. This is useful for automating updates to lead information based on external triggers or workflows, ensuring that the CRM data remains current without manual entry.
Practical examples:
- Automatically updating a lead's status after a marketing campaign interaction.
- Changing contact details like first name or salutation when new information is received.
- Assigning leads to different users dynamically based on workflow logic.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead record to update (required). |
| Salutation | The lead's salutation/title. Options include: "", Asst., Dr., K., Mr., Mrs., Ms., Prof., คุณ, ดร., นาง, นางสาว, นาย, รศ., ศจ. |
| First Name | The lead's first name. |
| Status | The current status of the lead. Options include: "", Assigned, Converted, Dead, In Process, New, Recycled, Registered |
| Additional Fields | A collection of optional fields to update, including: |
| - Account Name (string) | |
| - Assigned To Name or ID (select from user list or specify ID) | |
| - Campaign Name or ID (select from campaign list or specify ID) | |
| - Department (string) | |
| - Description (string) | |
| - Email (Primary) (string) | |
| - Last Name (string) | |
| - Lead Source (options): "", Campaign, Cold Call, Conference, Email, Employee, Existing Customer, Other, Partner, Self Generated, Social Media, Trade Show, Web Site, Word of mouth | |
| - Mobile (string) | |
| - Office Phone (string) | |
| - Title (string) |
Output
The node outputs JSON data representing the response from the SignifyCRM API after attempting to update the lead. This typically includes confirmation of the updated record and any relevant metadata returned by the API.
If multiple input items are processed, the output is an array of such JSON objects, each corresponding to one input item.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the SignifyCRM API via an API key credential configured in n8n.
- Uses internal helper methods to fetch user IDs and make authenticated API requests.
- Relies on the SignifyCRM API endpoint
/set_entrywith POST method to perform the update.
Troubleshooting
Common issues:
- Invalid or missing Lead ID will cause the update to fail.
- Providing empty or invalid values for required fields may result in API errors.
- Network or authentication failures can prevent successful API calls.
Error messages:
- Errors returned from the API will be propagated; typical messages might indicate missing fields, invalid IDs, or permission issues.
- If the node is set to continue on failure, errors for individual items will be included in the output with an error message field.
Resolution tips:
- Ensure the Lead ID corresponds to an existing lead in the CRM.
- Verify that the API credentials are correctly configured and have sufficient permissions.
- Validate all input fields before running the node.
Links and References
- SignifyCRM API Documentation (example placeholder, replace with actual URL if available)
- n8n Expressions Documentation – for using expressions in property fields like Assigned To or Campaign ID.