Flow Builder

The flow builder is where you create and edit automations. An automation is a vertical flow: the trigger sits at the top, and the steps below it run in order every time the trigger fires.

There's no dragging or wiring involved. You click a step to add it, the builder lays the flow out for you, and you click any step card to configure it.

Create an automation

1. Go to Automations in your podcast's sidebar
2. Click New Automation

The builder opens with a trigger already in place. Only podcast Hosts and Producers can create and edit automations.

At your plan limit?

If your account is at its automation allowance (or you're on the Free plan, which doesn't include active automations), clicking New Automation opens upgrade options instead of the builder. See Plan Limits.

Find your way around

• Top bar: the automation's name (click it to type; it starts as "Untitled automation"), a save-status line, the Enabled switch, and the Test and Create or Save buttons.
• Left panel, "Add a step": the step library, grouped into Triggers, Actions, and Logic. Click a step to add it to the end of the flow. Clicking Event trigger selects your existing trigger instead, since every automation has exactly one.
• Center canvas: the flow itself. Each card shows a When, Then, or If badge and a one-line summary. Click a card to configure it.
• Right panel, "Configure node": the settings for whichever step is selected.

You can also add steps from the canvas: the dashed Add step button at the end of the flow (and at the end of each condition branch), or the small + that appears on the connector between two steps to insert one in between.

Each step card has an options menu with Move up, Move down, Duplicate, and Delete step. Zoom controls sit in the bottom-right corner of the canvas (40% to 200%, plus Reset).

Both side panels can be collapsed to give the canvas more room.

Configure the trigger

Click the trigger card and pick an Event. The choices come in four groups:

Group	Triggers
Event Triggers	Booking Confirmed, Booking Declined, Booking Canceled, Episode Published, Episode Scheduled, Episode Transcribed, Guest Research Ready, Guest Responded
Analytics Triggers	Episode Downloads Milestone, Download Spike Detected
Distribution Triggers	Listed on a directory
Time-Based Triggers	Before Recording, After Recording, Before Publish, After Publish, After Booking

Some triggers take extra settings:

• Time-based triggers ask for a Time offset: an Amount and a Unit (Minutes, Hours, or Days). For example, 24 hours before the scheduled recording.
• Episode Downloads Milestone asks for a Download threshold. It runs once per episode, the first time that episode's all-time downloads pass the threshold, checked hourly.
• Download Spike Detected asks for a Multiplier and a Minimum downloads floor. It runs at most once per day, when a day's downloads reach the multiplier times your show's 7-day average.

The trigger can't be deleted: every automation needs one to start.

Add your actions

Send email

Sends an email from one of your email templates.

• Template: which email to send. A preview of the subject line appears once you pick one.
• Send to: by default the email goes to the guest. Enter an address to send it somewhere else.
• CC emails: an optional comma-separated list.
• Email tags: clickable chips for {guest_email} and {guests_emails}. Click to copy, then paste into Send to or CC emails.

Webhook

Sends data to an external service, which pairs well with Zapier, Make, n8n, or your own endpoint.

• Webhook URL: where to send the request.
• HTTP method: POST, PUT, or PATCH.
• Custom headers: an optional JSON object, for example an authorization header.
• Payload template: the JSON body. Use Insert Tag to drop any magic tag at the cursor; tags are filled in when the automation runs.

Update field

Writes a value to the record connected to the run. Pick a Record, a Field to update, and a New value:

Record	Fields you can update
Episode	Title, Description
Booking	Status (can only be set to Completed)
Guest	Private notes

Text fields accept magic tags through Insert Tag. Fields that end up public (like the episode title) don't offer tags carrying private links or contact details.

If the run has no matching record (say, a booking field on an episode trigger), the step is skipped.

Add logic

Condition

A condition routes the flow down a True or False branch depending on a rule. Configure the Field, an Operator, and (for most operators) a Value.

Fields you can branch on: Guest Email, Episode Status, Booking Status, Booking Link, Number of Guests, Days Until Recording, Days Until Publish, and Meeting Link (which checks whether a meeting link exists yet).

Below the condition card, the canvas forks into True and False columns. Use each branch's Add step button to add the steps that should run only when that path matches.

Deleting a condition deletes its branches

Removing a condition step also removes every step on its True and False branches. The builder asks you to confirm first.

Delay

Pauses the flow before the next step. Set a Duration and a Unit (Minutes, Hours, or Days). For example: when a booking is confirmed, wait 1 hour, then send prep materials.

Save your automation

Click Create (for a new automation) or Save (when editing). The automation needs a name before it will save.

The save-status line under the name always tells you where you stand: it shows "Unsaved changes" while you have edits pending and "All changes saved" once they're stored. Creating a new automation takes you to its edit page.

Enable and disable

The Enabled switch in the builder's top bar controls whether the automation runs. New automations start enabled, so they're live as soon as you save (flip the switch off before saving if you're not ready).

You can also toggle any automation with the switch on its card on the Automations page. Disabled automations never run.

Test an automation

1. Save your automation first. The Test button is unavailable for unsaved automations ("Save the automation first to test it") and while you have unsaved edits ("Save changes before testing").
2. Click Test.
3. In the Test Automation dialog, pick the sample data the run should use. Depending on the trigger, that's an episode, a booking, or both.
4. Click Run Test.

You'll see "Test execution queued". Head to run history to see the result.

Manage automations from the list

The Automations page shows every automation with its trigger, action icons, and on/off switch. From there you can:

• Search and filter by Trigger or Status (Enabled or Disabled)
• Edit an automation (the pencil icon) to reopen it in the builder
• Delete an automation (the trash icon). The confirmation warns you: deleting also removes its scheduled jobs and cannot be undone.
• Open History to see past runs

What's Next?

• Switch on the starter automations that come with your podcast
• Write the email templates your send-email steps use
• Browse magic tags to personalize every message
• Check run history to see your automations in action