Symbiosis Flow turns a written process into a running workflow, then lets you edit it in a production-honest studio. It executes across humans, governed Agent Cloud agents, RPA bridges, and system connectors, with SLAs, escalations, and self-heal when steps break. Approvals and exceptions are first-class. Every run is versioned and audited, and automated steps inherit Agent Cloud policy.
Most company processes still live in email threads, chat side-channels, and one person's memory. That is operational debt. Flow makes processes explicit: triggers, steps, roles, SLAs, exceptions, and integrations you can version, simulate, and prove.
iPaaS moves data between apps. BPM suites often drown you in notation. Chatbots answer. Flow runs the work: humans as steps, agents as governed workers, systems as connectors, on one runtime with one audit trail. The studio is for designers, the work inbox for operators, Process Intelligence for leaders who need cycle time.
Describe-to-build gets you a draft in minutes. The editor handles parallel paths, compensations, segregation of duties, business calendars, and canary deploys of a new process version. When a connector drifts or a system fails, self-healing proposes a repair that a human approves and the audit log records, instead of a silent 3am pile-up.
Describe-to-build
Natural-language process description → draft workflow with steps, roles, SLAs, escalations, and suggested integrations. Iterate in chat or refine in the studio.
Visual process studio
Drag-and-drop and structured editor for triggers, conditions, parallels, loops, subflows, timers, and compensations - with diffable version history.
Unified runtime
One engine for human tasks, Agent Cloud agent steps, system connectors, RPA bridge steps, webhooks, and schedules - replay-safe and idempotent where money or writes are involved.
Human Work OS
Unified inbox (web + mobile + Slack/Teams): approvals, forms, document review, delegation, out-of-office, skills-based routing, and SLA clocks with business calendars.
Agent steps on Agent Cloud
Automation steps run as governed agents - policy-checked, credential-brokered, spend-aware, killable - with structured explainability when blocked.
Self-healing flows
When a step's target changes or fails, Flow proposes a repair (remap field, retry policy, alternate connector) - human-approved, version-bumped, audit-logged.
Integration fabric
Connectors to ERP, CRM, HRIS, email, storage, tickets, payments, and custom APIs/MCP - plus an RPA bridge for UI-only systems with a path to real APIs.
Forms, documents & e-sign
Dynamic forms, generated documents, attachment evidence, and e-sign steps wired into the same run trail.
Case & exception management
Long-running cases (claims, incidents, vendor onboarding) with war-room views, notes, evidence, and exception queues that don't die in email.
SLA, escalation & calendars
Per-step and end-to-end SLAs, multi-level escalation trees, business-hours calendars, and holiday sets per region/entity.
Process mining & discovery
Discover real paths from event logs, email/ticket patterns, and system trails - then promote discovered variants into governed Flow versions.
Process Intelligence
Cycle times, bottlenecks, rework rates, exception heatmaps, cost-per-run, and agent vs human effort - by workflow version and cost center.
Simulation & canary release
Replay historical runs against a candidate version; canary a % of traffic; auto-rollback on SLA or error regressions.
Template & blueprint gallery
Procure-to-pay, hire-to-retire onboarding, invoice AP, incident, change, access JML, CapEx, vendor onboarding, claims - scopes and SLAs included.
Subflows & process library
Reusable subprocesses (approval matrix, dual-control pay, notify stakeholder) composed into larger flows with ownership boundaries.
SoD & compliance controls
Segregation of duties, dual-control steps, immutable run history, retention policies, and evidence packs for auditors.
Notifications & channels
Email, Slack, Teams, SMS, push - with digests, reminders, and quiet hours that respect SLA urgency.
Workload & skills routing
Route human work by role, skill, language, region, workload, and VIP priority - with fairness and overflow pools.
Knowledge-grounded decisions
Optional Symbiosis Knowledge steps: cite policy docs before a human or agent decides, so runs don't invent procedure.
Multi-entity & tenancy
Org/entity isolation, shared templates with local overrides, and cross-entity escalation where shared services run the middle office.
DESCRIBE STUDIO
Natural-language describe-to-build, chat iteration, and promotion of drafts into versioned workflows.
PROCESS STUDIO
Visual/structured editor: triggers, branching, parallels, subflows, timers, compensations, SoD.
RUNTIME ENGINE
Durable execution across humans, agents, connectors, RPA, webhooks, and schedules - with idempotency and replay.
HUMAN WORK OS
Unified work inbox, forms, delegation, skills routing, SLAs, escalations, multi-channel notify.
AGENT FABRIC
Agent Cloud-backed automation steps with policy, credentials, spend, and kill-switch inheritance.
INTEGRATION FABRIC
System connectors, events, RPA bridge, and self-healing remap proposals.
CASE & EXCEPTIONS
Long-running case management, exception war rooms, evidence, and customer/vendor portals.
PROCESS INTELLIGENCE
Mining, analytics, simulation, canary releases, and cost-per-run attribution.
Investment is bespoke to estate size, compliance needs, and deployment shape - book a demo and we'll map the right fit.
STARTER
- → Describe-to-build
- → Process studio (core)
- → Human tasks + SLAs
- → Basic connectors
- → Run audit trail
- → Template starter pack
BUSINESS
- → Everything in Starter
- → Agent Fabric (Agent Cloud steps)
- → Self-healing proposals
- → Forms, documents, e-sign
- → Process Intelligence dashboards
- → Multi-channel inbox (Slack/Teams)
- → Subflows & library
ENTERPRISE
- → Everything in Business
- → Process mining & discovery
- → Simulation & canary releases
- → Case & exception war rooms
- → SoD / dual-control packs
- → RPA bridge + residency controls
- → Private deployment options
Flow, answered
How is Flow different from an iPaaS?
iPaaS moves data between apps. Flow runs processes involving people - approvals, exceptions, SLAs, accountability - with integration as a means, not the product. Agent steps are governed workers, not fire-and-forget scripts.
How is Flow different from a classic BPM suite?
BPM often optimizes for notation and committee modeling. Flow optimizes for time-to-running-process: describe-to-build, production-honest editing, human work inbox, Agent Cloud automation, self-healing, and process intelligence - without requiring a six-month modeling program before the first run.
Do automation steps bypass security?
No. Automated steps run as Agent Cloud principals: RBAC/ABAC, policy checks, credential brokering, audit, and kill-switch. Automating a step never widens privilege by accident.
Can we keep humans in the loop?
Humans are first-class steps, not exceptions. Approvals, reviews, and exception handling sit in the Human Work OS with SLAs, escalation, and multi-channel notify - and disagreement logs feed process improvement.
What happens when a connector or system breaks?
Self-healing proposes a repair (retry, remap, alternate path). Humans approve the change; the workflow version bumps; the audit trail records what changed and why. Silent failure is the failure mode we design against.
Can Flow discover processes we don't have documented?
Yes - Process mining and discovery infer real paths from system events and work patterns, then let you promote a discovered variant into a governed, versioned Flow - with owners and SLAs attached.
See it against your reality.
A 30-minute walkthrough with an engineer who builds it - your use case, not a script.