Actions6
Overview
The node interacts with a CRM system to perform various lead-related operations. Specifically, the "Update Lead" operation allows users to modify details of an existing lead in the CRM. This includes updating the lead's status, sub-status, current segment, metadata, reminder date, and managing tags associated with both the lead and the customer.
This node is beneficial in scenarios where automated workflows need to keep lead information up-to-date based on external triggers or data changes. For example, after a sales call, a workflow could update the lead’s status and add relevant tags to reflect the new stage in the sales pipeline.
Practical example: Automatically update a lead’s status to "Contacted," set a follow-up reminder date, and attach specific tags indicating interest level after receiving input from a form submission.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to update (required). |
| Status | The ID of the new status to assign to the lead. |
| Sub Status | The ID of the new sub-status to assign to the lead. |
| Current Segment ID | The ID of the current segment the lead belongs to. |
| Metadata | Additional JSON-formatted metadata to associate with the lead. |
| Remind At | A date-time value specifying when to remind about this lead. |
| Tags | An array of tag IDs to attach to the lead. |
| Customer Tags | An array of tag IDs to attach to the customer associated with the lead. |
| Detach Tags | An array of tag IDs to remove from the lead. |
| Detach Customer Tags | An array of tag IDs to remove from the customer associated with the lead. |
Output
The node outputs a JSON object for each processed item containing:
success: Boolean indicating if the update was successful.operation: The string"updateLead"indicating the performed operation.leadId: The ID of the updated lead.status: The updated status ID (if provided).subStatus: The updated sub-status ID (if provided).metadata: The updated metadata object.remindAt: The updated reminder date-time string.response: The raw response from the CRM API after performing the update.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the CRM system.
- The node makes HTTP POST requests to the CRM API endpoints to update lead information.
- The base URL and API token are retrieved from the configured credentials.
- Proper permissions in the CRM API are necessary to update leads and manage tags.
Troubleshooting
Common issues:
- Invalid or missing Lead ID will cause the API request to fail.
- Incorrect or expired API authentication token will result in authorization errors.
- Providing malformed JSON in the Metadata field can cause parsing errors.
- Attempting to detach tags that do not exist on the lead/customer may be ignored or cause errors depending on the API behavior.
Error messages:
- Authorization errors typically indicate invalid API credentials; verify and update the API key.
- Validation errors from the API may indicate missing required fields or invalid IDs; ensure all required properties are correctly set.
- JSON parsing errors suggest the Metadata input is not valid JSON; validate the JSON format before input.
Resolution tips:
- Double-check all numeric IDs correspond to existing entities in the CRM.
- Use the "Continue On Fail" option to handle individual item failures gracefully in batch operations.
- Validate JSON inputs using online tools or built-in editors before running the node.
Links and References
- BimeBazar CRM API Documentation (hypothetical link as per context)
- n8n HTTP Request Node documentation for understanding API calls: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/