Integrations Overview

Product surfaces#

LumenFlow currently exposes external integrations through three different product surfaces:

Connectors and channels#

Cloud publishes this table from the connector catalogue. It lists every connector and channel that is Ready or Limited. The catalogue is served at GET /api/v1/sidekick/catalog, and ?availability=ready returns only the ready entries.

• Ready means the connector is available for general use.
• Limited means the connector is real and installable, with a deliberately bounded set of governed actions.

Connection methods#

Depending on the integration, setup uses one of these methods:

How connections work#

1. You add a Tool Connection or channel in Settings → Connections
2. LumenFlow securely stores the credentials
3. Sidekick discovers the governed actions available from that integration
4. Governance rules control which actions are allowed

Reactive routine routing#

Inbound messages can match configured reactive routines through typed semantic judgment. Provider and channel settings remain eligibility checks. If judgment is disabled, denied, fails, times out, or no active routine can be judged, the message stays review-only with a visible reason; matching a configured keyword alone never starts a routine. Only a successful typed judgment can select an automatic run.

Connection lifecycle#

Connections and channels follow a state machine with clear health status:

  disconnected ──(add integration)──> connected
      ^                                    |
      |                              (needs config?)
      |                               /         \
      |                             no           yes
      |                              |            |
      |                              v            v
      |                       inbound_ready   action_required
      |                              |            |
      |                        (healthy)    (fix config)
      |                              |            |
      |                              v            v
      +──(revoke)──────────── active      degraded

OAuth tokens are refreshed automatically. You can revoke access at any time from settings.

For newer integrations, v1 means the integration is real and installable today, but intentionally bounded. LumenFlow exposes the most useful governed actions first and expands later instead of claiming the provider's full API on day one.

Security#

• OAuth tokens are encrypted at rest
• Credentials are never exposed in the UI after initial setup
• All connection activity appears in the audit trail
• Revoking a connection immediately stops all related actions