BCP CRM

Overview

The node interacts with the BCP CRM API to manage deals and other CRM resources. Specifically, for the "Deal" resource with the "Apply Filter" operation, it applies a predefined filter to a set of deal IDs and retrieves the filtered results from the CRM system.

This operation is useful when you want to quickly narrow down or segment deals based on saved filters in the CRM without manually querying or processing all deals. For example, you might apply a filter to get all deals in a certain stage or with specific attributes, but only for a subset of deal IDs you are interested in.

Practical examples:

• Apply a sales pipeline stage filter to a list of deal IDs to find which deals are currently in negotiation.
• Use a priority-level filter on selected deals to identify high-priority opportunities.
• Retrieve deals matching custom criteria defined as filters in the CRM for reporting or automation purposes.

Properties

Output

The output is a JSON array containing the filtered deal data returned by the BCP CRM API after applying the specified filter to the given deal IDs.

• Each item in the output array represents a deal that matches the filter criteria.
• The structure of each deal object corresponds to the CRM's deal data schema.
• 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 filter options are dynamically loaded from the CRM via an API call.
• Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing API key credential will cause authentication failures.
  • Specifying an invalid filter ID or a filter not associated with the "Deal" resource may result in empty or error responses.
  • Providing improperly formatted deal IDs (e.g., wrong delimiter or invalid IDs) can cause the API request to fail or return no results.

• Error messages:

  • Errors from the API such as "Unauthorized" indicate credential problems; verify the API key.
  • "Filter not found" or similar errors suggest the filter ID does not exist or is not accessible.
  • Network or timeout errors require checking connectivity and API availability.

• Resolution tips:

  • Ensure the API key credential is correctly set up and has sufficient permissions.
  • Use the node's option loader to select valid filters rather than manually entering IDs.
  • Validate deal IDs before inputting them into the node.

Links and References

• BCP CRM API Documentation (example link, replace with actual if available)
• n8n Expressions Documentation — for using expressions in property fields
• BCP CRM Filters API Endpoint (if publicly documented)