Connection Model
Last updated September 21, 2026
Choose between OAuth, bot-token, webhook, SMTP/IMAP, and external-tool connection models in Matruno.
User-scoped connections#
Use OAuth when actions must reflect a connected account or provider connection. Gmail uses OAuth-specific routes and stored email credentials for legal correspondence and inbox monitoring. Nango-backed provider status is exposed for providers such as Slack, Notion, Google Drive, and Linear, but provider configuration must exist in Nango.
Workspace bot connections#
Telegram is implemented as a workspace-scoped bring-your-own-bot flow. The backend validates the bot token with Telegram, registers a webhook URL, stores the encrypted token, and exposes test-message and disconnect routes.
Webhook channels#
Webhooks are used for event intake and outbound notifications. The webhook models include endpoint configuration, signing secret handling, delivery records, status, retries, response metadata, and workspace scope. Use them for legal-intake events you actually own, not as implied court or DMS feeds.
External tools#
External tools are workspace-scoped definitions with methods, URLs, headers, JSON schemas, timeouts, breaker state, and execution traces. Calls are designed to be visible through ExternalToolExecution records instead of disappearing into agent code.
Document connector intent and maturity
For each connection, state whether it is active, optional, configured, scaffolded, or only represented in a sample workflow. That distinction prevents overpromising during legal-ops rollout.
Was this helpful?