Workflows
A workflow does routine work for you when something happens: it sends an email, waits, checks something, updates the booking. Build one step by step in the editor, start from a recipe, or describe what you want to the AI Assistant.
The Workflows page
Section titled “The Workflows page”Click Communications → Workflows in the sidebar. Each workflow shows its name, a summary of what it does, and the emails it sends.
- The switch shows whether a workflow is Active or a Draft. Drafts never run.
- Open Editor opens it (on a phone, View steps).
- The … menu has View runs, Edit workflow and Delete.
Under your workflows, Start from a recipe lists ready-made workflows.

Creating a workflow
Section titled “Creating a workflow”Click New Workflow. The New workflow dialog has two tabs.
From a recipe
Section titled “From a recipe”Pick a recipe and click Use this. It’s added as a draft with your own copies of the emails it sends: review the steps, then activate it. Recipes you’ve saved yourself are under Your saved recipes. Some recipes ask for a client page first.
On a team account, the recipes also include Find and confirm a provider: it asks the client’s preferred providers in turn and flags the booking if nobody confirms. See Ask preferred providers in turn.
When two recipes do the same job and you already use one of them (for example Bridal journey: enquiry to booking and its (team) version), the other’s card says so: use one, not both, or the client hears twice.

The bridal journey recipes
Section titled “The bridal journey recipes”Five recipes, all named Bridal journey, take a wedding from enquiry to the day itself. They work together, so add the ones you want:
- Bridal journey: enquiry to booking (or … (team) on a team account): welcomes the enquiry, sends your quote when you mark the booking Proposed, reminds the client after a week, then confirms the booking once they accept. With invoicing on it sends the invoice to secure the date first, reminds them after a week if it isn’t paid, and flags the booking if it’s still unpaid three weeks later. The team version first checks who’s free on the date with Check who’s free, and flags the booking if nobody is. Use one of the two.
- Bridal journey: trial details: emails the trial’s date, time and place whenever a trial date is set.
- Bridal journey: final check-in: 30 days before a booked wedding, asks the client to confirm their details, reminds them after a week, then sends their day-of schedule. If they still haven’t answered two weeks after the reminder, the booking is flagged so you can check the details with them and send the schedule yourself.
- Bridal journey: balance invoice (with invoicing on): 21 days before a booked wedding, invoices whatever is left of the agreed price. Add Invoice Overdue Reminder to chase it.
They come with their own emails and a Wedding Quote Page, copied to your templates when you add them. Before you activate them:
- Attach your brochure to the welcome email: open your copy of Wedding Enquiry Welcome in Templates and use Attach from Files (see Attaching files). The step that sends it is called Send welcome email (add your brochure) as a reminder.
- Booking minimum: the welcome email says “Our booking minimum is…” on a line of its own. If you haven’t set one in Settings › Pricing, delete that line, or it reads blank.
- Trials: the quote email and page each have a link for the client to choose trial dates. Only an upcoming wedding can be sent one, so the quote step stops for any other booking: these recipes are for wedding enquiries. An appointment booking ends the workflow straight away. If you don’t offer trials, delete the trial line and button from Wedding Quote and Wedding Quote Page.
- Team members needed: the quote page shows how many team members the day needs, worked out from the ceremony time and party size. If you work alone, delete that line.
- Deposit and trial length: set your deposit and trial length in Settings › Pricing.
- Send the quote by marking the booking Proposed. If you send the quote yourself instead, that marks the booking Proposed too, and the recipe doesn’t send it again while its price hasn’t changed (see Quotes you’ve already sent). Use either this recipe or Quote to booking, not both.
- When you confirm a trial, untick Email {client} that the trial is booked, or the client gets that email and the trial details too.
- For a reminder before the trial, add a workflow that starts Days Before Trial.
The separate check-in and balance invoice recipes start a set number of days before the wedding, so a booking made less than 30 days (or 21 days) before its date doesn’t get them. Send those yourself. A quote that’s never marked Proposed within 29 days, or never accepted within four weeks, simply ends the workflow.
Full team booking
Section titled “Full team booking”On a team account, Full team booking runs the whole journey for one wedding in a single workflow, instead of the separate Bridal journey recipes:
- Welcomes the enquiry, checks who’s free on the date, and flags the booking if nobody is.
- Sends your quote when you mark the booking Proposed. The quote shows a price for each tier with someone free, and the couple picks one when they accept. If the people already assigned are in different tiers, it shows one price with each person at their own tier’s prices instead. A week without an answer sends a reminder.
- With invoicing on, it sends the invoice to secure the date (the deposit, if you take one), reminds them after a week, and flags the booking if it’s still unpaid three weeks later. Once it’s paid, or straight after acceptance with invoicing off, the booking is marked Booked and the couple gets a confirmation.
- Asks the couple’s preferred team members in turn, only those in the tier they chose. Each request says how many people need their service and by when. If nobody confirms, the booking is flagged and you’re emailed; once you assign someone, the couple and the team member are introduced.
- 30 days before the wedding, with invoicing on, invoices the balance, due 21 days before the wedding.
- Then asks the couple to confirm their details, reminds them after a week, and sends the day-of schedule once they have. If they still haven’t answered two weeks after the reminder, the booking is flagged.
A booking made less than 30 days before the wedding gets steps 5 and 6 straight away, and its balance is due 9 days after it is sent.
The checklist above applies to it too (brochure, booking minimum, trials). Also:
- Use it instead of the Bridal journey recipes (enquiry to booking, final check-in, balance invoice) and Find and confirm a provider, not as well, or the couple and your team get some emails twice. Add Bridal journey: trial details alongside it: trials are dated separately, so a workflow can’t wait for one while it runs the rest.
- Each wedding keeps the version of the workflow it started with, which can be months. Changes you make reach new bookings only.
- A booking with no wedding date stops at the 30-day wait. Add the date, then use Retry step, or Skip it.
Start from scratch
Section titled “Start from scratch”Enter a Workflow Name and an optional description, then click Create Workflow. On a phone you can only start from a recipe.
The workflow editor
Section titled “The workflow editor”The editor lists the start (“When…”) and then each step in the order it runs.
- Use + between steps to add one.
- Click a step to open its settings in place; changes save automatically. You can give a step a Step name.
- Use the arrows on a step to move it up or down, or Delete step in its settings to remove it.
- An If splits into a Yes path and an Otherwise path. The steps below the If run after whichever path was taken. Ifs can sit inside other paths.
- A path can End here when nothing more should happen on it.
To edit, you need a computer or a tablet turned sideways. On a phone the editor shows the steps read-only.

