Reference

An integration is an account you connect so Mobius can use it. Connect Slack and your agents can post to Slack. Connect Google Workspace and they can read mail, check calendars, and write to spreadsheets.

Connecting one is the sign-in flow you already know: click the provider, sign in, approve the permissions, done. Mobius holds the connection so you never paste a password into a job.

Your jobs and agents refer to what they want to do, not to the credential. When you reconnect an account or rotate a key, nothing that uses it needs editing.

Connecting one

1. Open Library > Integrations.
2. Pick the provider.
3. Complete its sign-in, API key, app install, or account selection.
4. Come back to the integration page and confirm it says connected.

The catalog separates three groups: providers you've connected, providers that work without any setup, and providers that still need you to do something. A logo means Mobius supports it; the connection state tells you whether this organization can use it right now.

Each provider has its own page in the integration catalog with the exact steps, what becomes available, and what to do when it goes wrong.

A provider can hold more than one connection at a time, and each one belongs to somebody. A connection you make to your own account — your mailbox, your calendar — is yours: only you and the agents you have allowed to act through it can use it. A connection to a shared workspace, or to a keyed service like a scraping API, belongs to the organization and everyone can use it. An agent can hold its own, so a shared assistant sends from its own address rather than from whoever happened to talk to it last.

Name each connection for what it is. Two people can both call theirs "work"; what has to stay distinct is two connections the whole org shares.

What you get from a connection

Depending on the provider, connecting can give you:

• Actions your jobs and agents can call.
• Events that start jobs when something happens over there.
• Pickers in the editor for channels, repositories, documents, and so on, so you're choosing from a list rather than pasting an ID.
• AI models backed by that account.
• Recent activity, which is where you look when something isn't arriving.

Not every provider does all of these. The provider's page says what to expect.

When the provider isn't in the catalog

Your PSA, RMM, documentation platform, or backup console probably isn't here yet. This is the most common question we get, and the answer is that it's usually a solvable afternoon.

Most of these platforms can do two things, and those two things are all you need:

Getting work into Mobius. The simplest path is email: point a notification at an agent's email address. A ticket is created, your PSA emails the agent, the agent gets a turn with the ticket's details in it, and its answer goes back on the same thread.

If the platform can call a URL instead, have it call the Mobius API and start a session with the agent, passing the ticket as the message. See behind your own software.

Getting Mobius to act on it. If the platform has an API, create a custom HTTP action under Library > Actions. From then on it behaves like any other action.

For anything that has to stay inside your network, a worker is the third option.

Integration or worker?

Use an integration when Mobius knows the provider. The connect flow asks for exactly the right thing and the actions appear on their own.

For a provider Mobius does not model yet, keep credentials in your own secret manager and call it from a worker. Mobius does not offer a general-purpose secrets store.

Quick test: if it's under Library > Integrations, use the integration. Otherwise keep the credential behind your worker boundary.

Use the pickers

When the editor offers you a picker for a channel, repository, team, or document, use it rather than pasting an ID.

The picker checks the connected account as you choose, which catches a stale name or a missing permission right there, instead of at 3am when the job runs.

When an event doesn't arrive

Check the integration's recent activity first, before touching anything else.

If Mobius never received the event, the problem is on the provider's side: the app isn't installed, a webhook isn't configured, or the account is missing a permission. If the event did arrive, the problem is the event name or condition whatever was waiting for it used.

That order matters. Editing a wait cannot fix an event that was never sent, and people lose hours to that. Source events walks the whole path.

Rotating credentials

Reconnect or rotate from the provider's detail page. Everything that uses the integration keeps working, because agents refer to capability names, not to the credential itself.

Warning: Never paste a provider key into a message to an agent or into an action's inputs. Those values show up in the session transcript, which plenty of people can read. Use an integration or keep the credential inside your worker's secret store.

Next

• Browse what's supported in the integration catalog.
• Call connected capabilities with actions.
• Wait on something happening elsewhere with source events.