Overview
This node acts as a webhook trigger for a CRM system, allowing workflows to start automatically when specific CRM events occur. It listens for events such as lead creation, updates, deletions, and lead action creations. When one of the selected events happens in the CRM, the node receives the event data via a webhook and triggers the workflow with that data.
Common scenarios include:
- Automating follow-up actions when a new lead is created.
- Syncing lead updates to other systems.
- Triggering notifications or tasks when leads are deleted or specific lead actions occur.
For example, you could use this node to start a workflow that sends a welcome email whenever a new lead is created or to update a marketing list when a lead is updated.
Properties
| Name | Meaning |
|---|---|
| Events | The CRM events to listen for. Options include: "Lead Action Created", "Lead Created", "Lead Updated", and "Lead Deleted". Multiple events can be selected. |
Output
The node outputs JSON data representing the event payload received from the CRM webhook. This JSON contains all relevant information about the triggered event (e.g., details of the lead or lead action). The output is structured as an array with a single object corresponding to the event data.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential to authenticate with the CRM's API.
- Needs the CRM base URL and API token configured in the credentials.
- The node registers and manages webhooks on the CRM platform via HTTP requests to endpoints like
/api/bot/webhooks/create,/check-exists, and/delete. - The node expects the CRM to send POST requests to the webhook URL it provides.
Troubleshooting
- Webhook registration failures: If the node cannot create or verify the webhook on the CRM, ensure the API token and base URL are correct and have sufficient permissions.
- No workflow trigger on events: Verify that the selected events match those emitted by the CRM and that the webhook URL is accessible from the CRM.
- Authorization errors: Check that the API token used in credentials is valid and not expired.
- Unexpected payload structure: Confirm that the CRM sends event data in the expected JSON format.
Links and References
- Refer to your CRM's API documentation for webhook setup and event definitions.
- n8n webhook node documentation for general webhook usage and troubleshooting.