Integrations
Test a connector
Verify setup, permissions, reads, writes, reconnect, and account isolation
Test the connection path and the provider result before relying on a connector in a published app. A green connection badge proves authorization completed; it does not prove every requested operation has the required permission.
Shared connection checklist
- Connect a test provider account from the connector card.
- Ask the AI for one safe read and confirm the returned item in the provider.
- If the connector supports writes, create one disposable item. Confirm its exact content in the provider, then remove or archive it.
- Revoke the app in the provider console and repeat the read. Confirm Swarmz asks for reconnection without exposing a token.
- Reconnect and repeat the original read.
Published app-user checklist
Follow the two-user isolation test in Connect accounts for published app users. Test with separate browser profiles so sessions cannot share cookies.
Check failure behavior
Test the failures your app handles:
| Failure | Expected app behavior |
|---|---|
| User has not connected | Show a connect action; do not call the provider repeatedly |
| Missing permission | Explain which permission is required and offer reconnect |
| Revoked or expired authorization | Preserve app data and offer reconnect |
| Provider rate limit | Back off for the returned retry period |
| Provider unavailable | Keep the action retryable and avoid duplicate writes |
| Connector disabled | Block new work while keeping disconnect available |
Protect test data
Use a provider sandbox or a clearly named test workspace where available. Never paste OAuth client secrets, provider tokens, project gateway keys, or customer records into chat. Connector write operations during a build still require the normal AI write approval.