July 2026 · Available on all plans.
What Shipped
Three changes to how automations are organized and triggered. Automations now opens as a list view, and clicking a flow opens it on its own dedicated canvas. The trigger picker adds Manual audience, which runs a saved audience through a flow on demand. And an automation’s trigger can now be changed without rebuilding the rest of the flow.A List First, Then a Dedicated Canvas
Opening Automations shows every flow in one table: name, status, and trigger, with summary counts (total, live, draft) at the top. Search the list, manage trigger events with the Triggers button, or start a new flow with New automation. Click a flow and it opens on its own canvas. Each automation has a dedicated canvas, so what you’re editing is always exactly the flow you selected, never a shared surface with other automations.Change the Trigger Without Rebuilding
Click the trigger node to open its config panel. Alongside editing the selected trigger, Change trigger switches the flow to a different audience or a different event trigger entirely. The emails, waits, and splits stay exactly as you built them.A Saved Audience as a Trigger
The trigger picker now offers Manual audience alongside integration events and custom HTTP triggers. Pick a saved audience and the automation becomes a one-off: instead of listening for events forever, it runs every contact in that audience through the flow (waits, filters, splits, and sends included) when you launch it. There’s nothing to publish and leave running. The trigger node shows the audience, its filter query, and the live contact count; the list shows Sending while a run is in flight and Sent when it completes. Use it for launches, event invites, or any sequence where the follow-up depends on what happened in the first email.From the API
Manual-audience automations launch withPOST /v1/automations/{automationId}/run. Pass dry_run: true to preview the recipient count without sending, or scheduledAt to launch later, and follow the run through the audience-runs endpoints. Over MCP, the same action is the run_automation tool. See the API Reference for the contract.