Skip to content
In development

Connect your tools, then repeat the steps

Being built to link outside tools, keep their keys safe and repeat routine steps for Ethen.

Flow is the connector, vault, retrieval, automation and event subsystem of Ethen Platform. It is part of the Platform, not a separate product.

Read the workflow docsApprovals & evidence

Ethen Platform owns Flow's control plane, and Ethen products reach Flow through the Platform.

Automation railIllustration

01 · Ethen products

Exists in development

Trigger or request from a product

Products reach Flow through the Platform, using versioned Flow contracts, and a caller ledger records which products call Flow. Event triggers that start automations are planned.

  • Exists in development
  • Local fixture
  • Planned
Illustration of how an automation is designed to move through Flow, not a capture: trigger, connector registry, credential vault, policy check, the Activepieces bridge (local fixture) and a receipt. Marks show what exists today.

01Directory

A connector directory, in fixture state

Flow is designed around a directory of connectors. Which connectors run first is not decided, so this one is a fixture: sample classes, filterable by category, with nothing to install.

Fixture directory. Sample connector classes written for this page. It is not a catalogue: no connector is available for general use today.

Illustration

Category

Showing 8 of 8 sample entries

Fixture data

  • Database

    Sample class: records in a database a workspace connects.

    DataPlanned

  • Retrieval source

    Sample class: a connected source that retrieval reads from. Retrieval over connected sources is planned.

    DataPlanned

  • Mail

    Sample class: messages in a mailbox.

    CommunicationPlanned

  • Team chat

    Sample class: posts and threads in a team chat tool.

    CommunicationPlanned

  • File storage

    Sample class: files and folders in a storage service.

    Files & codePlanned

  • Code repository

    Sample class: repositories, issues and reviews.

    Files & codePlanned

  • Webhooks & events

    Sample class: an incoming event that starts an automation. Event triggers are planned.

    EventsPlanned

  • Activepieces bridge

    The bridge to the open-source Activepieces engine, run against a local test fixture. It is not a connector you can use.

    EngineLocal fixture

  • Not decided

    Which connectors run first is not decided. This slot is empty on purpose.

02Vault rule

Credentials stay on the server side.

Provider keys and connector credentials are kept on the server side and are not sent to browsers.[1] A managed vault for connector credentials is planned.[2]

Security & trust model
Where a credential livesIllustration

Notes

  1. 1.This is a design rule; it has not been independently tested.↩
  2. 2.A managed vault for connector credentials, shared by every Ethen product, is planned.↩

03Engine bridge

Activepieces, community edition, local fixture

Flow reaches an open-source automation engine through a bridge. Today that bridge runs only against a local test fixture.
Read the workflow docs
ItemToday
EngineActivepiecesAn open-source automation engine, reached through a bridge inside Flow.
Edition in scopeCommunity edition, MIT licenceOnly the MIT-licensed community edition is in scope.
Commercial directories (ee/)Not shippedIts commercially licensed directories are excluded.
Where it runs todayLocal test fixtureThe bridge runs only against a local fixture.
Real third-party servicesNot connectedConnectors that run against real services are planned.
Release-gate and runbook documentsExistTheir results have not been re-run for this page.
Licence gate

Only the MIT-licensed community edition of Activepieces is in scope; its commercially licensed directories are not shipped.

04Evidence

What exists, what is planned, and the limits

Contracts, a caller ledger and the engine bridge exist in development. Connectors, the vault and retrieval are planned.

Implemented

  • Versioned Flow contracts, and a caller ledger that records which products call Flow.
  • Integration-authority documents that give each Flow responsibility a single owner inside the Platform.
  • A bridge to the open-source Activepieces automation engine, with a local test fixture.
  • Release-gate and worker runbook documents for Flow. Their results have not been re-run for this page.

Planned

  • Connectors that run against real third-party services. Which connectors run first is not decided.
  • A managed vault for connector credentials, shared by every Ethen product.
  • Retrieval over connected sources, and event triggers that start automations.

Limits

  • No connector is available for general use today.
  • We do not publish a connector count or catalogue.
  • Flow is not offered as a standalone product.
  • Only the MIT-licensed community edition of Activepieces is in scope; its commercially licensed directories are not shipped.
  • Not available for general use; nothing here is a release promise or date.

05Questions

Questions

  1. 01Is Flow a separate product?

    No. Flow is a subsystem of Ethen Platform. Products use it through the Platform, and it is not sold or offered on its own. Older pages that described Flow as a product now point here.

  2. 02Which connectors work today?

    None are available for general use. Contracts, a bridge to Activepieces and a local fixture exist in development; which connectors run first is still open.

  3. 03Which automation engine does Flow use?

    Flow has a bridge to the open-source Activepieces automation engine, which today runs only against a local test fixture. Only the MIT-licensed community edition is in scope; its commercially licensed directories are not shipped.

Status and related pages

Flow is part of Ethen Platform and is in development. No connector is available for general use today.

See availability