> For the complete documentation index, see [llms.txt](https://docs.shortcutco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shortcutco.com/readme/automations/steps-and-variables.md).

# Steps, message options, and variables

Every step you can add to an automation and what you set on it, the extra options on emails and texts, conditions on a step, and every variable you can put in a message.

This page is the reference for what goes inside an automation: the steps, the settings on each one, and the details you can drop into a message. For how to add a step, see [Build and publish an automation](https://docs.shortcutco.com/readme/automations/build-and-publish-a-campaign.md#add-steps).

Click the **+** between two cards on the **Workflow** canvas to add a step, then click the new card to open its settings. Changes apply as you type; click **Done** to close the panel.

## Steps

### Messages

| Step             | What it does    | What you set                                                                                                                                                                                                                                                                                                                                |
| ---------------- | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Email**        | Sends an email. | **To**: **Customer · email on file**, **Specific staff member**, and, when the automation's start involves a task, service, or visit, **Assigned staff** or **Assigned team**. **Starter wording** (optional) fills the message from a ready-made one. **Subject** and **Message**. Plus [More options](#more-options-on-emails-and-texts). |
| **Text message** | Sends a text.   | **To**: **Customer · phone on file**, or the same staff choices as email. **Starter wording** (optional) and **Text message** (up to 640 characters; a counter shows how many you've used). Plus [More options](#more-options-on-emails-and-texts).                                                                                         |

### Timing

| Step                | What it does                                                                      | What you set                                                                                                                                                                                 |
| ------------------- | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wait**            | Pauses for a set amount of time.                                                  | **Wait for**: an amount and a unit (minutes, hours, days, weeks, or months).                                                                                                                 |
| **Sending window**  | Holds the run until a chosen time of day and day of the week.                     | **From**, **Until**, and the **Days** it may continue (Mon–Fri 09:00–17:00 to start). Texts to customers still never go out before 8:00 AM or after 8:00 PM, whatever the window allows.     |
| **Wait for a date** | Pauses until a date on a record, such as a visit's date or an invoice's due date. | The **Record** and its **Date field**, then **Wait**: an amount, a unit, and **before the date** or **after the date**. If the date moves before the run gets there, the wait moves with it. |

**When a run reaches a Wait for a date late**, for example because a visit was booked the day before:

* With **before the date**, the run carries on at once as long as the date itself hasn't arrived, so that visit still gets its reminder. Once the date arrives, the run ends instead of sending something stale.
* With **after the date**, the message has to go on the day it's due. If the run gets there after the due time, the run ends.

### Actions

| Step                       | What it does                                                                                                                | What you set                                                                                                                                                                                                                                                                                                                                                       |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Task**                   | Adds a task to the customer's **Tasks** for your team.                                                                      | **Task title**, **Assign to** (**Unassigned**, **Assigned staff**, **Assigned team**, **Visit team lead**, or **Specific staff member**), **Due in** (how long after the step runs), and **Due at** (optional time of day, in the automation's timezone). **Visit team lead** is the lead of the visit's team; the task is unassigned if the run has no visit.     |
| **Notify team**            | Sends your team a notification. It arrives as a push notification and email, following each person's notification settings. | **Notify**: **Company admins**, **Specific staff member**, and, when available, **Assigned staff**, **Assigned team**, or **Visit team lead**. A **Title** and a **Message** (optional). **Open**: where the notification takes them when they tap it: **Default page**, or the **Customer profile**, **Estimate**, **Invoice**, or **Task** when the run has one. |
| **Internal note**          | Adds an internal note to the customer's timeline, from this automation.                                                     | **Note**. It can't be empty.                                                                                                                                                                                                                                                                                                                                       |
| **Tag**                    | Adds or removes a customer tag.                                                                                             | **Operation** (**Add tag** or **Remove tag**) and the **Tag**.                                                                                                                                                                                                                                                                                                     |
| **Field**                  | Sets or clears one of your custom fields.                                                                                   | **Record**, **Field**, **Operation** (**Set value** or **Clear value**), and the **Value**.                                                                                                                                                                                                                                                                        |
| **Copy into a field**      | Fills a customer custom field from another value the run knows, such as a visit's date.                                     | **Set field** and **From**. Only values that field can hold are listed.                                                                                                                                                                                                                                                                                            |
| **Update lead stage**      | Moves an unconverted lead to a stage.                                                                                       | **Move lead to**: **Lead** or **Prospect**. Only leads move; someone who is already a customer is left as they are.                                                                                                                                                                                                                                                |
| **Create a job**           | Adds a pending one-time job for a service at the customer's property. Schedule it from Jobs.                                | **Service**.                                                                                                                                                                                                                                                                                                                                                       |
| **Webhook**                | Sends the run's records to another system as JSON.                                                                          | **URL**. Only public `https://` addresses are allowed. If the other system doesn't answer with success, the action shows as failed with **Retry**.                                                                                                                                                                                                                 |
| **Stop other automations** | Ends this customer's other running automations.                                                                             | **Automations to stop**. Leave it empty to end every other automation running for this customer.                                                                                                                                                                                                                                                                   |

### Paths

| Step                     | What it does                                                                     | What you set                                                                                                                                                                                       |
| ------------------------ | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Branch**               | Splits the run in two depending on a condition.                                  | The **Condition**, then the steps under **True path** and **False path**.                                                                                                                          |
| **Wait for a condition** | Pauses until something becomes true, or time runs out.                           | The **Condition**, **Give up after** (how long to wait), then the steps under **When matched** and **On timeout**.                                                                                 |
| **Wait for a reply**     | Pauses until the customer texts back, or time runs out. Only text replies count. | **Give up after** (2 days to start), then the steps under **When they reply** and **No reply in time**. Steps on the reply path can check the reply's text, channel, and time in their conditions. |

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-88949250e71bf7e74cd697e0f2f3d1e970486cb9%2Fautomation-wait-for-reply-card.png?alt=media" alt="A Wait for a reply card on the Workflow canvas splitting into When they reply and No reply in time"><figcaption><p>Wait for a reply splits the run into two paths.</p></figcaption></figure>

## More options on emails and texts

Every **Email** and **Text message** step has **More options** at the bottom of its panel. It stays closed unless something in it is set.

| Option                              | What it does                                                                                                                                      |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Send as**                         | **Company** (the default), or a staff member. Sender variables use that person's name, and for email, replies go to them.                         |
| **Reply-to**                        | Email only, optional. The address replies go to, like *<office@yourcompany.com>*.                                                                 |
| **Only send during business hours** | Holds the message until 8:00 AM–6:00 PM, Monday to Saturday, in the automation's timezone.                                                        |
| **Add opt-out footer**              | Texts only. Adds *Reply STOP to opt out.* to the end.                                                                                             |
| **Skip if sent in the last … days** | Optional, 1 to 365. Skips the message if this same step already sent one to the same person in that many days. Leave it blank to send every time. |

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-793e8187ca0b609221e584de4da891353fef57c7%2Fautomation-email-more-options.png?alt=media" alt="An Email step&#x27;s settings with More options open: Send as, Reply-to, Only send during business hours, and Skip if sent in the last … days"><figcaption><p>More options on an Email step.</p></figcaption></figure>

## Only send when / Only run when

Any message or action step can have its own condition. In the step's panel, click **Add condition** under **Only send when** (on emails and texts) or **Only run when** (on other steps). If the condition isn't true when the run reaches the step, the step is skipped and the run moves on. **Remove condition** takes it off.

On the canvas, the card shows an **Only if …** label so you can see it at a glance.

Conditions use the same builder as starts and exits. See [Build conditions](https://docs.shortcutco.com/readme/automations/build-and-publish-a-campaign.md#build-conditions).

## Variables

Click **Insert variable** under an email's subject or message, a text message, or an internal note (or type `/` at the start of a word) to open the list, then search or pick one. Hover a variable to see an example, like *Example · Jordan*. Inserted variables show as labeled chips. Shortcut fills them in when the message is sent.

You only see the variables that fit the automation's start. For example, invoice variables need a start that involves an invoice.

| Group in the list | Variables                                                                                                                                                                                                                                                                                                   |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| (top of the list) | Today's date                                                                                                                                                                                                                                                                                                |
| **Customer**      | Customer first name, Customer last name, Customer full name, Customer email, Customer phone, Customer company name, Customer account balance, Saved card last four digits, Customer portal link, Payment-method link (save a card or bank account), Services paused for the season, Next season resume date |
| **Property**      | Property address, Property size (acres)                                                                                                                                                                                                                                                                     |
| **Company**       | Company name, Company phone, Company email, Company address, Company website, Company review link                                                                                                                                                                                                           |
| **Sender**        | Sender first name, Sender last name, Sender signature                                                                                                                                                                                                                                                       |
| **Forms**         | Intake form link                                                                                                                                                                                                                                                                                            |
| **Invoice**       | Invoice number, Invoice total, Invoice balance due, Invoice due date, Invoice link, Invoice payment link                                                                                                                                                                                                    |
| **Estimate**      | Estimate link, Estimate total, Estimate expiry date                                                                                                                                                                                                                                                         |
| **Job**           | Service name, Next visit date                                                                                                                                                                                                                                                                               |
| **Visit**         | Visit date, Visit time, Visit team, Visit service name, Products applied, Visit reason, Visit reason note (typed by staff), and for day-before automations only: Grouped reminder visit date, Grouped reminder services, Grouped reminder addresses                                                         |
| **Custom fields** | Your customer custom fields                                                                                                                                                                                                                                                                                 |

Good to know:

* Dates and amounts are written out for the customer: a visit date reads *Monday, October 5*, an invoice due date *October 5, 2026*, and an invoice total *$1,250.00*.
* If a detail is blank on the customer's record (for example, no company phone), it's left blank in the message. **Services paused for the season** and **Next season resume date** are blank for a customer with nothing paused for the season.
* **Payment-method link** gives each customer their own secure link to save a card or bank account and turn on autopay. It's made when the message is sent, and only for customers: for a lead, or if you haven't connected Stripe, the message isn't sent. See [Collect a card or bank account with a payment-method link](https://docs.shortcutco.com/readme/finances-invoices-and-payments/payment-method-links.md).
* **Visit reason** is the reason picked when the visit was skipped or canceled. **Visit reason note** is whatever your team typed with it, so only use it if you're happy for customers to read those notes.
* **Sender** variables use the staff member picked in **Send as**, or the person who published the automation.
* A variable Shortcut doesn't recognize doesn't stop you publishing. It shows under **Worth knowing** in the review and is left blank.

<figure><img src="https://2299783971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOhi7KtJ4vY1pDKwWu5SV%2Fuploads%2Fgit-blob-27788f7f8eae8a3784e0250b58f9213be8e5c0c0%2Fautomation-insert-variable-menu.png?alt=media" alt="The Insert variable menu open under an email message, with a search box, grouped variables, and an example tooltip"><figcaption><p>Insert variable shows an example of each one.</p></figcaption></figure>

## Related pages

* [Build and publish an automation](https://docs.shortcutco.com/readme/automations/build-and-publish-a-campaign.md)
* [Templates and starts](https://docs.shortcutco.com/readme/automations/automations-list-+-triggers-exact.md)
* [Automation results, activity, and receipts](https://docs.shortcutco.com/readme/automations/campaign-activity-and-receipts.md)
