# Workflows overview

A **workflow** is a small automation: "when *this* happens to a meeting, send *that*
message." You build one or more **steps** (each with a trigger and an action), attach
the workflow to the [event types](/help/event-types/overview) it should apply to, and
42min runs it. Manage workflows from [**Workflows**](/360/workflows).

## What it is

- A workflow has a **name**, an **on/off status**, a list of **steps**, and a set of
  **event types** it's attached to.
- Each **step** is a [trigger + action](/help/workflows/triggers-and-actions) — e.g.
  "24 hours **before** the event, **email the invitee** this reminder."
- The same workflow can cover several event types; an event type can have several
  workflows.
- 42min ships nothing automatically: the booking *confirmation* email is always sent,
  but reminders and follow-ups only happen if you set up a workflow for them.

<Screenshot
  src="/help/screenshots/workflows/list.png"
  alt="The Workflows page in the 42min dashboard, showing a 'Reminder + follow-up' workflow that's active, has 2 steps, and is attached to the 'Intro call' event type"
  caption="Each workflow shows whether it's active, how many steps it has, and which event types it's attached to."
/>

## When to use it

- Cut no-shows with a reminder a day (and an hour) before.
- Send a follow-up after the meeting — next steps, a recording, a feedback link.
- Tell the host something extra when a booking comes in or gets canceled.

## How to do it

1. Open [**Workflows → Create Workflow**](/360/workflows).
2. Name it and add **steps** — for each, pick the [trigger and action](/help/workflows/triggers-and-actions)
   and write the message.
3. Attach the workflow to the **event types** it should run for.
4. Turn it **on**. (You can also attach a workflow from the event type's *Workflow* tab
   — see [the editor overview](/help/event-types/one-on-one#the-event-type-editor).)

## Common pitfalls

- **Set up but nothing sends.** Check the workflow is **on** *and* attached to the
  event type in question — both are required.
- **Reminders for a meeting that's hours away.** A "before event" step won't fire if
  the booking is created inside its lead time (a 24-hour reminder can't be sent for a
  meeting booked 2 hours out). That's expected.
- **Duplicate messages.** If two workflows attached to the same event type both send a
  reminder, the invitee gets two. Keep one reminder workflow per event type.
- **SMS needs phone numbers (and an opt-in).** An SMS step only reaches invitees who
  provided a phone number; respect the SMS opt-in setting on the event type.