Flows (Automation)
Automate follow-ups, reminders, and internal tasks with flows.
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.
Describe the flow
Explain the audience, goal, offer, timing, and any pages, funnels, or products the emails should reference. Use Add reference or type @ to mention saved resources from this site.
Choose the flow style
Pick a flow type, style preset, header/footer preference, and image quality.
Review the plan
Edit the flow name, URL slug, trigger summary, email subjects, preview text, calls to action, and delays before generating.
Generate and refine
Hiveality creates the flow, email steps, and editable email drafts. Open the flow to test triggers, timing, and messages before publishing.
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.
Builder updates (May 2026)
- 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.
For setup details, see Flow Triggers and Wait Until.
Build a simple first flow (recommended)
Pick a trigger
Choose something you can test quickly (like a form submission).
Add one wait and one message
A common pattern is: - Wait 5 minutes - Send a welcome email
Test it with a single contact
Trigger the flow once (submit the form yourself) and confirm the contact moves through the steps.
Start small. A flow that works reliably for one test contact is easier to expand than a big flow that’s hard to debug.
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
Related Help Docs
Was this helpful?