Actions29
- Ticket Actions
- Company Actions
- Contact Actions
- Deal Actions
- Lead Actions
Overview
This 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 Company resource with the Get By Filter operation, it retrieves a list of companies filtered by a predefined filter ID.
Common scenarios include:
- Fetching a subset of companies that meet certain criteria defined in saved filters within BCP CRM.
- Automating workflows that require processing or analyzing filtered company data.
- Integrating filtered company data into other systems or reports.
Example: You want to get all companies from your CRM that belong to a specific industry or region, as defined by a saved filter, and then send them personalized marketing emails.
Properties
| Name | Meaning |
|---|---|
| Filter Name or ID | Choose a predefined filter from the list or specify its ID via an expression. This filter determines which companies are retrieved based on saved criteria in BCP CRM. |
Note: The property is required and only shown when Resource is "Company" and Operation is "Get By Filter".
Output
The output is a JSON array where each element represents a company record matching the selected filter. Each item contains the company's 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 with the BCP CRM API.
- The node makes HTTP requests to the BCP CRM endpoints using the base URL and API key provided in credentials.
- No additional environment variables or external services are needed beyond the configured API key.
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.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors from the API (e.g., unauthorized, not found) are thrown and can be caught if "Continue On Fail" is enabled.
- If the filter parameter is missing or incorrect, the API may return an error or empty results.
Resolutions:
- Verify the API key is correct and has necessary permissions.
- Confirm the filter exists in BCP CRM and you have access rights.
- Check network connectivity and retry.
Links and References
- BCP CRM API Documentation (example link, replace with actual)
- n8n Expressions Documentation – for using expressions to specify filter IDs dynamically