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 Lead - Create operation, it allows users to create new lead records in the BCP CRM system by providing relevant lead details.
Common scenarios where this node is beneficial include:
- Automating lead capture from web forms or other sources into the CRM.
- Integrating marketing platforms with BCP CRM to automatically add new leads.
- Streamlining sales processes by programmatically adding leads based on external triggers.
For example, when a new contact form submission occurs on a website, this node can be used to create a corresponding lead in BCP CRM with the submitted information such as name, email, phone, and company association.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to specify additional lead details: |
| - Address | Lead's address (string) |
| - Company Names or ID | Select one or multiple companies from a list or specify IDs via expression |
| Lead's email address (string) | |
| - First Name | Lead's first name (string) |
| - Last Name | Lead's last name (string) (required for creation) |
| - Phone | Lead's phone number (string) |
The "Additional Fields" property groups all these inputs, allowing flexible specification of lead attributes during creation.
Output
The node outputs an array of JSON objects representing the created lead(s). Each object contains the data returned by the BCP CRM API for the newly created lead record, including any assigned IDs and field values.
If multiple leads are created in one execution, the output will be an array containing each lead's data object.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the BCP CRM API using an API key credential.
- The node uses HTTP requests to communicate with the BCP CRM REST endpoints.
- Proper configuration of the API base URL and API key is necessary in the node credentials.
Troubleshooting
Missing Required Fields:
If the "Last Name" field is not provided when creating a lead, the node throws an error indicating that this field is required. Ensure this field is always set.API Authentication Errors:
If the API key is invalid or missing, requests will fail. Verify that the API key credential is correctly configured.HTTP Request Failures:
Network issues or incorrect API URLs can cause request failures. Check connectivity and credential settings.Empty or Unexpected Responses:
If the API returns unexpected data structures, verify that the resource and operation parameters are correct and supported.
Links and References
- BCP CRM API Documentation (example placeholder, replace with actual if available)
- n8n Expressions Documentation – for using expressions in property values
- n8n HTTP Request Node – understanding how HTTP requests work in n8n