Flows (Automation)

What flows do

A flow is an automation that runs steps for you.

Think: when something happens → do these steps.

Flows are used for:

• Follow-ups and nurture sequences
• Appointment reminders
• Internal task handoffs
• Automated emails and notifications

Key parts of a flow

• Trigger: what starts the flow (example: form submitted, tag added)
• Conditions: rules that decide which path to follow (example: “has tag VIP”)
• Actions: what the flow does (send an email, wait, update a record, etc.)
• Targeting filters: optional list/tag include/exclude rules for tighter audience control

If you are brand new, start with Flow Triggers and then review Flow Steps. For milestones and go-live changes, see Flow Goals and Flow Drafts and Publishing.

Generate a flow with AI

Use AI Flow Builder when you want Hiveality to draft a complete email flow from a prompt.

If your prompt includes pasted source copy, choose whether Hiveality should preserve it closely, lightly edit it, or freely rewrite it for the flow.

For references that support layout matching, click the reference chip to choose Content, Layout, or Both before generating.

Recent builder and automation updates

• Quiz automations can start from guided result, score, and answer filters. A quiz result router starter creates one named branch per result plus a fallback path, and the trigger preview can test saved answers without enrolling a contact or sending a message.
• Flow lists now load names, trigger summaries, step totals, and contact counts in fewer passes, so larger automation lists are quicker to scan.
• Flow grid and list views have clearer card actions and faster delete feedback. If a flow delete fails, the list restores the flow instead of leaving the screen out of sync.
• Step badges now summarize waiting, completed, error, opted-out, sent, delivered, opened, and clicked activity with fewer refresh delays in larger flows.
• The flow sidebar and top controls were refined for faster editing in larger flows.
• Trigger and wait configuration now supports searchable list/tag selectors with inline create/manage actions.
• Date-based trigger/wait setup now includes explicit trigger time controls to reduce timing ambiguity.
• Connected assistants and API-key workflows can review the ordered step graph for a flow, then add, update, delete, or reorder steps after approval.
• Deleting a step from a flow is designed to keep active contacts on a valid next step when possible and preserve past step history for reporting.
• Moving or pasting a step keeps its nested condition branches or A/B variants together, and Hiveality blocks moves that would place a step inside one of its own branches.

For setup details, see Flow Triggers and Wait Until.

Build a simple first flow (recommended)

Common flow patterns (copy the idea, customize the content)

• Welcome flow: form submission → wait → send email → tag contact
• Reminder flow: booking created → wait until date/time → send reminder
• Re‑engagement: last activity > X days → send email → if opened/clicked, branch

Troubleshooting (quick checks)

• If contacts don’t enter: confirm the trigger event actually happened (and matches the flow trigger)
• If contacts look “stuck”: check for a Wait step that is waiting on a condition/time that never becomes true
• If emails aren’t sending: confirm email settings and that the contact is eligible to receive messages