Govern

An integration is a project-scoped connection to an external provider. It gives Mobius the credentials and configuration needed to call provider actions, receive provider events, or use provider-backed models.

Loops and agents refer to stable action, event, and model names. They do not carry the provider's raw credential.

Integrations or secrets?

Use an integration when Mobius knows the provider. The connect flow asks for the right credential shape, and the provider's actions become available without copying secrets into a loop.

Use a secret for your own worker code or a provider Mobius does not model yet.

If the provider appears under Library > Integrations, use the integration. Otherwise keep the credential in a secret and call it from a worker action.

Connect a provider in the app

1. Open Library > Integrations.
2. Choose the provider.
3. Complete its OAuth, API key, app installation, or account selection flow.
4. Return to the integration page and confirm it appears as connected.

The catalog separates connected providers, providers ready without project credentials, and providers that still need setup. A provider logo means the capability exists in the catalog; connection state says whether this project can use it now.

Provider-specific pages in the integration catalog show the exact connect flow, actions, events, and troubleshooting steps.

What a connection enables

Depending on the provider, an integration may enable:

• Actions that agents or loop steps can call.
• Events that start loops or resume waiting steps.
• Reference pickers for repositories, channels, teams, documents, or other provider-owned objects.
• Model routes backed by the connected account.
• Recent event and delivery status for diagnosis.

Not every provider supports every capability. The provider detail page shows what becomes available after connection.

Use reference pickers

When the loop editor offers a picker for a channel, repository, team, document, or other provider object, use it instead of pasting an opaque ID. The picker checks the connected account and reduces mistakes from stale names or missing permissions.

Diagnose a missing event

Open the integration's recent activity first. If Mobius never received the provider event, check the provider installation, webhook, or account scope. If the event appears in Mobius, inspect the related source event and trigger match.

This separates provider delivery from loop configuration. Changing a trigger cannot fix an event the provider never sent.

Rotate credentials

Rotate or reconnect credentials from the provider detail page. Loops and agents keep referring to the same stable action and event names, so the credential can change without editing every consumer.

Never place plaintext provider keys in loop inputs or step fields. Those values can appear in run history and logs.

Next

• Browse providers in the integration catalog.
• Call connected capabilities through actions.
• React to provider events with triggers.
• Store custom credentials with the Secrets API.