Automate the work between your tools.
Approvals, handoffs, and reports that run on their own and wait for the right person. Built with AI, backed by Python you own.
Examples
Approvals, retries, and schedules. Built in.
An invoice that waits for sign-off, a support request that routes itself, a post that retries only the channel that failed, and a maintenance sweep that runs every five minutes. Switch to Code for the Python behind each; all four are open source.
Example run: an invoice is received, checked by the agent, approved in Slack, and logged in Notion.
Waits for a person, and escalates if nobody answers in a week.
From [email protected]
Invoice agentExtracts, checks, and routes
Extracted
- Vendor
- Northstar Studio
- Amount
- $2,400
- Due
- Oct 15
Checks
- Extract invoice details
- Check for duplicates
- Find the right approver
Finance approval#finance
Invoice agent · to Morgan
Approve $2,400 to Northstar Studio? No duplicate found.
Escalates to the finance director after a week
Decision logRecords the decision next
Step 1 of 3Swipe to follow the workflow
ex06_invoices.pyView full sourcefrom reflex_workflow import Workflow, step, wait_for class Invoice(Base, Workflow): # Setup and database fields omitted. See full source. @step(retries=RETRIES, backoff=BACKOFF) async def extract(self): fields = await world.call( "ocr.extract", key=self.upload_id, upload=self.upload_id ) # A field the reader could not make out comes back as null, not absent. self.supplier = fields.get("supplier") or "unknown" self.number = fields.get("number") or self.upload_id self.amount_cents = int(fields.get("amount_cents") or 0) self.status = "extracted" return Invoice.check_duplicate @step(retries=RETRIES, backoff=BACKOFF) async def check_duplicate(self): already = await Invoice.by( Invoice.supplier == self.supplier, Invoice.number == self.number, Invoice.id != self.id, Invoice.bill_id.is_not(None), ).get() if already is not None: self.status = f"duplicate-of:{already.upload_id}" return None return Invoice.request_approval @step(retries=RETRIES, backoff=BACKOFF) async def request_approval(self): self.approver = ( "finance-director" if (self.amount_cents or 0) >= SECOND_SIGNATURE_CENTS else "team-lead" ) await world.call( "chat.post", key=f"approve-{self.upload_id}", to=self.approver, text=f"{self.supplier} {self.number}: {(self.amount_cents or 0) / 100:.2f}", ) self.status = "awaiting-approval" return wait_for( Invoice.decide, timeout=APPROVAL_DEADLINE, on_timeout=Invoice.escalate ) @step(retries=RETRIES, backoff=BACKOFF) async def decide(self, verdict: str, *, by: str): self.decided_by = by if verdict != "approve": self.status = "rejected" return None return Invoice.record_bill @step(retries=RETRIES, backoff=BACKOFF) async def record_bill(self): bill = await world.call( "ledger.record", key=self.reference, supplier=self.supplier, number=self.number, amount_cents=self.amount_cents, ) self.bill_id = bill["id"] self.status = "recorded" @step(retries=RETRIES, backoff=BACKOFF) async def escalate(self): await world.call( "chat.post", key=f"overdue-{self.upload_id}", to="finance-director", text=f"Invoice {self.number} from {self.supplier} has waited a week", ) self.status = "overdue"Build your way
The ease of AI. The power of Python.
Start in Reflex AI Builder or work with your own coding agent. Either way, you get readable Python you can inspect and extend.
Describe the work. Shape the workflow.
Start in Reflex AI Builder. Explain the outcome, connect your tools, and refine the steps in conversation.
When a client signs, draft a kickoff brief from their contract. Get our project lead’s approval before sending the welcome email.
Added an AI draft, a human checkpoint, and a welcome email—all backed by Python.
@step()
async def request_review(self):
await services.request_review(self.brief)
return wait_for(Onboarding.approve_brief)
@step()
async def approve_brief(self, approved: bool):
if approved:
return Onboarding.send_welcome
return None
- Human approvalsWaits for people
- Automatic retriesFailed steps only
- Every run tracedEach step visible
Connected from the start
Designed for the tools you already use.
Workflows will use the AI Builder integration catalog: your CRM, documents, email, payments, AI models, and databases. Python packages and APIs cover the rest.
Connect your CRM, prepare a document with AI, request approval, and send the result.
Explore AI Builder integrationsExtend with your own APIs and Python packages.
- HubSpotCustomer data
- NotionKnowledge
- ResendEmail delivery
- OpenAIAI steps
- StripePayments & billing
- DatabasesYour business data
Reliability
Every step of your workflow, visible.
Every step is recorded as it runs. See what finished, what is waiting on a person, and what is being retried, with the code behind each step.
Keep people in the loop.
Pause for approval and continue with the decision.
Retry without starting over.
Keep completed work and retry the step that needs attention.
Know what happened.
Inspect the code and timing of each step.
A few things to know.
When can I try Reflex Workflows?
Join the waitlist and we’ll email you when early access is available.
Do I need to write Python?
You’ll be able to start with a prompt in AI Builder or work with your own coding agent. The workflow is backed by Python, so you can inspect or extend it whenever you want.
What does Reflex Workflows bring together?
AI that drafts a workflow from your description, Python your team can read and edit, execution that saves progress, waits for people, and retries failed steps, and the AI Builder integrations, which Workflows will use.
Where do workflows run?
In your Reflex app. A workflow is Python in the app’s code, built in AI Builder or with your own agent. Its progress is stored in the app’s Postgres database and the app’s own processes run the steps, so there’s no separate service to operate, and workflows run wherever the app is deployed.
What makes a workflow durable?
Progress is saved as each step finishes. After a restart or a failed call, the workflow resumes from saved progress instead of starting over. A step that was interrupted can run again, so steps that change other systems are written to be safe to repeat.
Which integrations will Workflows use?
Workflows will use the AI Builder integration catalog, with Python and APIs available for custom connections. We’ll share availability details when early access opens.
Does every step need AI?
No. Use rules for predictable decisions and AI for tasks such as reading documents, classifying requests, or drafting replies. Human review belongs wherever your process needs it.
What should I automate first?
Start with a recurring process that has a clear trigger and outcome: routing a lead, preparing a weekly report, or approving an invoice. Add more steps as you learn what your team needs.