Integrations
Connect external services to AI chat, projects, and published app users without exposing provider credentials
Integrations give Swarmz a controlled way to read or change data in another service. Credentials stay encrypted behind the connector gateway; they do not enter project source or chat.
Every connector has its own page in the Integrations menu. The pages are grouped by product area so you can find setup, supported operations, example prompts, verification, and recovery steps without scanning one long catalog.
Choose the connection mode
| Mode | Who authorizes it | Where it works |
|---|---|---|
| Shared project | A workspace member | AI builds and linked project server operations |
| Published app user | Each signed-in app user | Only that app user's account inside the published app |
| Personal AI | The person using AI chat | Build context and MCP tools for that person |
| Project setup | A project owner | Generated app code and provider configuration |
Compare the connection modes before adding authorization to a published app. A personal AI connection does not silently become a credential for the published app.
How availability works
An administrator controls whether each connector is visible. OAuth connectors also require the administrator to configure the Swarmz OAuth application before users can see or authorize them. API-key connectors need only admin visibility; the workspace supplies its own provider credential when it connects.
Unavailable provider integrations such as Aikido Security, Wiz, and Paddle remain hidden from users and are marked honestly in the admin catalog. Swarmz does not show a credential form or teach the AI to claim capabilities that do not have a working provider contract.
What the AI can do
The AI sees only the registered operations for available, connected providers. It asks for the right connection when a prompt needs one, and write operations pause for approval unless the user has already approved that exact action.
Examples:
- “List our Slack channels and build a notification setting for the selected channel.”
- “Search Notion for the launch checklist and create a project status page.”
- “Read our Granola notes from this week and extract decisions and follow-ups.”
- “Create a Linear issue when a support report is confirmed.”
- “Build a HubSpot deal board for the connected pipeline.”
- “Use the signed-in user's Google Calendar to show their next five events.”
- “Use my personal Atlassian connector to summarize the linked Jira issue while we build.”
The AI does not receive raw credentials. A generated server route calls the connector gateway with the project, connection, provider, and operation it is allowed to use.
Connect and verify
Open Settings → Integrations and choose the provider.
Authorize the provider or enter the requested workspace credential.
Link a shared connection to the project, or complete the published app-user or personal AI setup shown on the connector page.
Run the connector page's smallest read test before trying a write.
Use Test a connector for the common read, write, reconnect, and isolation checks. The individual connector page adds provider-specific checks and recovery steps.
Disconnect safely
Open the connected provider under Settings → Integrations and select Disconnect or Remove. This deletes the stored Swarmz authorization and blocks new operations. It does not delete records in the provider.
If a credential may have leaked, revoke or rotate it in the provider first, then reconnect in Swarmz and repeat the smallest read test.