Automations
Triggers

Triggers

A trigger is the specific event that tells Gordon CRM to start an automation. In your workspace, you scope triggers to specific entities (for example, when a particular form is submitted or a particular tag is added).

Broad Targeting with the "Any" Option

When setting up a trigger, you can target specific items or choose the "Any" option:

  • Specific: "When form Inquiry Form is submitted..."
  • Any: "When Any Form is submitted..." (fires the action regardless of which form the contact filled out).

Entity-Based Triggers

These triggers fire in response to contact interactions.

1. Form Submitted

  • Fires when: A contact submits a public form.
  • Verification Flow:
    • New Contacts: The automation fires immediately because there is no prior data to protect.
    • Existing Contacts: To prevent someone from impersonating an existing contact and overwriting their data, the automation fires only after the contact clicks the verification link sent to their email.

2. Event Registration

  • Fires when: A contact registers for an event.
  • Integrations: This trigger fires from both native RSVP form submissions and third-party ticket bookings (like Eventbrite). If a ticket order contains multiple slots for the same contact, the automation runs only once.

3. Product Purchased

  • Fires when: A Stripe checkout session completes successfully for a linked product in your workspace.

4. Product Refunded

  • Fires when: A product purchase is refunded in Stripe.

Tag-Based Triggers

Tag triggers are useful for chaining workflows. They can fire when tags are changed manually by your team or programmatically by another rule.

5. Tag Applied

  • Fires when: A specific tag is added to a contact.
  • Example: Applying the "VIP" tag can automatically enroll a contact in a premium welcome email campaign.

6. Tag Removed

  • Fires when: A specific tag is removed from a contact.
  • Example: Removing the "Active Member" tag can automatically remove them from a members-only announcement list.

Deal-Based Triggers

These triggers fire when sales opportunities progress through your pipelines.

7. Deal Stage Changed

  • Fires when: A deal card is dragged to a new stage on the Kanban board or modified on a detail page.
  • Targeting: You can target "Any Pipeline / Any Stage", "Specific Pipeline / Any Stage", or narrow it down to a "Specific Pipeline / Specific Stage".

8. Deal Status Changed

  • Fires when: A deal is marked with a terminal status of Won or Lost.
  • Targeting: You can target status changes across all pipelines or limit the rule to a specific pipeline (e.g., "Only when a deal in Enterprise Sales is Won").

Lifecycle Triggers

9. Contact Birthday

  • Fires when: The system finds contacts whose birth month and day match today's date.
  • Timing: A daily background sweeper runs automatically in the morning, checking all contacts in your database and triggering any matching rules (e.g., sending a birthday greeting email).

Related

OverviewActions