Close CRM Trigger icon

Close CRM Trigger

Starts the workflow when Close CRM events occur

Close CRM Trigger

AI-generated

Overview

This node acts as a trigger for Close CRM events, starting workflows when specified events occur in Close CRM. It supports a wide range of entity types such as leads, contacts, opportunities, tasks, custom activities, emails, meetings, calls, SMS, exports, bulk actions, and account setup changes. Users can select specific actions within these events to trigger the workflow, such as creation, updates, deletions, status changes, and other relevant actions. This node is beneficial for automating processes based on real-time CRM changes, like updating a database when a lead is created or sending notifications when a meeting is scheduled.

Use Case Examples

  1. Trigger a workflow when a new lead is created in Close CRM to automatically add the lead to a marketing campaign.
  2. Start a workflow when an email is sent to log the communication in an external system.
  3. Trigger actions when a task is completed to update project management tools.
  4. Automate notifications when a meeting is scheduled or canceled.

Properties

Name Meaning
Event The entity type to trigger on, such as lead, contact, opportunity, task, custom activity, email, meeting, call, SMS, export, bulk action, or account setup.
Actions The specific actions to trigger on for the selected event type. These vary depending on the event and include options like created, updated, deleted, status changes, completed, sent, scheduled, started, canceled, and others relevant to the event type.

Output

JSON

  • body - The full webhook payload received from Close CRM representing the event data.

Dependencies

  • Requires an API key credential for Close CRM to authenticate API requests.
  • Uses Close CRM API to manage webhooks and verify webhook signatures.

Troubleshooting

  • Webhook signature verification failure: Ensure the webhook request contains the correct signature headers and the signature key is properly configured.
  • Webhook URL mismatch: If the stored webhook URL differs from the current node webhook URL, the webhook is deleted and recreated. Ensure the node webhook URL is stable.
  • API request failures: Check API credentials and network connectivity if webhook creation or deletion fails.
  • Custom activity events may require additional status checks to determine if the event should trigger the workflow.

Links

Discussion