> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Flowker documentation

> Comprehensive documentation for Flowker, the workflow orchestration engine, including guides, API reference, and OpenAPI specification.

<Badge stroke icon="calendar-days" iconType="regular">April 22, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation update</Badge> <Badge color="purple" size="lg" stroke icon="eye" iconType="regular">Review recommended</Badge>

## Affects

***

Teams using Flowker guides or API reference.

This update applies to the public documentation portal. It does not change the runtime API behavior unless the linked product documentation says otherwise.

## What changed

***

# Flowker documentation

Flowker now has full documentation coverage across guides, API reference, and OpenAPI specification. This release includes 11 guide pages, the API reference, and an OpenAPI 3.1 spec — all verified against the Flowker source code and available in English, Portuguese, and Spanish.

### New pages

***

### Overview

* [**What is Flowker**](/en/flowker/what-is-flowker) — Product overview, architecture, and where Flowker fits in the Lerian platform
* [**Why Flowker**](/en/flowker/why-flowker) — Key differentiators, design principles, and the problems Flowker solves
* [**Flowker concepts**](/en/flowker/flowker-concepts) — Core concepts: workflows, nodes, edges, executor configurations, provider configurations, catalog, and executions

### Guides

* [**Getting started**](/en/flowker/flowker-getting-started) — End-to-end walkthrough: explore the catalog, connect your providers, define workflows, and execute
* [**Integration guide**](/en/flowker/integration-guide) — Deep dive into provider configuration, authentication types, field mapping, webhook triggers, circuit breaker, and retry behavior
* [**Workflow design guide**](/en/flowker/workflow-design-guide) — Workflow lifecycle, node types, edge conditions, design patterns (sequential, conditional, parallel fan-out), and technical limits
* [**Working with request and response data**](/en/flowker/working-with-request-and-response-data) — Input/output mapping, inline transformations, Kazaam operations, and execution order
* [**Security**](/en/flowker/security) — Access Manager authentication, provider authentication, CORS policy, TLS, and data protection
* [**Compliance**](/en/flowker/compliance) — Validation before the ledger write, the step-level record of every execution, and regulatory context
* [**Observability guide**](/en/flowker/flowker-observability-guide) — OpenTelemetry traces, Prometheus metrics, health check endpoints, and Grafana dashboard setup
* [**Environment variables**](/en/flowker/flowker-environment-variables) — Complete reference for all server, database, authentication, and observability configuration options

### Use cases

* [**Use cases**](/en/flowker/use-cases) — Real-world scenarios: payment processing, fraud detection, KYC/AML, reconciliation, and notification orchestration

### API reference

* [**API quick start**](/en/reference/flowker/flowker-api-quick-start) — Getting started with the Flowker API
* [**Error list**](/en/reference/flowker/flowker-error-list) — Complete error code reference
* [**Implementing observability**](/en/reference/flowker/flowker-implementing-observability) — Observability setup guide for the API

Endpoint reference pages shipped in the same release. The **Flowker** section of the API Reference tab lists the endpoints Flowker publishes today.

### OpenAPI specification

* [**Flowker OpenAPI 3.1 spec**](/en/openapi/v3-current/flowker.yaml) — The specification that the API reference pages render from

## Impact

***

This is a documentation update. Existing integrations do not need a migration from this release note alone.

## What you need to do

***

<Steps>
  <Step>
    Review the Flowker documentation before building or updating workflow orchestration integrations.
  </Step>
</Steps>

### Deadline

None.

### Why

The documentation now covers Flowker guides, API reference, and product behavior more comprehensively.