> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/list-of-workflow-triggers.md). # List of Workflow Triggers {% embed url="" %} Within the Workflow Builder you can have one or multiple triggers to fire off the workflow’s series of actions. Below is a complete list of workflow trigger options: **Appointments** * **Appointment Status:** runs on all appointment status updates **Contact** * **Birthday reminder:** runs on customer’s birthday (if in their Contact Record) * **Contact Changed:** Runs when a contact data is updated * **Contact Created:** Runs when a new contact record is added * **Contact Tag:** runs when tags are added or removed * **Custom Date Reminder:** runs on a custom date * **Note Added:** runs when a note is added to the contact * **Note Changed:** runs when a note is modified * **Task Added:** runs when a task is added for the contact * **Task Reminder:** reminds that the task is due **Contact Actions** * **Customer Replied:** a contact responded to the workflow * **Form Submitted:** runs when a form is submitted * **Order Form Submission:** runs when a contact submits an order form * **Order Submitted**: Runs upon a 1-Step or 2-Step order form submission and upsells. Please note that this only works with version 2 funnels * **Survey Submitted:** runs when a survey is submitted * **Trigger Link Clicked:** runs when a trigger link is clicked * **Twilio Validation Error:** runs based on the Twilio Lookup response before sending an SMS or making a call. (Number Validation must be enabled in order for this feature to work.) **Events** * **Call Status:** Runs on outbound and inbound calls * **Email Events:** runs on specific email events **Social Media** * **Facebook Lead Form Submitted:** runs when the lead submits your Facebook Form * **Tik Tok Lead Form Submitted:** runs when the lead submits a form connected to your Tik Tok **Membership** * **Category Completed:** runs when a category of specified product gets completed * **Membership New Signup:** a customer.lead subscribed for a membership * **Offer Access Granted:** runs when access to offer is granted * \*\*Offer Access Removed:\*\*runs when access to offer is removed * **Product Access Granted:** runs when access to product is granted * **Product Access Removed:** runs when access to product is removed * **Product Completed:** runs when product is completed * **User Login:** runs when user logs in to membership **Opportunities** * **Opportunity Status Changed:** runs when the opportunity status is changed * **Pipeline Stage Changed:** runs when the pipeline stage is updated for the opportunity * **Stale Opportunities:** runs when opportunities are older than a set time duration **Payments** * **Invoice:** runs when an invoice is paid or sent **Shopify** * **Abandoned Checkout:** runs when the lead (shopper) does not complete the checkout * **Order Placed:** runs when the lead (shopper) places an order * **Order Fulfilled:** runs when an order is fulfilled ***NOTE:*** Many triggers include filter options which allow you to further specify the actions. For example, if you want the workflow trigger to run any time any form is submitted, you can keep the generic “Form Submitted” trigger, as shown below: {% embed url="" %} Or, if you want the workflow to only apply for a specific form, you can click “Add Filters” and choose the exact form you want the trigger to apply to: {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflows/list-of-workflow-triggers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.