Skip to main content
A trigger is the event that starts a workflow. When a trigger fires, Hoop executes the actions you’ve configured in sequence. You can add multiple triggers to a single workflow, and each trigger can be refined using filters to narrow when it activates.

​
Adding a trigger

In the workflow builder, click + Add New Trigger, then search for or browse the available trigger types. You can:
  • Name the trigger for easy identification within complex workflows
  • Add filters by clicking + Add Filter to limit the trigger to specific conditions (e.g., only fire when a tag equals “VIP”)
  • Add multiple triggers to the same workflow so different events can all start the same sequence
Click Save Trigger when done.

​
Trigger categories

Hoop organizes triggers into the following categories:
Triggers related to contact data and management:
  • Birthday reminder — fires on a contact’s birthday (use to send birthday messages or offers)
  • Contact changed — fires when tags, assigned users, DND status, or custom fields are updated
  • Contact created — fires when a new contact is added (filter by tag or custom field)
  • Contact DND — fires when Do Not Disturb is toggled on or off for any channel
  • Contact tag — fires when a tag is added or removed from a contact
  • Custom date reminder — fires on a date you specify (great for account review reminders)
  • Note added — fires when a note is added to a contact
  • Note changed — fires when a note is edited
  • Task added — fires when a task is created on a contact
  • Task reminder — fires based on a previously scheduled task
  • Task completed — fires when a task is marked complete
  • Contact engagement score — fires when a contact’s engagement score changes
  • Appointment — fires when appointments are created, confirmed, rescheduled, cancelled, or when a no-show occurs
  • Opportunity changed — fires when an opportunity’s status, stage, or details change
  • Opportunity created — fires when a new opportunity is added
  • Opportunity status change — fires specifically on status transitions
  • Pipeline stage changed — fires when an opportunity moves between pipeline stages
  • Stale opportunities — fires when an opportunity has been inactive for a defined period
  • Form submitted — fires when a contact submits a form
  • Survey submitted — fires when a survey is completed
  • Quiz submitted — fires when a quiz is submitted
  • Order form submission — fires when an order form is submitted
  • Order placed — fires when a new order is created
  • Order fulfilled — fires when an order is marked fulfilled
  • Order submitted — fires on order submission events
  • Payment received — fires when a payment is successfully processed
  • Subscription return triggers — fires on subscription events (renewal, cancellation, etc.)
  • Customer replied — fires when a contact replies to any message
  • Inbound message — fires when an inbound message is received
  • Trigger link clicked — fires when a contact clicks a tracked trigger link
  • Call status — fires based on call outcomes (answered, missed, voicemail, etc.)
  • Product access granted — fires when a contact gains access to a product/course
  • Product completed — fires when a course or product is completed
  • Product started — fires when a contact begins a course
  • Products access removed — fires when access is revoked
  • Product review submitted — fires when a review is left
  • Private channel access granted — fires when a contact joins a private community channel
  • Private channel access revoked — fires when a contact is removed
  • Facebook lead form submitted — fires when a Facebook lead ad is submitted
  • TikTok lead form submitted — fires on TikTok lead form submissions
  • TikTok comments — fires when someone comments on a TikTok reel
  • Shopify triggers — fires on Shopify store events (order placed, abandoned cart, etc.)
  • Scheduler — fires on a recurring schedule (hourly, daily, weekly, monthly)
  • IVR — fires based on events in your automated phone system
  • Inbound webhook — fires when your CRM receives an HTTP POST from an external system (Zapier, Make, custom apps). This is a Premium trigger.
  • Page view — fires when a contact views a tracked page
  • User login — fires when a user logs in
  • Video tracking — fires based on video watch events
  • Prospect generated — fires when a new prospect is identified

​
Inbound webhook trigger (premium)

The inbound webhook trigger lets external systems send data to Hoop via HTTP POST requests, starting a workflow in real time. Common use cases:
  • eCommerce order integration — push order data from your online store to Hoop
  • Customer support — route inquiries from external helpdesks into workflows
  • Event registration — automatically enroll attendees when they register
  • Lead capture — send form data from external landing pages
1

Add the trigger

In the workflow builder, click + Add New Trigger and search for Inbound Webhook.
2

Copy the webhook URL

Hoop generates a unique webhook URL. Copy it and paste it into your external system (Zapier, Make, your app, etc.).
3

Send a test request

Trigger a test event from the external system, then click Fetch Sample Requests in the trigger config to capture the incoming data.
4

Map the data

Select which fields from the payload to use (contact name, email, phone, etc.) and save the trigger.
Inbound webhook workflows can run without a contact — useful for processing data before you know who it belongs to. You can create or update a contact later in the workflow using the Create Contact action.
Last modified on March 4, 2026