Integrations
Integrations & BYOK
SoConnective connects to third-party services on a bring-your-own-key (BYOK) basis: each account supplies its own credentials, stored in the tenant-scoped integrations collection. The set of connectable services is not hard-coded — it is a dynamic catalog that platform admins manage as data, so new providers can be added without shipping code (see Adding an integration provider).
The provider catalog
The catalog lives in the integration-providers global collection, managed by platform admins. Each entry is a pre-connection: everything a user needs to connect a service, packaged ahead of time.
| Field | Purpose |
|---|---|
| Logo | Visual identity in the Marketplace |
| Description | What the provider is / does |
| Category | Grouping in the catalog |
| Auth type | How the provider authenticates |
| Credential label / hint | What to paste, and a hint for the field |
| Help URL + instructions | Exactly where to find the key |
| Key | Stable provider identity (e.g. anthropic) used by the system |
Seeded providers
Seven providers ship pre-seeded in the catalog:
| Provider | Key | Category |
|---|---|---|
| Anthropic | anthropic | AI |
| OpenAI | openai | AI |
| Stripe | stripe | Payments |
| Twilio | twilio | Messaging |
| SendGrid | sendgrid | |
| Google Calendar | google-calendar | Calendar |
| Meta Ads | meta-ads | Advertising |
The install → key flow
- Browse providers in Marketplace → Integrations — each shows its logo, category, and description.
- Install / Connect opens a dialog that includes the "where to find your <key>" help link plus a paste field.
- You then choose one of two paths:
- Paste the key now — the key is saved, and the connection is tested immediately.
- "I'll add it later" — a disconnected row is created so the provider is installed but not yet connected.
Managing keys — Settings → Integrations
Once installed, providers appear under Settings → Integrations, which lists your installed providers and lets you manage keys:
- the provider logo
- the connection status
- a masked key field
- Save and Test actions
This is purely key management — you add, update, and test credentials here. A provider added with "I'll add it later" is connected by pasting and saving its key on this screen.
How the key is resolved for the AI
Provider identity is the catalog key (for example, anthropic). When the AI needs a credential, getAiConfig resolves the tenant's key for that provider. If the account has not supplied its own key, the platform key is used as a fallback. This is the mechanism behind Inbox AI's BYOK model — see AI architecture.