Why use Flowker?
Flowker makes decisions based on the result of each step, using predefined rules to determine whether the workflow should move forward or stop. At its core, Flowker is based on two building blocks:- Workflows: Orchestrate task execution across the system, ensure resilience, and store execution states for auditing and recovery.
- Tasks: The actionable steps in each workflow, such as calling an API, triggering a plugin, or running a validation based on other task responses.
Solving orchestration challenges
Flowker tackles a real challenge in financial systems: managing flexible, multi-step authorization flows that reflect how each business operates. Whether you need to integrate with an anti-fraud service, wait for a manual approval, or coordinate calls to other Lerian product, Flowker ensures your transactions follow the right path, securely and reliably.Key capabilities
- Sequential workflows.
- HTTP request tasks (POST, GET, PUT).
- Conditional validations and branches based on HTTP status codes and response fields.
- Event generation to external queues during workflow execution.
Flowker usage examples
Flowker is ideal for use cases involving external checks before or during a transaction. It supports anti-fraud validations, manual approvals, and seamless integration with other Lerian plugins.- Anti-fraud: During a financial transaction, institutions often need to validate data to prevent fraud. This usually involves calling an external anti-fraud service with transaction and account details.
- Manual approvals: High-value or corporate transactions often require extra user, manager, or treasury team validation. Flowker lets you add steps waiting for an external “trigger” before completing or canceling a transaction.
Integrations with Lerian ecosystem
When using other Lerian product or plugins, Flowker acts as the orchestrator, coordinating the transaction flow and communicating with the right services at the right time.This product is still under development. For more information, contact us.