Overview
This node is a trigger for Leadcrate events, designed to start an n8n workflow whenever specific events occur within the Leadcrate platform. It listens for webhook notifications from Leadcrate related to leads in a specified organization.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when a new lead is created.
- Tracking changes in lead status or score to update CRM systems or notify sales teams.
- Logging or processing notes added to leads automatically.
- Reacting to leads being archived or marked as read to maintain data consistency.
Practical example: When a lead is created in Leadcrate, this node triggers a workflow that sends a welcome email to the lead or assigns the lead to a sales representative.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently supports "Access Token" to authorize API requests. |
| Organization Name or ID | Select or specify the Leadcrate organization by name or ID for which the webhook will listen to events. |
| Events | Choose one or more Leadcrate lead-related events to trigger the workflow on. Options include: - Lead Archived - Lead Created - Lead Marked As Read - Lead Note Added - Lead Score Changed - Lead Status Changed |
Output
The node outputs JSON data representing the event payload received from Leadcrate via the webhook. The output contains the full body of the webhook request, which includes details about the lead and the specific event that triggered the workflow.
If binary data were involved, it would be summarized here, but this node only outputs JSON event data.
Dependencies
- Requires an active Leadcrate account with API access.
- Needs an API key credential (access token) for authenticating requests to Leadcrate.
- The node dynamically loads organizations from Leadcrate via an API call to populate the organization selection.
- Requires proper webhook URL configuration accessible by Leadcrate to send event notifications.
Troubleshooting
- Webhook not triggering: Ensure the webhook URL is publicly accessible and correctly registered in Leadcrate. Verify the selected organization and events are correct.
- Authentication errors: Confirm the provided access token is valid and has sufficient permissions.
- Event data missing or malformed: Check that Leadcrate is sending the expected event payloads and that the node’s event selections match those configured in Leadcrate.
- Webhook creation/deletion failures: Network issues or permission problems may prevent webhook management. Review API credentials and network connectivity.
Links and References
- Leadcrate API Documentation (hypothetical link)
- n8n Webhook Documentation
- Using Expressions in n8n