Integrations & API

Integrations at /settings/integrations connect Limnn to the tools your teams already use, and Settings > Developer (/settings/developer) provides programmatic access for your own systems: API keys, request logs, webhooks and the MCP server. Both are admin-controlled and audited.

Connecting an integration

1. 1Open /settings/integrations and find the app (email, calendar, messaging, storage, automation or payments).
2. 2Choose Connect and complete the provider's authorization flow.
3. 3Choose the scope: which teams or modules may use the connection.
4. 4Run the built-in test and confirm data flows in the expected direction.
5. 5Review the connection's status regularly; expired credentials show as needing reauthorization.

API keys

1. 1Open Settings > Developer > API keys (/settings/developer/api-keys; the old /settings/api-keys address redirects here) and choose Create key.
2. 2Name it after the system that will use it, add a description and an expiry, and tick only the per-object read or write scopes it needs.
3. 3Copy the key immediately; it is stored hashed and is displayed only once.
4. 4Store it in your secrets manager and rotate on a schedule or when staff change.

Webhooks and automation

Register webhook endpoints in Settings > Developer > Webhooks, where you can send a test, pause or resume an endpoint and resend recent deliveries. To act on record events without code, use Flows (/flows) or Simple rules (/settings/automations). Verify webhook requests on the receiving side, and make handlers idempotent because deliveries can be retried. See Developer platform & MCP server for logs and trace ids.

• Prefer OAuth connections over shared passwords.
• Give each external system its own key so one can be revoked alone.
• Import data through /settings/import rather than building a one-off script when possible.
• Check /settings/audit for who created or changed connections and keys.