BCP CRM

Overview

The node interacts with the BCP CRM API to perform various operations on CRM resources such as Contacts, Companies, Deals, Leads, and Tickets. Specifically for the Contact resource and the Get By Filter operation, it retrieves a list of contacts filtered by a selected filter ID.

This node is useful when you want to programmatically fetch filtered contact data from BCP CRM within an n8n workflow. For example, you might use it to get all contacts that meet certain criteria defined in a saved filter (e.g., contacts from a specific region or with a particular status) and then process or analyze this data further in your automation.

Properties

Note: The property is required and dynamically loads available filters based on the selected resource.

Output

• The output is a JSON array where each item represents a contact record matching the specified filter.
• Each contact object contains fields as returned by the BCP CRM API, typically including contact details like name, email, phone, and other CRM-specific attributes.
• The node does not output binary data.

Dependencies

• Requires an API key credential for authenticating with 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.
• No additional environment variables are needed beyond the API key credential configuration.

Troubleshooting

• Common issues:

  • Using an invalid or expired API key will cause authentication failures.
  • Specifying a filter ID that does not exist or is not accessible will result in no data or errors.
  • If the resource parameter is incorrect or mismatched with the filter, the request may fail or return empty results.

• Error messages:

  • Errors from the API are propagated; typical messages include authorization errors or "filter not found".
  • If required fields are missing during create/update operations (not applicable here but relevant for other operations), the node throws descriptive errors.

• Resolution tips:

  • Verify the API key is correct and has sufficient permissions.
  • Use the dynamic dropdown to select filters to avoid invalid IDs.
  • Check that the resource matches the intended filter context.

Links and References

• BCP CRM API Documentation (example placeholder, replace with actual if available)
• n8n Expressions Documentation – for using expressions in property values.

If you need details on other operations or resources, feel free to ask!