Agentic flows β conditions and chained actions
Build multi-step automations that fire conditionally and trigger follow-up actions in sequence.
Updated 2 Mar 2026
What are Agentic Flows?
Agentic flows let you chain actions together and add conditional logic. For example:
- Only alert if the lead provided a phone number
- When lead is captured β send email (immediately), then post to Slack (after 5 minutes)
- Only run the HubSpot action if the lead's email contains
@enterprise.com
Flows are available on Business plans.
Conditions
Each action can have one or more conditions. The action only fires if all conditions pass (AND logic) or if at least one passes (OR logic).
Adding conditions
- Open an action (Dashboard β Actions β Edit)
- Scroll to Conditions
- Click Add condition
- Configure:
- Field β e.g.
lead.email,lead.phone,lead.name,lead.company - Operator β exists, not exists, contains, equals, starts with
- Value β the comparison string (not needed for exists / not exists)
- Field β e.g.
- Set Logic to AND (all must pass) or OR (at least one must pass)
- Save
Example conditions
| Goal | Field | Operator | Value |
|---|---|---|---|
| Only fire if email is provided | lead.email | exists | β |
| Skip anonymous leads | lead.name | exists | β |
| Only for business emails | lead.email | contains | @ |
| Enterprise leads only | lead.email | ends with | .com.au |
Flow chains
Flow chains let one action trigger another. After action A fires successfully, action B fires (optionally after a delay).
Creating a chain
Using the Supabase dashboard or API:
INSERT INTO flow_chains (tenant_id, trigger_action_id, follow_up_action_id, delay_minutes)
VALUES ('<your-tenant-id>', '<action-a-id>', '<action-b-id>', 5);
-- ^ after action A fires, trigger action B 5 minutes later
For immediate chaining, set delay_minutes = 0.
A UI for managing flow chains visually is coming soon. For now, use Supabase Studio or contact support.
Testing conditions locally
- Create an action with a condition (e.g. "only if lead.email exists")
- Open your chatbot Preview and submit a lead without an email β action should not fire
- Submit again with an email β action fires, check Logs to confirm
Use cases
- Lead scoring: only notify Slack for leads that include a phone number (higher intent)
- Follow-up sequence: send a welcome email immediately, then send a feature overview after 1 hour
- Escalation: for enterprise email domains, also create a HubSpot deal in addition to the contact
Was this helpful?
If you have questions or suggestions, email us at support@pivra.ai .