Crm Trigger icon

Crm Trigger

Basic Crm Node

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 certain 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 details about the triggered event, such as lead information or action specifics depending on the event type.

The output structure is an array of JSON objects, each corresponding to an event notification received. There is no binary data output.

Example output JSON snippet:

[
  {
    "id": "12345",
    "event": "lead.created",
    "data": {
      "leadId": "abcde",
      "name": "John Doe",
      "email": "john@example.com"
    }
  }
]

Dependencies

  • Requires an API key credential to authenticate with the CRM system.
  • The node uses HTTP requests to register, check, and delete webhooks on the CRM platform.
  • The CRM base URL and API token must be configured in the node credentials.
  • The node exposes a webhook endpoint that must be accessible by the CRM system to deliver event notifications.

Troubleshooting

  • Webhook registration failure: Ensure the API key credential is valid and has permissions to manage webhooks in the CRM.
  • No events triggering: Verify that the webhook URL is correctly registered in the CRM and publicly accessible.
  • Invalid or missing event data: Confirm that the selected events match those supported by the CRM and that the CRM is sending data in the expected format.
  • HTTP errors during webhook management: Check network connectivity and correct base URL configuration in credentials.

Links and References

Discussion