Actions29
- Ticket Actions
- Company Actions
- Contact Actions
- Deal Actions
- Lead Actions
Overview
This node integrates with the BCP CRM API to manage CRM data programmatically within n8n workflows. Specifically, for the Contact - Update operation, it updates existing contact records in the CRM system by sending modified field values.
Typical use cases include:
- Automatically updating contact details when new information is received from other systems.
- Synchronizing contact data between BCP CRM and external databases or applications.
- Enriching contact records with additional fields such as address, phone, or company associations.
For example, you could update a contact’s email and phone number after receiving updated customer info from a form submission or another CRM.
Properties
| Name | Meaning |
|---|---|
| Contact ID | Unique identifier of the contact record to update. |
| Additional Fields | Optional fields to update on the contact, including: |
| - Address: Contact's physical address (string). | |
| - Company Names or ID: Select one or multiple companies associated with the contact. | |
| - Email: Contact's email address (string). | |
| - First Name: Contact's first name (string). | |
| - Last Name: Contact's last name (string). | |
| - Phone: Contact's phone number (string). |
Output
The node outputs an array of JSON objects representing the updated contact records returned by the BCP CRM API. Each object contains the updated contact data as confirmed by the API response.
If multiple contacts are processed, the output will be an array containing each updated contact's data.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the BCP CRM API via an API key credential.
- The node uses HTTP requests authenticated with the provided API key.
- The base URL and API key must be configured in the node credentials before execution.
Troubleshooting
- Missing Required Fields: When creating or updating contacts, certain fields like "Last Name" may be required by the API. Omitting these can cause errors.
- Invalid Contact ID: Providing an incorrect or non-existent Contact ID will result in API errors indicating the resource was not found.
- API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems to the BCP CRM API endpoint will cause request failures.
- Error Handling: If the node is set to continue on fail, errors for individual items will be included in the output with error messages; otherwise, execution stops on the first error.
Links and References
- BCP CRM API Documentation (example placeholder, replace with actual if available)
- n8n Expressions Documentation – for using expressions in property values such as company IDs.