GATEWAY

Every flow can be an API endpoint

Publish a workflow as a versioned, authenticated HTTP route. Your integration layer becomes something you can see, not a folder of glue code nobody wants to inherit.

A paper craft circuit board in mauve, with lilac and teal ribbon traces routing out to an envelope, a calendar and a database.
editor.flomation.app/gateway
Gateway routes5 live+ New route
GET
/v1/customers/:id
customer_lookup.flow
24ms
POST
/v1/orders
order_intake.flow
86ms
POST
/v1/invoices/reconcile
reconcile.flow
142ms
GET
/v1/stock
stock_levels.flow
31ms
DELETE
/v1/sessions/:id
session_revoke.flow
18ms
Auth: API key + per-route scopes · Rate limit: 600 req/min · Region: eu-west-2

An integration layer you can read

01

Publish in one click

Any flow gets a URL, an OpenAPI spec and a versioned contract. No deploy pipeline to build.

02

Auth, limits, versions

API keys, OAuth, scoped permissions and rate limits are configuration, not code you maintain.

03

Front your legacy systems

Wrap an old ERP or a SOAP endpoint in a clean REST route without touching the thing behind it.

04

Debug a real request

Every call is a run you can open, inspect node by node and replay with the same payload.

05

Change without redeploying

Adjust the logic on the canvas, publish a new version, roll back if it misbehaves.

06

Runs where you need it

Managed in our cloud, or on your own runners inside your network for regulated workloads.

Turn a flow into an endpoint

Build the logic on the canvas, publish it as a versioned route, and hand the rest of the business a URL instead of a folder of glue code.

Free to start, and the same routes run in our cloud or on your own runners.