When a workflow starts
Section titled “When a workflow starts”Click the “When…” card at the top and choose what it Starts when:
- A booking’s status changes: to one of the statuses you choose (choose at least one).
- A client sends an enquiry: through your enquiry form.
- You add a booking yourself.
- A booking is rescheduled: its date changes.
- A provider is assigned: a team member is assigned to a booking, however they were assigned (team accounts only).
- A trial date is set: a booking’s trial gets a date, or its date or time changes. It doesn’t start for the trial Knotless adds by itself when a client asks for one on your enquiry form, or for a cancelled, declined or completed booking.
- A deposit is paid: a client pays their deposit invoice in full (with invoicing on). The booking is moved to Booked first.
- A client confirms their details, or you accept the changes they sent. See Confirm your details.
- A client sends a questionnaire: the first time a client sends one of your questionnaires. Changing their answers afterwards doesn’t start it again.
- Only when you run it: you run the workflow by hand.
- Days before the event: a set number of days before the event.
- Days after a booking is created: a set number of days after the booking was created.
- A booking stays in a status: a set number of days after the booking was created, if it’s still in one of the statuses you choose, such as an enquiry nobody has replied to.
- Days before a trial: a set number of days before each dated trial.
The last four are checked once a day, every morning.
To let the client choose their trial date, send an email with {{trial_request_link}}, then Wait Until the client acts or the status changes › A trial date is set: it carries on once you confirm one of their dates. Add a step for when nothing happens in time to remind them. If the client couldn’t choose a date when the step runs (your trial date settings leave none, the trial is already booked, or a wedding abroad has it the day before), the email or page still goes with only the trial parts left out (see Email templates), so a quote that carries the link is never held up. The step says so on the timeline, for example “The trial dates button was left out: there are no dates left for the client to choose.” An email that only asks the client to choose trial dates (the link is its only button or link, and its subject or opening heading mentions the trial), like this one, isn’t sent then: the step is skipped and says why, for example “Not sent: this email only asked the client to choose trial dates, and she can’t right now (the trial is already booked).”
For a trial reminder, use Days before a trial rather than a long wait in an A trial date is set workflow. If the trial moves, the waiting workflow follows it and the move starts the workflow again, so the client would get two reminders.

