The short answer

Triggers start workflows and actions perform work. The palette includes current and planned integrations, but activation is allowed only when the selected node has an executable, account-safe handler.

Availability: Available to accounts with access to this workspace or feature.

Step-by-step

  1. Choose one trigger

    Available choices include contact, form, booking, document, payment, SMS, WhatsApp and phone events. The inspector states when an event adapter is still required.

  2. Choose actions for the outcome

    Author email, SMS, WhatsApp, CRM task or opportunity, signature, payment, booking, video, staff and CRM tag steps as needed.

  3. Read capability warnings

    A node may be configurable and saveable while activation remains blocked. Treat the displayed requirement as mandatory, not informational.

  4. Use currently executable nodes

    Form submitted (`form.submitted`), booking cancelled (`booking.cancelled`) and booking rescheduled (`booking.rescheduled`) are connected triggers. Conditions, delays and CRM tag add/remove are executable actions in the current visual runtime.

  5. Validate before activation

    Validation checks node support, required configuration, connections, ports, cycles and reachability.

Was this guide helpful?

Send feedback about this guide