Why use Flowker?
Financial operations involve multiple steps, approvals, and external checks. Managing these manually leads to errors, delays, and compliance gaps. Flowker centralizes this orchestration so every step stays tracked, traceable, and repeatable. For the full business case, see Why Flowker?.
Core concepts
At its core, Flowker works with workflows and nodes:
- Workflows: The overall process — a graph of nodes and edges that defines what happens for a given operation (for example, “process a Pix payment” or “onboard a new customer”). Workflows can branch, and retry policy can retry eligible executor-call failures.
- Nodes: The individual elements in a workflow — such as a trigger, an external-service call, a condition, or an action.
What makes Flowker different?
Purpose-built for the financial domain
Unlike generic workflow tools, Flowker is modeled specifically for the transactional ecosystem. Its architecture reflects the operational and regulatory realities of banking, payments, Pix, and financial orchestration.Pre-ledger validation
Use Flowker to orchestrate validation calls before a ledger-posting step. Your ledger integration must enforce that no other path can post without the required checks.Integrations with APIs and webhooks
Flowker receives webhooks and calls external services through provider configurations. You define input and output expectations, then configure the provider connection and the nodes that call it.Step-level execution records
Each executed executor, conditional, or action node records its status, duration, output, and error message. Trigger nodes start graph traversal and do not create execution-step records. This gives you a step-by-step view of what each execution did through the API.End-to-end observability
When you enable telemetry, Flowker emits OpenTelemetry data for its HTTP and service operations. It also records structured logs.Enterprise-grade security
Token-based authentication through Access Manager, with per-resource, per-action authorization. Configure TLS termination and encrypted links in your deployment.Developer-first experience
Flowker includes OpenAPI definitions and a local development environment with Docker — enabling teams to build, test, and deploy flows with confidence and speed.Key features
Workflow orchestration
- Run nodes according to the workflow graph and selected conditional branches.
- Apply conditional logic based on HTTP status codes and response fields.
- Persist workflow execution state for review.
- Manage versions with full lifecycle control, including draft, activation, deactivation, and clone-based iteration.
Integration and connectivity
- Send HTTP requests (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS).
- Receive and process webhooks from external systems.
- Connect to multiple financial service providers.
Workflow configuration
- Define workflows as graphs of nodes and edges.
- Validate workflow definitions before activation.
- Map and transform data between executor calls.
Authentication and security
- Token-based authentication through Access Manager, with per-resource, per-action authorization.
- Structured logs. Configure encryption at rest in the deployment services that store data and secrets.
Observability
When telemetry is enabled, Flowker emits data through OpenTelemetry/OTLP and records structured logs. Connect your deployment’s telemetry backend to monitor API and service operations. Use execution records together with your deployment’s telemetry and logs to investigate workflow behavior.Common use cases
Anti-fraud operations
- Send transaction and account data to external fraud prevention services.
- Collect and process responses from multiple providers, and apply configurable rules to decide whether to proceed.
- Every step is recorded with its status and result.
Manual approvals
- Submit a request to, or query, an external approval system with executor nodes.
- Route on the decision that the external system returns.
- Flowker does not have a built-in pause; model asynchronous human review with an external system and a later workflow trigger or execution.
Payment orchestration
- Coordinate multi-step payment flows that span multiple providers or rails.
- Flowker can retry eligible executor-call failures. Reconciliation and posting controls belong to the systems you integrate.
Customer onboarding
- Automate KYC and AML processes, integrate with credit bureaus and validation services, and set up conditional onboarding rules based on risk profiles.
API architecture
Flowker’s API is divided into three main categories: Authoring, Runtime, and Administrative. Each category has a clear purpose to help developers build, execute, and manage workflows.
- Authoring routes: create, update, and manage workflow definitions and versions.
- Runtime routes: start, monitor, and control workflow executions in real time.
- Administrative routes: manage tenants, providers, and system health.
Current status
For additional information about specific integrations or implementation details, contact us.