Anatomy of a Workflow #
A workflow has three parts: a trigger, an optional delay, and one or more actions. Open Workflows and choose New workflow to build one.
Triggers #
- Booking created
- Before meeting starts
- After meeting ends
- Booking rescheduled
- Booking cancelled
- Invitee marked as no-show
Actions #
- Send an email to the invitee, the host, or a fixed address such as a shared inbox
- Send an SMS to the invitee, where a phone question has collected a number
- Call a webhook endpoint with the booking payload
- Add a tag to the booking for later filtering
Variables #
Message bodies support placeholders that are substituted at send time, including {{invitee_name}}, {{host_name}}, {{event_name}}, {{start_time}}, {{meeting_link}}, {{reschedule_url}}, and {{cancel_url}}. Answers to custom questions are available as {{answers.slug}} using the question’s slug.
Scope #
A workflow applies to selected event types or to all of them. Team admins can create workflows that apply across every member’s event types, which is how a consistent reminder policy is enforced without asking each person to configure it.
Testing #
The Send test action delivers the rendered message to your own address using sample data, so you can check formatting and variable substitution before enabling the workflow.
