SabFlow gives your team a visual canvas where triggers, conditions, AI calls and channel actions snap together like Lego. Build a 12-step abandoned-cart recovery, a tax-season nudge, or a multilingual onboarding tree in an afternoon — and watch it run in production with live execution logs.
Most operators describe their automation stack the same way: a tab in Notion, a folder of Zaps no one owns, two HubSpot workflows that occasionally fire twice, and a WhatsApp bot the agency built last year. When the marketing manager wants to add a single branch — say, send a Hindi template to Tier-2 customers — they file a ticket and wait three weeks.
Meanwhile, the actual logic of the business lives in heads, not systems. New hires re-discover that orders above ₹5,000 should skip the COD reminder. Refunds get a different SLA than complaints, but only the senior agent knows that. Every change risks breaking something silently, because nothing is observable end-to-end.
Flow Builder collapses this. One canvas, one source of truth, one place where a non-developer can read a customer journey from trigger to outcome and confidently change a step without paging engineering.
SabFlow is a graph-based execution engine wrapped in a designer that feels closer to Figma than to Zapier. You start with a trigger — a WhatsApp message, a Shopify webhook, a CRM stage change, a cron — and drag nodes onto the canvas. Send Template, Wait, Branch, HTTP Request, AI Generate, Assign Agent, Update Field, Add Tag, Goto: each node has typed inputs, retry policy and timeout. The runtime serialises every execution to durable storage so a flow that started yesterday can resume after a deploy, a crash, or a 24-hour wait window.
Branching is first-class. A Branch node evaluates JSONPath expressions against the flow context — `{{contact.tags}}`, `{{order.total}}`, `{{lastMessage.intent}}` — and routes execution down the matching path. You can split on geography, plan tier, language preference, last-seen timestamp, or any custom field. Branches nest, loops are explicit (with bounded iteration), and dead-letter paths catch anything unhandled.
Because SabFlow runs inside SabNode, every node has zero-config access to the rest of the platform: send a WhatsApp template using your verified BSP, trigger an email through the same audience filter you built for broadcasts, drop a contact into a Kanban stage, or hand the conversation to a live agent with full context. There is no glue code, no auth juggling, no rate-limit accounting — it is one system speaking to itself.
For technical teams there is an escape hatch on every node. HTTP Request talks to any REST endpoint with retries and exponential backoff. AI Generate calls your tenant-scoped model from AI Studio with tool-calling enabled. Script (sandboxed JavaScript) lets you transform payloads in-place. And the whole graph is exportable as JSON, version-controlled and diffable in pull requests if you want a GitOps workflow.
Send Template, Send Free-form, Wait (relative or absolute), Branch, Switch, Loop, HTTP Request, AI Generate, Assign Agent, Update Contact, Add/Remove Tag, Move Stage, Webhook Out, Script, Subflow. Each has typed inputs, JSON schema validation and inline docs.
Replay any historical run step by step. See the exact context object at every node, every API response, every retry attempt and the final outcome. Filter executions by contact, trigger, status or duration to find the one customer who fell through.
Every save creates a numbered version. Diff two versions side-by-side, promote a draft to live with one click, and roll back to any prior version if a deploy goes sideways. In-flight executions continue on the version they started on.
Extract any cluster of nodes into a Subflow with named inputs and outputs. Use the same KYC verification or refund-eligibility block across ten parent flows. Update the subflow once and every parent picks up the change instantly.
Drop an AI step anywhere on the canvas. It calls your tenant-scoped LLM in AI Studio with retrieval, tools and guardrails configured per node. Use it to classify intent, summarise a thread, draft a reply or pick the next-best-action.
Every external call (HTTP, BSP send, AI) has configurable retry windows with exponential backoff and a dead-letter queue. Failed runs surface in an alerts panel with the full stack so ops can replay after the upstream is healthy.
Reference any variable in the flow context using `{{path.to.value}}` syntax. Pipe transforms (upper, lower, date:dd-MM-yyyy, currency:INR) format on the fly. No template engine to learn — it is the same syntax across nodes.
Trigger on Shopify checkout.abandoned. Wait 30 minutes, send a WhatsApp template with the cart summary, then a Branch on reply. If the customer asks about size, route to AI Generate with the catalog as context. If silence at hour 4, send a 5% off coupon. Recover 18-22% of carts with three nodes and no agent time.
New KYC submitted → Branch on contact.language. Hindi, Tamil, Telugu and English paths each send the verification template in the right script. Subflow handles document upload via interactive list message. Hand off to an agent only if the AI classifier flags risk. Cuts agent load by 60% in the first month.
Trigger on user.enrolled. Send module-1 link, wait 48 hours, HTTP Request to your LMS to check completion. If incomplete, send a nudge template; if complete, advance to module-2. Loops until course done or 30-day timeout. Replaces a manual cohort manager.
Cron trigger 24 hours before appointment pulls today's slots from Google Calendar. Sends a confirmation template with reply buttons (Confirm / Reschedule / Cancel). Reschedule branch calls AI Generate to suggest the next three open slots, books on confirmation. Cuts no-shows by a third.
Form submission → enrich via Clearbit HTTP node → Branch on company size and region. Enterprise leads get assigned to AE Slack channel with full payload; SMB leads enter a self-serve nurture flow with three templates over seven days. Marketing edits the branch thresholds without filing engineering tickets.
Flow Builder is included on every SabNode workspace. No separate billing, no extra setup — flip it on from your workspace settings.
Choose from WhatsApp message, webhook, schedule, CRM event, form submit or manual fire. Each trigger exposes its own payload schema you can reference downstream.
Connect nodes with arrows. Configure each one with typed inputs. The validator catches missing fields, circular paths and unreachable nodes before you save.
Hit Test, pick yourself or a sandbox contact, and step through the flow. The debugger shows every variable at every node and lets you skip waits in test mode.
Promote the draft to live. New trigger fires use the latest version; in-flight runs finish on the version they started on. Roll back from history if anything goes wrong.
Watch the execution list, drop into any run that errored, fix the node, redeploy. Flow Analytics shows funnel drop-off so you know where to optimise next.
No credit card. No sales call required. Spin up a workspace, plug in a number, and your team is live in under an hour.