> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/automations/sesami-flows.md).

# Sesami Flows

Sesami Flows is the automation layer for customizing notifications, integrations, and operational workflows around your bookings.

With Flows, you can trigger events at any stage of the customer's booking journey — before, during, or after their appointment.

## Flow Types

| Type        | What it does                    | Use case                             |
| ----------- | ------------------------------- | ------------------------------------ |
| **Email**   | Send custom HTML or text emails | Confirmations, reminders, thank-yous |
| **Webhook** | Send data to external platforms | Klaviyo, Slack, Zapier integrations  |

## Triggers

Every Flow starts from one of these booking events:

| Trigger                     | When it fires                                |
| --------------------------- | -------------------------------------------- |
| **Appointment created**     | A new booking is made                        |
| **Appointment rescheduled** | A booking is moved to a new date or time     |
| **Customer checked in**     | The customer is checked in for their booking |
| **Appointment started**     | The booking's start time is reached          |
| **Appointment cancelled**   | A booking is cancelled                       |
| **No show**                 | A booking is marked as a no-show             |

## Timing

Use the **When** setting to choose when the Flow runs relative to its trigger:

| Timing             | When it runs                                                      | Example                                          |
| ------------------ | ----------------------------------------------------------------- | ------------------------------------------------ |
| **Immediately**    | As soon as the trigger event happens                              | Booking confirmation on **Appointment created**  |
| **Before / after** | A set number of minutes, hours, or days before or after the event | Reminder 24 hours before, thank-you 1 hour after |

## Flow Ideas

* **Reminders** — send one or more email reminders before the appointment
* **Thank-you / survey** — send a follow-up after the appointment asking for feedback
* **Klaviyo integration** — trigger Klaviyo events for confirmation, reminder, cancellation, etc.
* **Multi-language notifications** — use conditions to send emails in the customer's language
* **Slack notifications** — notify your team via webhook when a booking is created
* **Auto-collect cancellation fee** — charge a fee on no-show via webhook automation
* **Auto-collect on check-in** — trigger payment collection when a customer checks in for their appointment

## Plan Limits

Flows are available on all paid plans:

| Plan    | Max Flows |
| ------- | --------- |
| Small   | 1         |
| Pro     | 6         |
| Premium | 9         |

{% hint style="warning" %}
Flows emails do **not** support `.ics` attachments (calendar files). Default Sesami notifications do include `.ics` attachments.
{% endhint %}

## Related

* [Email and Webhook as Action Types](https://help.sesami.co/automations/email-and-webhook-as-action-types.md) — detailed Flow configuration
* [Sesami Flows and Klaviyo](https://help.sesami.co/automations/sesami-flows-and-klaviyo.md) — Klaviyo integration via Flows
* [Sesami Flows and Omnisend](https://help.sesami.co/automations/sesami-flows-and-omnisend.md) — Omnisend integration via Flows
* [Notification Emails](https://help.sesami.co/notifications/notification-emails.md) — default Sesami notifications


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sesami.co/automations/sesami-flows.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