Step types
Section titled “Step types”Clicking + opens the add-step menu. Its groups and steps are:
- Message the client: Email (send one of your email templates; see Who an email goes to), Link page (send a client page as a secure link), Document to read, Ask the client to confirm their details (an email step: choose a template that contains
{{confirm_details_link}}), Send a questionnaire (emails the client a link to one of your questionnaires, with an optional message), Ask for a review. - Wait: For a time, Until days before or after the event, Until days before or after the trial, Until the client confirms their details, Until the client sends a questionnaire, Until the client acts or the status changes (a status change, terms accepted on a page, a trial date being set, the client confirming their details, or, on team accounts, a provider being assigned).
A wait until days before or after the trial carries on at 9am on that day, and follows the trial if it moves. A booking with no trial date can’t use it: the step stops with “This booking has no trial date, so this wait can’t be worked out.” A trial date is set carries on straight away when the booking already has a trial date coming up.
The client confirms their details carries on straight away when they’ve already confirmed since they were last asked. To check in a month before: start a workflow with Days before the event (30 days), add Ask the client to confirm their details, then Until the client confirms their details, with If nothing happens sending a reminder (see When nothing happens). An If can also check Details Confirmed.
Send a questionnaire is skipped, with the reason on the timeline, when the client has already sent that questionnaire, a planner is the booking’s main contact (the questionnaire is the couple’s), the client has no email address, or the questionnaire is turned off. A workflow can’t be activated while its questionnaire is turned off or deleted, and a questionnaire a workflow sends can’t be deleted until you remove it from the workflow. Until the client sends a questionnaire carries on straight away when they’ve already sent one for the booking.
- If: If… (choose what happens on each path); see If blocks.
- Update the booking: Change status, Add a checklist, Add to my calendar, Flag for review (see Flag for review).
- Assign (team accounts only): Check preferred providers’ availability, Assign a preferred provider, Ask preferred providers in turn. See Preferred providers.
- Stop: End here (this path stops), offered at the end of a path.
Add to my calendar emails you links to add the booking to Google Calendar, Outlook or another calendar. It doesn’t need the Google Calendar connection.
If blocks
Section titled “If blocks”To add an If, click + where you want it and choose If… (choose what happens on each path), then pick what to check.
- The Yes path runs when the check is true; the Otherwise path runs when it isn’t.
- Add steps to each path with the + inside it.
- Steps below the If run after either path: the two paths join back together.
- Ifs can go inside a path, to check something else on that path only.
- To stop a path early, add End here (this path stops) at its end, from the Stop group. The steps below the If then don’t run on that path.
- Some steps have their own two paths and work like an If. Ask preferred providers in turn has Provider confirmed and No one confirmed (see Ask preferred providers in turn).
- If an If or a step with paths is skipped (for example with Skip and continue after it failed), neither path runs, and the steps below it don’t run either. A wait is the exception: skipping it counts as the thing having happened, so its When it happens path runs (see below).
When nothing happens
Section titled “When nothing happens”A Wait for event step waits for something, such as a payment or a status change, for as long as its Timeout allows. In its settings, If nothing happens in time decides what happens when the timeout passes first:
- Stop, so I can retry or skip it (the default): the workflow stops at the wait, you’re told, and you can retry or skip it (see Running a workflow and its history).
- Follow a different path: the wait gets two paths, like an If. When it happens runs if the thing happens in time; If nothing happens after 7 days (your timeout) runs if it doesn’t. For example, send a reminder when a deposit hasn’t been paid after a week, then wait again.
While the If nothing happens path has no steps, a timeout still stops the workflow so you can retry or skip it. To stop quietly instead, add End here to that path. Steps below the wait run after either path. Changing the setting back to Stop removes the steps on the If nothing happens path, after asking you.
Just before taking the If nothing happens path, the workflow checks once more whether the thing has happened (for example, the invoice was paid), so a reminder isn’t sent by mistake.
An invoice you mark as received counts as paid: a workflow waiting until it’s paid carries on, just as if they’d paid it by card.
An If can check:
- Booking: Booking Status, Booking Type (Event or Appointment), Total Price, Event Date, Booking Notes, Days Until Event, Days Since Created, Event is in Past, Event is in Future.
- Client: Client Email, Client Name, Client Phone, Has Email, Has Phone.
- Event: Trigger Type, Is Manual Trigger, Is Status Change.
- Preferred provider: Any Preferred Provider Available (for team accounts).
Deposits and balances
Section titled “Deposits and balances”With invoicing on and a deposit set in Settings › Pricing:
- A Create Invoice step has an Amount: Full price, Deposit or Balance (the agreed price less everything already invoiced). For example, Days before the event (21) then Create Invoice with Balance sends the rest three weeks before the wedding. A balance with nothing left to bill is skipped and the workflow carries on.
- An accepted quote already gets its deposit invoice by itself, so a Full price step on such a booking sends the deposit instead (or nothing, if it was already sent). Use Balance for the rest.
- Until the client acts can wait until The deposit is paid. If it’s already paid, it carries on straight away.
- An If can check Has Deposit (the booking has a deposit invoice) and Deposit Paid. Is Fully Paid counts the whole agreed price, so a paid deposit alone isn’t fully paid.
- Emails can use Deposit Amount (
{{deposit_amount}}); Balance Due ({{balance_due}}) is what’s left of the agreed price once a deposit has been sent.
Who an email goes to
Section titled “Who an email goes to”In an Email step, Send To chooses who the email goes to: Client, Provider (You), Both, or, on team accounts, Assigned provider(s). Client means the booking’s main contact: the couple, or their planner when you’ve made her the main contact.
- Assigned provider(s): each provider assigned to the booking gets their own copy, and the assigned-provider merge fields in it describe them. If no one is assigned yet, the step is skipped (“Not sent: no one is assigned to this booking yet.”) and the workflow carries on.
- For service (with Assigned provider(s)): pick a service so that only the provider assigned for that service gets the email, and the assigned-provider details in it are theirs. All services sends to everyone assigned. If nobody covers that service, the step is skipped.
See Assigned provider fields for what the email can say about them.
Quotes you’ve already sent
Section titled “Quotes you’ve already sent”A Send Page step with a quote page (one with a price and an accept button) doesn’t send the client a second copy. It’s skipped, and the workflow carries on, when you’ve already emailed the client that same page for this booking, and it’s either:
- still open, at the price the booking has now, or
- accepted by the client.
This covers the usual case: you send the quote by hand, which marks the booking Proposed (see Stages and the next step), and that starts the workflow. It doesn’t matter who sent it (you, a team member or another workflow). Only the same page counts, so send the quote page the workflow uses; a different page sent (a priced contract, say) doesn’t stop the step. The run’s timeline says when the quote went, for example “Not sent: the same quote went out on Wednesday, 14 October 2026.” If the price has changed since, or the quote was withdrawn, expired or its email didn’t go, the step sends a new one. To send the same quote again anyway, resend it from Communications → Sent → Page links (see Page links).
If the client already accepted it, a Wait for the quote to be accepted straight after the step carries on at once, so they aren’t reminded about a quote they’ve accepted. If the step needs your approval, you’re still asked first.
Steps that need your approval
Section titled “Steps that need your approval”Switch on Requires Approval in a step’s settings to have the workflow pause there until you approve it. Waiting approvals show on the booking and on Home under Approvals waiting. Approve to carry on, or reject to stop that path.
Older workflows
Section titled “Older workflows”A workflow saved before this editor may have steps linked in a way it can’t show. It opens read-only, with its steps listed and a Start again button: that keeps its start and removes its steps, so you can add them back.
Workflow settings
Section titled “Workflow settings”The settings button (Workflow Settings) changes the workflow’s Name and Description. Changes save when you leave a field.
Saving as a recipe
Section titled “Saving as a recipe”Save as Template saves the workflow as a recipe you can reuse, with a Template Name, a description and an optional category. It then appears under Your saved recipes.
Building a workflow with AI
Section titled “Building a workflow with AI”Click AI Assistant in the editor and describe what you want: “Describe what to add or change…”. The assistant adds, changes or removes steps for you. Check what it did before you activate. It’s on the Premium and Team plans; team members need the AI Chat permission.
Example prompts:
- “When a booking is booked, send a welcome email, then wait 3 days and send a reminder.”
- “Send a follow-up email 1 week after an event is completed.”
- “When an enquiry comes in, wait 2 days, then if it’s still pending, send a nudge email.”

