Zagru FlowIntegration and workflow automation
Draw it. It runs.
Triggers, databases, REST, SOAP, files and approvals on one canvas — running reliably and securely, in the cloud or on your own servers. No accepted event is ever silently lost.
Early access — we are onboarding a small number of design partners.
- chaos-test runs green, under 82 forced kills
- 1,000 / 1,000
- events lost
- 0
- p95 engine overhead, measured
- 3.8 ms
Illustrative interface
From trigger to e-invoice, on one canvas.
Every step writes to a durable journal, so any run can be resumed, replayed or explained.
Illustration: a Zagru Flow canvas. A daily trigger reads new orders from SQL Server, maps fields, then creates orders in Zagru One over REST and sends e-invoices over SOAP, and finally emails a summary.
What it does
Built for the integrations that keep a company running.
- 01
Database- and file-first
PostgreSQL, SQL Server, MySQL and Oracle; SOAP with WSDL and WS-Security; REST with OpenAPI import; FTP, FTPS and SFTP; e-mail; CSV, JSON, XML and Excel.
- 02
An honest delivery promise
Idempotency keys, saga compensation, re-run from the failed step and bulk replay — and an "outcome unknown" state that is never quietly counted as success.
- 03
Every run tells its story
A run is a readable timeline — "Inserted 1,240 rows into STOCK_IMPORT" — with re-run from this step, replay, cancel and resolve-unknown-outcome one click away.
- 04
Dev and Prod, done properly
Separate environments with promotion, versions for every flow, a sandboxed code step — and copying to Prod never copies a secret.
- 05
Flow Apps
Point Flow at an existing database and get lists, record pages and forms generated from its tables, without moving the data. Reads are automatic; writes always go through a flow, so the old system's rules still hold.
How it works
Trigger. Steps. Journal. Recover.
The only mandatory infrastructure is PostgreSQL — the journal is what makes every run durable.
Trigger
A schedule, a webhook, a database change, a file arriving, a queue message or a person pressing Run.
Steps
Database, REST, SOAP, files, transforms, branches, loops, approvals, sandboxed code and sub-flows.
Journal
Each step's input and outcome is written durably before the next begins — crash-safe and replayable.
Recover
Retries with idempotency, compensation when a later step fails, and a human decision when the outcome is unknown.
Report
Notifications, a searchable run explorer and a full audit trail of who changed what.
Illustrative interface
The story of a run.
Every run reads like a timeline. When an outcome is unknown, Flow says so — and a person decides.
In depth
The details integration teams check first.
Triggers and steps
- Schedule, webhook, database change, file arrival, queue message, manual
- Database query and bulk insert
- REST with OpenAPI import; SOAP with WSDL and WS-Security
- FTP, FTPS, SFTP; e-mail
- Transform, branch, loop, approval, sub-flow
- Sandboxed code step
Reliability
- Durable, crash-safe run journal
- Idempotency keys on side effects
- Saga compensation
- Outcome-unknown state, never auto-succeeded
- Re-run from a step; replay whole runs in bulk
Runs on
- SaaS or on your own servers
- Small installation: 2 vCPU / 4 GB RAM including PostgreSQL
- PostgreSQL is the only required infrastructure
- Turkish and English interface
On the roadmap
- Outbound-only Agent for systems behind the firewall
- Regression replay on real history
- Shadow mode
- Daily no-data-loss reconciliation
- Change impact analysis
- Automatic KVKK data map
- Every flow as an MCP tool; local LLM option
- Local connectors: Logo, Mikro, Netsis, Nebim, e-invoice integrators, marketplaces, carriers, Zagru One
Security and data
Security is in the core, not in a plug-in.
Integrations touch every system you own. Flow is built on that assumption.
Tenant isolation in the database
Row-level security keeps each tenant's flows, runs and data apart, enforced by PostgreSQL itself.
Envelope-encrypted secrets
Credentials live in a vault, are redacted from logs, and are never copied when a flow is promoted to Prod.
SSRF protection and egress policy
Outbound calls are checked against policy, so a flow cannot be turned against your internal network.
Parameterised SQL only
No string-built queries, anywhere — database steps bind parameters.
Hardened file handling
XML and zip processing is hardened against entity expansion and path traversal.
Roles, 2FA and quiet logs
Owner, Admin, Builder, Operator and Viewer roles; TOTP two-factor sign-in; a metadata-only logging mode for sensitive flows.
In the suite
Sold on its own. Stronger together.
Flow connects the systems around Zagru One — ERPs, e-invoice integrators, FTP drops, SOAP services — and journals every event on the way. It connects any other systems just as well, so it is sold on its own.
Questions
What buyers ask us first.
Is this another no-code automation tool?
It is an operational integration platform: databases, files, SOAP and on-premises systems first, with a durable journal behind every run. It is built for the integrations a company cannot afford to lose.
What does "no data loss" mean exactly?
Every accepted event is journaled durably and ends in one of three ways: completed, compensated, or flagged "outcome unknown" for a person to resolve. We do not claim exactly-once effects on external systems; idempotency keys make retries safe.
How was that tested?
In a 1,000-run chaos test with 82 forced process kills and 588 node restarts, all 1,000 runs succeeded, no event was lost and each of the 5,000 test side effects was applied exactly once.
What does it need to run?
PostgreSQL — nothing else is mandatory. A small installation runs on 2 vCPU and 4 GB of RAM, database included.
Can it reach systems behind our firewall?
Today, by installing Flow on your own servers. An outbound-only Agent that needs no open inbound ports is on the roadmap.
Is it available today?
Zagru Flow is in early access. We are working with a small number of design partners; request a demo to join.
Draw your hardest integration.
Bring the one that breaks every month. We'll draw it with you.
Or write to hello@zagru.com