Actions29
- Ticket Actions
- Company Actions
- Contact Actions
- Deal Actions
- Lead Actions
Overview
This node integrates with the BCP CRM API to update existing lead records in the CRM system. It allows users to modify various fields of a lead, such as contact details and associated company information. This is useful for keeping lead data current, correcting errors, or enriching lead profiles with additional information.
Practical examples include:
- Updating a lead's email and phone number after receiving new contact info.
- Changing the associated company for a lead if they switch employers.
- Correcting spelling mistakes in a lead's name or address.
Properties
| Name | Meaning |
|---|---|
| Lead ID | Unique identifier of the lead record to update. |
| Additional Fields | Collection of optional fields to update on the lead: |
| - Address | The lead's physical address. |
| - Company Names or ID | Select one or more companies from a list or specify their IDs to associate with the lead. |
| The lead's email address. | |
| - First Name | The lead's first name. |
| - Last Name | The lead's last name. |
| - Phone | The lead's phone number. |
Output
The node outputs an array of JSON objects representing the updated lead records returned by the BCP CRM API. Each object contains the lead's data fields as stored in the CRM after the update operation.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the BCP CRM API.
- The node makes HTTP requests to the BCP CRM endpoints using the base URL and API key provided in the credentials.
- Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
- Missing Required Fields: When updating a lead, ensure that the "Lead ID" is provided; otherwise, the API call will fail.
- API Authentication Errors: If the API key is invalid or missing, requests will be rejected. Verify the API key credential setup.
- Invalid Field Values: Providing incorrect formats (e.g., malformed email) may cause the API to reject the update.
- Network Issues: Connectivity problems can cause request failures; check network access to the BCP CRM API endpoint.
- Error Messages: The node throws errors with messages from the API response. Review these messages to identify issues like permission denied or resource not found.
Links and References
- BCP CRM API Documentation (example link, replace with actual)
- n8n Expressions Documentation – for using expressions in property values