Choose a connection path based on the system and action: connect a sending mailbox in Dureach, use the customer API or webhooks for custom data flows, or connect an MCP-capable AI client. Provider options and permissions depend on the workspace, so check the available settings before planning a connection.
Connection options
In-app sender accounts
Open Email → Add New and choose a provider shown in the workspace or the supported SMTP/IMAP fields. This setup guide covers mailbox sending, replies, and account-level limits. It does not confirm a native CRM connector list or field-level sync behavior; check those details in the workspace before planning a CRM sync.
Connect an email provider and review sending settings
APIs and webhooks
Use Dureach’s customer API resources for custom integrations. Create an OAuth service account with only the scopes the job needs. Configure webhooks in Settings → Integrations, test delivery against a non-production receiver, and make the receiver safe to retry. Use documented customer API paths; an internal application route is not automatically a public endpoint.
MCP-capable AI clients
Connect an external AI client to Dureach through MCP streamable HTTP and workspace OAuth. The tools available to a client depend on its grants and workspace access. Start with read scopes; review approval policies before enabling writes or sends. Check the client’s data handling and retention terms before sharing workspace information with it.
- Connect External AI via MCP
- Connect an AI client and review MCP access
- Review MCP approvals, policies, and quotas
Before you connect
Confirm the destination workspace and your permission to connect it. Limit access to the fields and actions the workflow needs. Test in a non-production destination, verify the connection status and activity log, and know how to revoke or disconnect access.