Previewing a workflow
Section titled “Previewing a workflow”Click Preview, choose one of your bookings (“Choose a booking to test…”), and see step by step what the workflow would do for it: which emails it would send, how long it would wait, and which path each If would take. Nothing is sent.

Activating a workflow
Section titled “Activating a workflow”A new workflow is a Draft. Click Activate in the editor (or turn on its switch on the Workflows page). Ready to go? checks every step and shows what the workflow will do before it goes live. If steps still need setting up, the editor shows them with links to each one.
Once active, the workflow shows Active: it starts whenever its start happens. Deactivate (or turning the switch off) sets it back to a draft straight away.

Bookings already inside the window
Section titled “Bookings already inside the window”A Days before the event workflow starts for each booking on the day that many days before it. Bookings already closer than that when you activate it would never get it, so Ready to go? offers Also start it now for the bookings already less than 21 days away (ticked), with how many and the first few names. Leave it ticked and it starts for them now, and from then on also for any booking made less than 21 days before its date, the next morning. Untick it to keep to bookings still far enough away. Imports you chose to keep out of these workflows stay out.
Running a workflow by hand
Section titled “Running a workflow by hand”Click Run in the editor, search for a booking by client or venue, and click Run now. Only active workflows run. Its progress then appears on that booking.
Seeing what ran
Section titled “Seeing what ran”Open a workflow’s … menu on the Workflows page and choose View runs: every time the workflow ran, newest first. Filter by All runs, Stopped, Failed or Waiting.
Each booking also shows its own runs in Workflow Activity, on its Team & automation tab. Expand a run to see its steps. Editing or deactivating a workflow keeps the step history of runs that already happened.
Coming up, and pausing a booking
Section titled “Coming up, and pausing a booking”Above it, Coming up lists what your workflows will do next for the booking and when: the next step of each run already going, and every scheduled workflow (such as Days before the event) that hasn’t started for it yet.
Pause stops automation for just that booking. While it’s paused, workflows don’t email, send pages or documents, invoice or ask for a review from that client, and no new workflow starts for the booking. Other steps, such as status changes and checklists, carry on. Resume turns it back on. Anything skipped while paused isn’t sent later: Coming up lists it under Skipped while paused.
When a booking is cancelled
Section titled “When a booking is cancelled”Cancelling a booking, declining it or marking it unavailable stops its workflows: nothing more is sent, and the run says why (“Stopped: the booking was cancelled.”). Any approval waiting for it is withdrawn, and a Needs review flag is cleared. A workflow that starts on the booking being cancelled (for example a “sorry to see you go” email) still runs, and so does one that waits for that status. Completed bookings carry on, so a review request after the event still goes.
Running a workflow and its history
Section titled “Running a workflow and its history”If a step fails or a wait times out with no If nothing happens path (see When nothing happens), that path of the workflow stops (the run shows Stopped) while other paths carry on. Nothing after the stopped step runs on that path. Home lists these under Workflows that stopped.
Once the cause is fixed (for example, you’ve added the client’s email address), open the run and choose:
- Retry step: runs only that step again and carries on down its path if it succeeds. Steps that already completed never run again.
- Skip and continue: marks the step done without running it and carries on. A skipped wait carries on down its When it happens path. You’ll be asked to confirm, because anything the step would have done (such as an email) won’t happen.
You can retry or skip for a limited time; the run shows until when. Retry and skip need permission to edit workflows. If a wait timed out because the thing it was waiting for has already happened, use Skip and continue: a retry starts waiting again and won’t see it.

Workflow limits
Section titled “Workflow limits”The Free plan includes 1 workflow; the “Enquiry Received” workflow every account starts with doesn’t count. Premium and Team have no limit. See Your plan.
On a team, members need the Workflows permission to see workflows, and the matching actions to create, edit or delete them.
Next: Sent.