Build
Integrations
An integration connects another service to your Mobius organization. Connect Slack to post messages, GitHub to react to repository events, or a model provider to use your own account.
Connect a provider
- Open Library > Integrations.
- Choose the provider.
- Complete its sign-in, API key, app-install, or account-selection flow.
- Return to the provider page and confirm the connection is ready.
A connection belongs to the organization, not to any one agent. Reconnecting an account or rotating its key does not require editing the agents that use its actions.
A connection can make several things available:
- Actions that an agent can call.
- Events that Mobius records when the provider reports a change.
- Pickers for channels, repositories, documents, and other provider data.
- AI models billed through the connected account.
- Activity records for diagnosing missing events or failed calls.
Not every provider offers every capability. Open its detail page to see what is
ready in your organization. The mobius CLI cannot connect providers yet;
use the app or API.
Slack and Telegram can also back agent messaging, where incoming messages go directly to an agent conversation.
Browse the catalog
The integration catalog is the list of providers your organization can use. Mobius builds it from the organization's connection state plus the provider, action, and event registries.
| Catalog source | Contributes |
|---|---|
| Provider registry | Provider metadata, auth kind, and connect mode. |
| Action registry | Action names, schemas, readiness, and usage. |
| Event registry | Provider event names and payload schemas. |
| Organization integrations | Connection readiness and credential source. |
Read the live app catalog before assuming a provider is ready. A deployment can enable or hide a provider, and an organization can use either Mobius-managed platform credentials or its own connected credentials.
Google providers share a few credential rules. Start with Google integrations when you are connecting a Google provider.
Provider types
| Type | How it works | Use when |
|---|---|---|
| Connected provider | The organization stores the provider credential. | You need provider actions or events to run with your account. |
| Built-in provider | Mobius supplies the credential and marks the provider ready without an organization-local row. | The provider is read-only or platform-funded and your own quota is not required. |
| Action-only provider | Actions exist, but the provider does not implement the managed connect flow yet. | Create an integration row directly until the provider gets a first-class connect screen. |
| Model provider | The integration stores a model API key for agents, not an action catalog. | You want agents to use your model account instead of the default model route. |
| MCP server | The integration points to a remote Model Context Protocol (MCP) server. | You already operate an MCP server and want its tools available inside Mobius. |
When in doubt, use the provider catalog in the app. It shows the exact readiness and credential source for the current organization.
Current providers
| Provider | Provider ID | Auth kind | Actions | Events |
|---|---|---|---|---|
| Anthropic | anthropic | api_key | No | No |
| Apollo.io | apollo | api_key | Yes | No |
| Bitbucket Cloud | bitbucket_cloud | oauth2_user | Yes | Yes |
| Discord | discord | api_key | Yes | No |
| Firecrawl | firecrawl | api_key | Yes | No |
| Gmail | gmail | oauth2_user | Yes | Yes |
| GitHub | github | github_app_install | Yes | Yes |
| Google Ads | google_ads | oauth2_user | Yes | No |
| Google Calendar | google_calendar | oauth2_user | Yes | Yes |
| Google Gemini | gemini | api_key | No | No |
| Google Drive | google_drive | oauth2_user | No | Yes |
| Google Places | google_places | api_key | Yes | No |
| Google Sheets | google_sheets | oauth2_user | Yes | No |
| HubSpot | hubspot | oauth2_user | Yes | Yes |
| Jira | jira | api_key | Yes | Yes |
| Linear | linear | api_key | Yes | Yes |
| MCP server | mcp | api_key | Dynamic | No |
| Notion | notion | oauth2_user | Yes | Yes |
| OpenAI | openai | api_key | No | No |
| OpenRouter | openrouter | api_key | No | No |
| Polymarket | polymarket | none | Yes | No |
| ScrapeCreators | scrapecreators | api_key | Yes | No |
| SendGrid | sendgrid | api_key | Yes | No |
| Slack | slack | oauth2_user | Yes | Yes |
| Telegram | telegram | api_key | Yes | Yes |
| Twilio SMS | twilio | api_key | Yes | No |
| X | x | api_key | Yes | Yes |
| xAI Grok | xai | api_key | No | No |
Some providers appear only when the deployment has the backing service configured. The catalog endpoint is the final source of truth for your organization.
Inspect the catalog
From the app
Open Library > Integrations to see provider readiness and connection state. Provider detail pages show available actions, source events, webhook endpoints, and recent provider events.
Open Library > Actions when you need input schemas, output schemas, action annotations, or direct invocation.
From the CLI
The mobius CLI can inspect the action and event catalogs:
mobius catalog list-actions
mobius catalog get-action slack.message.post
mobius catalog list-eventsThe CLI does not connect integrations yet. Use the app or HTTP API for connection setup.
From the API
Use the provider catalog endpoint when you are building your own admin surface or authoring tool. Use the action and event catalog endpoints when that tool needs exact names and schemas. The CLI commands above call those same catalog endpoints.
Connect through the API
Most providers use a generic connect endpoint under
/v1/integrations/providers/{provider}/connect. Redirect
providers return a redirect_url; inline providers return an integration row.
Provider pages list the body shape and endpoint to use, and the API reference
has the exact schema.
Action-only providers use POST /v1/integrations until they
have a managed connect endpoint.
Actions and events
Provider actions run inside Mobius and use the resolved credential source for the organization. A ready organization-owned integration wins over a platform credential. If an action posts, deletes, merges, sends, or mutates upstream state, retries can repeat that side effect. Use idempotency fields where the provider supports them, or have the agent open an interaction before an irreversible call.
Provider events enter Mobius as integration events. Mobius then turns them into source events, which carry a normalized event type and payload:
github.pull_request.openedPrefer exact event names. Use a trailing wildcard, such as github.*, only when
every event under that prefix is worth recording.
Next
- Use provider credentials from integrations.
- Grant provider actions to an agent from actions.
- Receive outside changes with source events.
- Get the result back in your software with interactions.
- Check wire-format names in the event catalog.