> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/workflows/create-a-workflow.md).

# Workflows

Set up automated Slack, email, and webhook notifications.

Use a workflow to send a notification or run another action when a booking or routing event happens. Workspace admins manage workflows.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2Fg8I4CqpnjijxY3XhMJ72%2FCleanShot%202026-09-10%20at%2020.45.09%402x.png?alt=media&amp;token=1b8d34a5-01e6-421c-9e3e-3156c4fc10f5" alt=""><figcaption></figcaption></figure>

For example, notify the host when a meeting is booked through a particular group link.

1. Open **Workflows** and click **New Workflow**.
2. Give it a name that describes the outcome.
3. Under **Trigger**, choose **When a meeting is booked**.
4. Under **Scope**, select the resource type, then decide whether the workflow applies to all resources of that type or selected ones.
5. Under **Action**, configure the notification or action and its content.
6. Create the workflow, review it, and activate it when ready.

Meeting triggers support Form Routers, Click Routers, personal links, group links, and Outbound Routers. Submission and no-booking triggers apply to Form and Click Routers; disqualification applies to Form Routers.

## Choose when it runs

Meeting workflows can run when a meeting is booked, rescheduled, cancelled, completed, or marked as a no-show. Use a before-meeting or after-meeting trigger for a timed action, and set its offset in minutes.

For **prospect no booking**, the workspace’s [No booking timeout](/settings/workspace-settings/scheduler-settings.md) determines the wait. This trigger is available for Form and Click Routers.

## Choose an action

Email the assignee when the host needs the information. Send an email to specific people for another recipient list. Use Slack for a channel notification, or a webhook when another system needs to receive the event.

Use the editor's available variables for meeting and prospect details. The available triggers, sources, and actions depend on the combination you choose.

Slack needs a connected integration and access to the destination channel. A webhook needs a receiving endpoint; ask the person responsible for that system for its URL and any required authentication settings.

## Check before enabling

Use the workflow’s preview and test options to check the output. Choose sample data or find an existing booking by its title, guest, reference, or booking URL. Existing-booking results are limited to the workflow’s selected source and scope. A preview shows content; sending a test can deliver a message or call an external system, so review the destination first.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FqlsZy951J1QTdluWoW7o%2FCleanShot%202026-09-10%20at%2020.46.35%402x.png?alt=media&amp;token=19ef6e7a-14da-4629-a322-2a2ce70968d8" alt=""><figcaption></figcaption></figure>

After enabling the workflow, check **History** and open an execution to review individual action results. If an action did not run, review the execution details for its result. Confirm the workflow is active and that the event and source match its scope.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FlJws3sfiTVKjG4LRflZn%2FCleanShot%202026-09-10%20at%2020.47.16%402x.png?alt=media&amp;token=0d4a273d-eadb-4b60-b3c6-b14b0e49b562" alt=""><figcaption></figcaption></figure>

**Duplicate** copies the workflow and its source filters. Review the scope and destinations before enabling a copy. For receiving systems, see [Webhook payloads](/workflows/webhook-payloads.md).


---

# 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://help.distro.so/workflows/create-a-workflow.md?ask=<question>&goal=<endgoal>
```

`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.