Overview
This node acts as a trigger for events occurring in the BCP CRM system. It starts an n8n workflow when specific changes happen in selected CRM resources, such as when rows are added or updated. This is useful for automating processes that depend on real-time updates from the CRM, like syncing data to other systems, sending notifications, or updating dashboards.
For example, you could use this node to:
- Trigger a workflow whenever a new company record is added to the CRM.
- Start a process when a contact's information is updated.
- Monitor ticket updates and automatically assign follow-up tasks.
Properties
| Name | Meaning |
|---|---|
| Resource | The CRM resource to monitor. Options: Company, Contact, Deal, Lead, Ticket |
| Limit | Maximum number of rows returned per polling cycle. Options: 50, 100, 200 (max 200) |
| Trigger On | The event type to trigger on. Options: Row Added, Row Updated |
Output
The node outputs an array of JSON objects representing the rows from the selected CRM resource that triggered the event. Each object corresponds to a row that was either added or updated, depending on the chosen trigger event.
If no new or updated rows are found during polling, the node returns null to indicate no trigger.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the BCP CRM API.
- The node makes HTTP GET requests to the BCP CRM API endpoints to poll for changes.
- The base URL and API key must be configured in the node credentials.
- Polling is used to detect changes, so the node depends on periodic execution within n8n.
Troubleshooting
- No data returned: Ensure the API key credential is valid and has access to the requested resource. Also verify that there have been recent additions or updates matching the trigger event.
- Authentication errors: Check that the API key is correctly set up in the node credentials and has not expired or been revoked.
- Empty triggers: If the limit is set too low, some changes might be missed if many occur between polls. Increase the limit up to 200 if needed.
- API endpoint issues: The node switches endpoint URLs based on the resource; ensure the resource name matches supported values exactly.
Links and References
- BCP CRM API documentation (not provided here, but recommended to consult for detailed API behavior)
- n8n documentation on creating and using trigger nodes
- General info on webhook vs polling triggers in automation workflows