BCP CRM icon

BCP CRM

Interact with BCP CRM API

Actions29

Overview

The node integrates with the BCP CRM API to perform various operations on CRM resources such as Leads, Contacts, Companies, Deals, and Tickets. Specifically for the Lead resource with the Apply Filter operation, it applies a predefined filter to a set of lead IDs and retrieves the filtered data from the CRM.

This node is useful when you want to programmatically filter leads based on saved filters in BCP CRM and process or analyze the filtered results within an n8n workflow. For example, you might use it to segment leads that meet certain criteria (e.g., leads from a specific campaign or status) and then trigger follow-up actions like sending emails or updating records.

Properties

Name Meaning
Filter Name or ID Select a saved filter by name or specify its ID to apply to the leads.
Lead IDs Provide one or multiple unique identifiers of leads to which the filter will be applied.
  • The "Filter Name or ID" property loads available filters dynamically from the CRM.
  • "Lead IDs" expects a string of lead identifiers; these are the leads that the filter will be applied against.

Output

  • The output is a JSON array containing the filtered lead data returned by the BCP CRM API.
  • Each item in the output corresponds to a lead record that matches the applied filter.
  • The structure of each lead object depends on the CRM's response but typically includes lead details such as name, contact info, status, and other custom fields.
  • No binary data output is produced by this operation.

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.
  • The user must have predefined filters configured in their BCP CRM account to select from.

Troubleshooting

  • Common issues:

    • Providing invalid or empty lead IDs may result in no data returned or errors.
    • Using a filter ID that does not exist or is not accessible will cause the API call to fail.
    • Missing or incorrect API credentials will prevent successful communication with the CRM.

  • Error messages:

    • Errors from the API are propagated and can appear as messages indicating failure to find filters or leads.
    • If the node throws an error about missing required fields, verify that all mandatory properties are correctly set.
    • Network or authentication errors should be resolved by checking API key validity and network connectivity.

  • To handle errors gracefully, enable the "Continue On Fail" option in the node settings if partial processing is acceptable.

Links and References

Discussion