Flows

Beta

Flows are visual workflows that define how payments and events are processed in Orvion. They enable automation, conditional logic, and integration with external systems.

What are Flows?

Flows provide:

Visual workflow builder: Drag-and-drop interface for building workflows
Payment routing: Route payments to different connectors based on conditions
Automation: Trigger actions when events occur
Conditional logic: Handle different scenarios (success, failure, retry)

Flow Types

Payment Routing

Route payments to different connectors based on:

Amount thresholds: Route large payments differently
Currency: Route by currency type
Customer: Route based on customer attributes
Time-based: Route differently at different times

Invoice Automation

Automate invoice-related actions:

Payment reminders: Send reminders before due dates
Overdue handling: Mark invoices as overdue automatically
Agent triggers: Trigger agent actions when invoices are paid

See Invoice Automation Flows for details.

Custom Flows

Build your own workflows for:

Custom business logic: Implement your own payment rules
External integrations: Call external APIs and services
Complex scenarios: Handle multi-step processes

Flow Components

Start Nodes

Trigger when events occur:

Payment created: When a payment is initiated
Invoice created: When an invoice is created
Invoice overdue: When an invoice becomes overdue
Custom events: Your own custom events

Route Nodes

Route to different connectors:

Lightning Network: Route to Lightning connector
Multiple connectors: Try multiple connectors in sequence

Condition Nodes

Add conditional logic:

Amount checks: Route based on payment amount
Currency checks: Route based on currency
Status checks: Route based on payment status

Webhook Nodes

Call external APIs:

HTTP requests: Make GET, POST, PUT, DELETE requests
Custom headers: Add authentication and custom headers
Response handling: Process API responses

End Nodes

Complete the flow:

Success: Payment completed successfully
Failure: Payment failed
Canceled: Payment was canceled

Flow Configuration

Flows are configured:

Via Dashboard: Visual flow builder
Via API: (Coming soon)

Flow Execution

When a flow is triggered:

Event occurs: Payment created, invoice overdue, etc.
Flow starts: Start node is activated
Nodes execute: Each node processes in sequence
Flow completes: End node is reached

Flow Limits

One invoice automation flow per organization: Only one active invoice automation flow
Multiple payment routing flows: Can have multiple payment routing flows
Flow versioning: Flows can be versioned and tested before going live