Skip to main content
Short answers to the questions people ask most about connecting ModuleX to the services you already use, so your workflows and the Assistant can act on your behalf. For the full detail, follow the link in each answer.

Integrations overview

Connect ModuleX to 175 services and call their tools from workflows and the Assistant.

Authentication & credentials

How integrations authenticate: OAuth2, API keys, bearer tokens, and managed keys.

Integration catalog

Browse the full catalog of 175 integrations by category.

Managing credentials

Create, set a default, test, and remove credentials in the app or via the API.

​
Credentials & integrations

Add a credential for the service you want to use. For an OAuth integration you click connect and approve access on the provider’s site (for example GitHub); for a key-based integration you paste an API key or token. Adding and managing credentials needs an owner or admin role on the organization. See Authentication & credentials for each connection type.
There are 175 integrations available today, spanning developer tools, communication, CRM, data, and more. Browse them all in the integration catalog, or read the integrations overview for what they can do.
A tool usually only becomes available once you have connected its integration. Add a credential for that service and its actions appear for use in workflows and the Assistant. See Managing credentials.
Yes. With bring-your-own-key (BYOK) you supply your own credential for a provider, and that usage is billed by the provider directly — it is not charged in ModuleX credits. ModuleX-managed keys are the alternative and are metered in credits. See Authentication & credentials and Credits & metering.
Credentials are encrypted at rest with a key scoped to your organization and the specific credential, so they cannot be reused outside it. Secrets are decrypted only when a tool runs, and the API returns masked values (for example start***end) rather than the raw secret. See Data security & encryption and Credentials & OAuth2.
For most providers, OAuth tokens refresh automatically just before they expire, so you do not need to do anything. If a connection breaks, reconnect the credential — remove it and connect the service again. The manual “refresh” action in the app is a known limitation and may not work, so prefer reconnecting. See Managing credentials.
Yes, but not from inside the app yet. You add a custom integration by packaging it as code (a tool package the runtime discovers) or by connecting a custom MCP server. See Build an integration to get started.
Connecting, testing, and removing credentials all require an owner or admin role on the organization. If a teammate cannot add or see a credential, check their role under Account & access.

Knowledge (RAG)

Connect a provider key for BYOK embeddings or an external vector store.

Known limitations

The OAuth refresh button and other things to be aware of.

Errors & troubleshooting

What a 401, 402, or 403 means and how to clear it.