Actions29
- Ticket Actions
- Company Actions
- Contact Actions
- Deal Actions
- Lead Actions
Overview
This node integrates with the BCP CRM API to perform various operations on CRM resources such as Contacts, Companies, Deals, Leads, and Tickets. Specifically for the Contact - Create operation, it allows users to create new contact records in the CRM system by providing relevant contact details.
Typical use cases include automating the addition of new contacts collected from web forms, lead generation tools, or other data sources directly into the CRM without manual entry. For example, when a new customer signs up on a website, this node can automatically create their contact record in BCP CRM with their name, email, phone, and address.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to specify additional contact information: |
| - Address: Contact's physical address (string) | |
| - Company Names or ID: Select one or more associated companies from a list or specify IDs | |
| - Email: Contact's email address (string) | |
| - First Name: Contact's first name (string) | |
| - Last Name: Contact's last name (string) (Required for creation) | |
| - Phone: Contact's phone number (string) |
The "Additional Fields" property is a grouped input allowing users to provide detailed contact information. The "Company Names or ID" field supports multiple selections loaded dynamically from existing companies in the CRM.
Output
The node outputs an array of JSON objects representing the created contact(s). Each object contains the data returned by the BCP CRM API for the newly created contact record. This typically includes identifiers, timestamps, and all submitted contact fields.
No binary data output is produced by this operation.
Example output JSON structure (simplified):
{
"id": "contact_id",
"name": "Last Name",
"surname": "First Name",
"emails": "email@example.com",
"phones": "1234567890",
"address": "123 Main St",
"account": ["company_id_1", "company_id_2"],
...
}
Dependencies
- Requires an API key credential for authenticating with the BCP CRM API.
- The node makes HTTP requests to the BCP CRM REST endpoints.
- The base URL and API key must be configured in the node credentials.
- Dynamic loading of company options depends on successful API calls to fetch existing companies.
Troubleshooting
Missing Required Fields:
If the "Last Name" field is not provided when creating a contact, the node throws an error:"The "Last Name" field is required for creating"
Ensure that this field is filled before execution.API Authentication Errors:
If the API key is invalid or missing, HTTP requests will fail. Verify that the API key credential is correctly set up.Network or Endpoint Issues:
Failures in HTTP requests due to network problems or incorrect base URL configuration will cause errors. Check connectivity and credential settings.Empty or Unexpected Responses:
If the API returns unexpected data structures, the node may not output results as expected. Confirm that the API is functioning normally.
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 specifying company IDs.