Integrations
Last updated September 21, 2026
Matruno includes specific integration surfaces for Gmail, Microsoft email support, Telegram, Nango-backed providers, webhooks, and external tool execution.
Implemented connector surfaces#
The repository supports these integration surfaces:
| Surface | Maturity in repo | Configuration |
|---|---|---|
| Gmail | Implemented connection status, authorization URL, token exchange, disconnect, callback, test email, token refresh, and inbox monitoring paths. | GMAIL_CLIENT_ID, GMAIL_CLIENT_SECRET, GMAIL_REDIRECT_URI, GMAIL_SCOPES |
| Microsoft/Azure email | Service and token-refresh support exists in backend dependencies/services. | AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, AZURE_REDIRECT_URI, GRAPH_SCOPES |
| Telegram | Workspace-scoped bring-your-own-bot connection, webhook registration, disconnect, test message, and webhook route. | PUBLIC_APP_URL or FRONTEND_URL, workspace bot token via API |
| Nango-backed providers | Thin Nango status/disconnect service for slack, notion, google-drive, and linear; missing provider config is reported as not configured. | NANGO_SECRET_KEY, NEXT_PUBLIC_NANGO_PUBLIC_KEY |
| Webhooks | Inbound webhook ingestion, outbound webhook config, delivery records, signing secret rotation, and test delivery routes. | Workspace settings and webhook routes |
| External tools | Workspace-scoped tool definitions and Temporal-backed execution traces. | /api/v1/webhooks/tools |
| SMTP/IMAP | SMTP/IMAP settings are present for email service and inbox paths. | SMTP_*, IMAP_* |
Email and webhook paths can support legal correspondence and intake. They do not connect Matruno to courts, e-filing systems, or case-law databases.
What not to claim#
Do not describe Matruno as "connect anything" or "all integrations supported." Example workflow JSON may mention other systems, but those names are examples unless a connector route and credentials exist in the repo or deployment.
Govern each connection#
Each integration extends what legal workflows and agents can do with confidential matter data. Define who can configure it, what scopes are allowed, where credentials are stored, how failures surface, and what audit trail proves the connection was used.
Optional by configuration
Most connectors require credentials and upstream provider setup. A route existing in the repo does not mean your local runtime is connected.
Was this helpful?