Flows
Flows on the Orvanta Hub are complete, multi-step automations — several scripts wired together with branches, loops, triggers, and approvals — that you fork in as a working starting point instead of building the orchestration from a blank canvas.
What’s on the Hub today
Section titled “What’s on the Hub today”Community flows lean toward two shapes:
- Trigger-shaped starters that pair a native trigger with a preprocessor, ready to adapt to your own payload — e.g. “Email trigger flow with preprocessor template”, “Kafka flow with preprocessor template”, “HTTP route flow with signature verification template”.
- End-to-end examples that show a realistic multi-step pattern — e.g. “List Slack channels and send a shared message to selected channels”, “Call an existing service in Python, normalise in TypeScript, and audit the result”, “Triage a record with an agent, then require a human to authorise the write”, “Review an exception queue on a schedule and only interrupt a human when it matters”.
That last pair is a useful pattern to recognise: several Hub flows pair an AI agent step with a human approval step, rather than letting the agent act unattended.
Using a flow from the Hub
Section titled “Using a flow from the Hub”Fork the flow into your workspace, then:
- Swap the trigger/resource for your own (a different mailbox, topic, or endpoint).
- Replace the domain-specific steps; keep the surrounding retry/branch/approval structure unless you have a reason to change it.
- Re-test before promoting it to a schedule or a live trigger.