BCP CRM

Overview

The node interacts with the BCP CRM API to perform various operations on CRM resources such as Company, Contact, Deal, Lead, and Ticket. Specifically for the Contact resource with the Apply Filter operation, it applies a predefined filter to a set of contact IDs and retrieves the filtered data from the CRM.

This operation is useful when you want to quickly filter contacts based on saved criteria (filters) in the CRM system without manually querying or processing the data yourself. For example, you might use this node to apply a filter that selects all contacts from a specific region or with a certain status, then process or export those filtered contacts downstream in your workflow.

Properties

Output

• The output is a JSON array where each element represents a contact record that matches the applied filter.
• Each item contains the contact data fields as returned by the BCP CRM API.
• No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating requests to 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.
• The "Filter Name or ID" options are dynamically loaded from the CRM via an API call, so the node depends on network connectivity and valid credentials.

Troubleshooting

• Common issues:

  • Invalid or expired API key: The node will fail to authenticate and return errors.
  • Using a filter ID that does not exist or is not applicable to the Contact resource may result in empty results or errors.
  • Providing invalid or malformed contact IDs can cause the API request to fail.

• Error messages:

  • Errors from the API are propagated; typical messages include authentication failures or "not found" errors if filters or contacts do not exist.
  • If required parameters like "Filter Name or ID" or "Contact IDs" are missing, the node will throw validation errors before making requests.

• Resolution:

  • Ensure the API key credential is correctly configured and has necessary permissions.
  • Verify that the filter exists and is applicable to the Contact resource.
  • Confirm that contact IDs are correct and formatted properly.
  • Use the "Continue On Fail" option to handle individual errors gracefully in batch operations.

Links and References

• BCP CRM API Documentation (example placeholder, replace with actual link if available)
• n8n Expressions Documentation – for using expressions in property values such as specifying filter IDs dynamically.