> ## Documentation Index > Fetch the complete documentation index at: https://help.hoopai.com/llms.txt > Use this file to discover all available pages before exploring further. # Automation > No-code workflow builder, 100+ triggers, actions, if/else branching, SMS campaigns, Zapier and Make integrations, and drip sequences. The HoopAI Platform's Automation suite lets you build workflows that trigger on any event — form submissions, appointments, contact changes, and hundreds more — then automatically execute actions like sending SMS, booking appointments, updating contacts, and more. Automation overview Core concepts and getting started with your first workflow Navigate the drag-and-drop canvas, steps panel, and builder settings Over 100 triggers including contacts, appointments, payments, and social media Send messages, update records, charge payments, and integrate with third-party apps Pre-built workflow templates you can copy and customize If/Else branching, math operations, AI actions, and premium integrations Advanced actions for AI, integrations, and data operations Links that fire CRM actions when clicked inside emails or SMS Debug failed steps, review execution logs, and fix common errors Send bulk SMS messages to contact lists with personalization Connect HoopAI to thousands of apps via Zapier Control how contacts enter and re-enter workflows Pause workflows until a condition is met or a time has elapsed Branch workflow paths based on contact data, events, or time Skip ahead in a workflow when a contact achieves a defined goal View the full execution history for any contact in a workflow Track enrollments, completions, and action-level performance metrics Trigger workflows from external systems using webhook payloads Send data from workflows to external systems via HTTP requests Connect HoopAI to Make (formerly Integromat) scenarios Organize workflows into folders for easier management Save and share reusable workflow templates across accounts Send time-spaced content sequences to nurture contacts over time ## Getting started Go to **Automation > Workflows** and click **Create Workflow**. Start from scratch or choose a recipe to get a pre-built template. Click **Add New Trigger** and choose what event starts the workflow — such as a form submission, appointment booked, or contact tag added. Add actions in sequence — send an SMS, wait a set time, check an If/Else condition, update the contact, or call an external webhook. Use the **Test Workflow** button to manually fire the workflow for a specific contact. Review the execution log to confirm every step ran correctly. Toggle the workflow from **Draft** to **Published**. The workflow is now live and will fire whenever the trigger condition is met. ## Frequently asked questions A workflow is a sequence of automated actions that runs when a specific trigger event occurs. For example, when a contact books an appointment (trigger), the platform can automatically send a confirmation SMS, tag the contact, and notify your team (actions) — all without manual effort. A single workflow can have multiple triggers. Each trigger can have its own filters so the same workflow handles different entry conditions while running the same action sequence. Yes, if the workflow's re-entry setting is enabled. This is useful for recurring automations such as appointment reminders or birthday messages. By default, re-entry is disabled so a contact only runs through a workflow once. A workflow in Draft mode will not fire even if a trigger event occurs. Only Published workflows are active and processing contacts. Switch a workflow to Draft when you need to make changes, then republish when ready. Use the Test Workflow button in the builder to manually trigger the workflow for a specific contact without waiting for a real event. Review the execution logs immediately after to confirm every step ran as expected. A drip sequence is a series of messages spaced out over time, typically used for nurture campaigns. A workflow is more general — it can include branching logic, CRM updates, webhooks, and conditional paths. Drip sequences are often built inside workflows using Wait actions between message steps.