Skip to main content
Financial operations involve multiple steps, approvals, and external checks. Managing these manually leads to errors, delays, and compliance gaps. Flowker lets you define these processes once as workflows and execute them consistently — with full audit trails and real-time visibility. This page walks you through what Flowker can do for your business. For technical setup instructions, see the Technical quickstart.

​
How Flowker works

You start by exploring what integrations are available, connect them to your environment, define a workflow that models your business process, and then execute it. Each execution is tracked, auditable, and recoverable. Here’s the high-level flow:
1

Explore the catalog

Browse built-in providers, executors, and triggers to see what integrations are available out of the box.
2

Configure your executors

Connect Flowker to the external services your workflows need — fraud engines, payment processors, KYC providers, notification services — by creating executor configurations with credentials and endpoints.
3

Define your workflows

Model your business process as a workflow: define the steps (nodes), the order they run (edges), and the conditions that control branching.
4

Execute and monitor

Trigger workflows via API or webhook. Monitor each execution in real time and retrieve results when complete.

​
What you can automate

Flowker is designed for multi-step financial processes that require reliability, traceability, and integration with external services. Here are common scenarios.

​
Payment orchestration

The challenge: A payment involves multiple steps — validation, routing to the right provider, confirmation, and notification. When handled manually or through scattered integrations, failures go unnoticed and reconciliation becomes painful. How Flowker solves it: Define a workflow that coordinates the entire payment lifecycle:
  1. Trigger — A new payment request arrives via API or webhook.
  2. Validate — Check that the payment data is complete and the account has sufficient balance.
  3. Route — Select the appropriate payment provider based on amount, currency, or rail (Pix, TED, SWIFT).
  4. Confirm — Call the provider and wait for confirmation.
  5. Notify — Send a confirmation event to the customer and update the ledger.
If any step fails, the workflow handles retries automatically. Every step is logged for reconciliation and audit.

​
Anti-fraud validation

The challenge: Fraud checks must happen before a transaction is processed — but they involve external services, scoring logic, and different thresholds depending on the transaction type. Hard-coding this logic creates maintenance nightmares. How Flowker solves it: Define a pre-transaction workflow that runs fraud checks before anything reaches the ledger:
  1. Trigger — A new transaction is submitted.
  2. Enrich — Collect customer history, device data, and geolocation from internal systems.
  3. Score — Call one or more fraud detection providers and collect risk scores.
  4. Decide — Apply rules: if the score is above the threshold, block. If borderline, flag for review. If clear, approve.
  5. Act — Proceed with the transaction or notify the compliance team.
All decisions are traceable. You can adjust thresholds and add new providers without changing the core logic.

​
Customer onboarding

The challenge: Onboarding a new customer requires identity verification, document validation, AML/KYC checks, and account creation. These steps involve multiple external providers and regulatory requirements that vary by jurisdiction. How Flowker solves it: Define an onboarding workflow that automates the entire process:
  1. Trigger — A new customer registration arrives.
  2. Verify identity — Call a KYC provider to validate the customer’s documents and identity.
  3. Check compliance — Run AML screening against sanctions lists and PEP databases.
  4. Evaluate risk — Apply internal risk rules based on the customer profile, jurisdiction, and transaction history.
  5. Create account — If all checks pass, create the customer’s account in the system.
  6. Notify — Send a welcome email or notify the relationship manager if manual review is needed.
Each step’s result determines the next action. If a check fails, the workflow stops and creates an audit record explaining why.

​
Manual approval workflows

The challenge: Some operations — high-value transfers, credit limit changes, account closures — require human approval. But building approval flows with email notifications, timeouts, and escalation paths is complex and error-prone. How Flowker solves it: Define a workflow that calls an external approval service via an executor:
  1. Trigger — A high-value transfer request is submitted.
  2. Evaluate — Check the amount, customer risk profile, and internal policies.
  3. Request approval — Call an external approval service (manager, compliance officer) through an executor node.
  4. Decide — A conditional node evaluates the approval response.
  5. Act — If approved, proceed with the transfer. If rejected, cancel and notify the requester.
You can define multi-level approvals by chaining executor nodes that call your approval service at each level.

​
Key capabilities

  • Pre-ledger validation — All checks run before any posting reaches the ledger, preventing inconsistent states.
  • Full audit trails — Every step generates detailed logs that can be queried, reviewed, and exported.
  • Provider integrations — Connect to fraud engines, KYC providers, payment processors, and any HTTP-based service.
  • Conditional branching — Route execution based on step results, amounts, risk scores, or any data field.
  • Idempotent execution — Built-in idempotency ensures safe retries without duplicate processing.
  • Real-time monitoring — Track execution status and step results as workflows run.
All Flowker API requests require authentication via the X-API-Key: <your-api-key> header. The API key is provisioned via the API_KEY environment variable during deployment. Provider-specific credentials (for external services) are managed through provider configurations. See the Technical quickstart for the full bootstrapping flow.

​
What’s next

Core concepts

Understand workflows, nodes, edges, and the execution model in detail.

Technical quickstart

Set up Flowker locally and run your first workflow through the API.

What is Flowker?

Deep dive into Flowker’s architecture, features, and design philosophy.

API reference

Explore the full API for workflows, executions, and configurations.