Flow Steps

What a step does

Steps are the actions, waits, and decisions inside a flow. You can combine them to build a sequence that reacts to what a contact does. If you are still picking a starting event, see Flow Triggers.

Flow steps overview (visual grouping)

Use this mental model when building a flow:

• Timing: Delay, Wait Until
• Communication: Email, SMS
• Logic: Conditions, Quiz Result Router, A/B Testing
• Data + Integrations: Actions, Webhook

Step types (quick guide)

Edit steps from connected tools

Connected assistants and API-key workflows can help make reviewed changes to flow steps without rebuilding the whole flow.

• Read the flow first so the current trigger, step order, emails, waits, and delays are visible before changes are made.
• Add a new step after an existing step or at a specific position.
• Update an email step, delay duration, wait condition, or other saved step settings.
• Reorder linear step sequences while active contacts stay attached to their current step.
• Delete a step after review. If contacts are currently on that step, Hiveality moves them to a valid nearby step when possible and reports how many were affected.

For complex branching changes, use the flow editor to review the path visually before publishing.

Continue after branches

Conditions, Quiz Result Routers, and A/B tests show separate plus buttons inside each branch and a centered Add step after all branches button. Use the centered button for a common sequence that should run after every path. This also keeps nested branches readable because their shared continuation stays inside the containing path.

Need help verifying? Use Flow Testing once your steps are in place.