BCP CRM

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 - Get operation, it retrieves detailed information about a single contact using its unique identifier.

Typical use cases include:

• Fetching contact details to enrich customer data in workflows.
• Retrieving contact information before performing updates or sending communications.
• Integrating CRM contact data into other systems or reports.

For example, you might use this node to get a contact's full profile by providing their Contact ID, then use that data downstream to personalize emails or update records in another database.

Properties

Output

The node outputs JSON data representing the contact's details as returned by the BCP CRM API. The structure typically includes all fields associated with the contact record in the CRM system.

• If multiple contacts are returned (unlikely for a single get), they are flattened into the output array.
• The output does not include binary data.

Example output JSON snippet (conceptual):

{
  "id": "12345",
  "name": "John Doe",
  "email": "john.doe@example.com",
  "phone": "+1234567890",
  "company": "Example Corp",
  ...
}

Dependencies

• Requires an API key credential for authenticating with the BCP CRM API.
• The node expects the base URL and API key to be configured in the credentials.
• Network access to the BCP CRM API endpoints is necessary.

Troubleshooting

• Missing Contact ID: The node requires the Contact ID to retrieve a contact. Omitting this will cause an error.
• Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
• Not found errors: If the Contact ID does not exist, the API may return an error or empty data.
• API rate limits or connectivity issues: Network problems or API throttling can cause request failures.
• Error messages from the node will typically include the API response message; check those for clues.

To resolve:

• Verify the Contact ID is correct.
• Check API key validity and permissions.
• Confirm network connectivity.
• Enable "Continue On Fail" if partial failure handling is desired.

Links and References

• BCP CRM API Documentation (example placeholder, replace with actual if available)
• n8n documentation on Creating Custom Nodes
• General REST API usage best practices