Skip to main content
When an automation’s trigger fires and its conditions are met, it performs the actions listed under Then. There are three types: send an email, send a text message, or create a task. An automation can run more than one action: click Add Action for each one you need.
This page covers features gated by Admin-tier permissions — typically Settings access. Admins have these by default; your administrator can adjust who has them in Settings > Team.

Template variables

Email subjects, email bodies, and SMS messages can include variables like {{customer.name}} that resolve when the automation runs. The automation builder shows the available variables under each message field. Click one to insert it at the cursor. Use that panel rather than typing a variable from memory. The set it offers is the one that will resolve for the automation you’re building: order automations get order tokens, event automations get event tokens, both get the customer set, and an action repeating for each event contact gets a {{contact.*}} set as well.

Sending to each contact in turn

When an event automation action repeats for each Event contact, the {{contact.*}} variables resolve to the current recipient’s details, so each fan-out message is addressed to that specific person. Use {{customer.first_name}} when you mean the event’s primary customer, who is the same for every message, and {{contact.first_name}} when you mean the person the current message is going to. Most fan-out messages want {{contact.*}} for the greeting and {{customer.*}} when referring to who booked the event. The panel only offers the {{contact.*}} set when the action repeats for each event contact.
If a customer or contact doesn’t have a value for the variable you’ve used, such as no phone number, it comes through as a blank space. The preview fills in sample values, subject included, so you can check the wording before you save. Send yourself a test before you rely on a new message.
Loops use a different syntax (%name%, %quantity% and so on) and only work inside an action that repeats; see Loops below.

Send an email

The most common action. When the automation fires, an email goes out to the customer on the order or event, wrapped in your standard notification layout and branding.

Setting it up

1

Write the subject

Type the subject line. Insert variables from the picker so each email is personalised. See Template variables.
2

Write the message

Compose the email body. Variables work here too. You don’t need to recreate headers, footers, or styling, because the message is dropped into your branded notification layout.
The email goes to the customer recorded on the order or event. If you need to notify a team member instead of (or as well as) the customer, set up a separate notification event for that; see Notifications. Automation emails and texts aren’t sent to a customer who has opted out of notifications or whose record is closed, or to the client of an order made from an event. Each is recorded as held back in the message history. When the customer has only opted out, their event contacts still receive messages from event automations. If the email action has a loop on it, the body is rendered once per loop item, with loop variables like %name% filled in for each one. See Loops for the full variable list per loop type.

Send a text message (SMS)

Sends a text message to the customer’s phone number when the automation fires. Useful for time-sensitive notifications like delivery updates.

Setting it up

Enter the SMS content. The same variables work in SMS as in email; see Template variables. Keep the message short: standard SMS messages are 160 characters, and longer ones are split into multiple parts and use multiple credits, so insert variables sparingly. The SMS sends to the phone number on the customer record by default. If the action has an Event contact loop on it, the SMS sends to each contact’s phone instead, once per contact. If a phone number is missing, the automation logs that the SMS was skipped and moves on. Your order or event isn’t blocked.
Text messages use SMS credits from your plan. If a phone number is missing or credits run out, the automation logs the skip and the rest of your workflow keeps running.

Create a task

Automatically creates a task when the automation fires. This is great for making sure preparation steps, follow-ups, or checks don’t get forgotten.

Setting it up

A new action starts as a task. Fill in:
  • Task name, such as “Prepare arrangement” or “Call {{customer.name}} to confirm the details”. Variables work here.
  • Description and Category, if your team needs them.
  • Priority and Time. Leave Time blank for a task that can be done at any time of day.
  • Default assignee, the person the task is given to when it’s created, or Nobody.
You can also give the task a checklist, with one item for each product on the order or each recipe on an event’s quotation. See Loops below.

Scheduling the due date

Under Due, choose when the task is due:
  • When the automation runs: due straight away.
  • Before a date: due that many days before the date you pick, such as the fulfilment date or the event date (like a prep task 7 days before).
  • After a date: due that many days after it (like a follow-up 14 days after).
Digital Florists works out the due date when the automation fires. If the order or event date changes afterwards, the task’s due date doesn’t recalculate. The created task appears on your Tasks board and can be assigned, completed, and tracked like any other task.

Scheduling when an action runs

An action timed against a date doesn’t run the moment the trigger fires. It waits and runs on the day it falls due, so a thank-you set to go out 10 days after a wedding goes out on that tenth day. A message still waiting sits on the Scheduled Messages card in Settings > Advanced > Automations until then, and you can cancel it there. A message waiting on an order that’s cancelled before it’s due isn’t sent.

Loops

Loops let you repeat an action for each item in a list. Tick Repeat for each item on the order on an order automation, or Repeat for each recipe, ingredient or contact on an event automation, then choose what to repeat it for under Repeat for each.

Loop variables

Inside a loop, the message body is rendered once per item with the %variable% values filled in for that item. Each loop has its own variable set: Outside a loop, use the {{ }} variables from Template variables instead. The two syntaxes are intentional: {{ }} refers to the order or event the automation fired on, %% refers to the current item inside the loop.

How loops work with emails

The email is sent once per loop item with the loop variables filled in. Three of the loops (items, recipes and ingredients) all send to the customer recorded on the order or event, with a different message each time, so the customer may get several. The Event contact loop is different, as below.

Event contact loop: sends to each contact in turn

The Event contact loop is the only loop that changes who the email or SMS is sent to. For each contact on the event:
  • The email goes to that contact’s email address (not the event customer’s)
  • The SMS goes to that contact’s phone number (not the event customer’s)
  • The {{contact.*}} variables from Sending to each contact in turn resolve to the current recipient’s details, so the greeting reads “Hi Sarah” for the bride and “Hi Tom” for the groom on the same automation
  • A contact with no email address won’t get the email, and a contact with no phone number won’t get the text. The automation carries on to the other contacts either way. Check every contact on the event has the details you need before you rely on the fan-out
Use it for any “fan out” scenario: send the same reminder to the bride, groom, and venue coordinator without writing three automations.

How loops work with tasks

When you repeat a create task action, tick Group the repeats into one task with a checklist and Digital Florists makes one task with a checklist item per loop entry. For example, if an order has three products and you repeat for each item on the order, the task gets a three-item checklist, one for each product, with %name% x %quantity% filled in per line.
Loops are especially powerful for event automations. You can automatically create a prep task with a checklist of every recipe that needs to be made for a wedding, send the client an email listing every ingredient in their quotation, or fan a reminder out to every named contact on a funeral.

Common questions

Yes. Click Add Action to chain as many actions as you need onto a single automation. Each action runs in turn when the trigger fires and the conditions match.
There’s no dry-run mode. Create a test order or event and let the automation fire on it, then check the Logs to confirm it worked.
The subject and message you write are wrapped in your branded notification layout, with its header, footer, colours and signature, before being sent. You write the content; Digital Florists handles the styling. Adjust the layout itself in Notification Templates.
Yes. %name%, %quantity%, %price%, %note%, and the contact-specific ones (%first_name%, %email%, %phone%, %label%) all resolve in SMS the same way they do in email. The Event contact loop also sends the SMS to each contact’s phone in turn. Just keep the message short, since each loop iteration is a separate SMS and counts against your credits.
The task keeps its original due date. The due date is worked out when the automation fires and doesn’t recalculate if the order or event date shifts afterwards.

What’s next?

Triggers & Conditions

Control when your automations fire.

Logs & Troubleshooting

Check what your automations have done and fix issues.

Notifications

Manage the email templates your automations use.

Tasks

View and manage tasks created by automations.
Last modified on October 14, 2026