When agents react to Salesforce triggers—deal stage changes, case escalations, renewal alerts—MultiMail ensures every outbound email passes the right approval gate before it reaches your customer.
Salesforce Flows, Apex triggers, and Einstein AI can detect the right moment to reach out to a customer. What they cannot do is safely hand that email to an AI agent without human review. CRM-native email tooling has no concept of graduated autonomy—it either sends or it doesn't.
MultiMail sits between your Salesforce automation and the outbound SMTP layer. Agents receive CRM event data via webhook or direct API call, compose a response, and submit it through MultiMail's oversight pipeline. A gated_send configuration holds the message in a pending queue until a human approves it in the MultiMail dashboard or via a webhook callback.
This matters most in regulated industries. Salesforce is widely deployed in financial services, healthcare, and insurance—sectors where FINRA, HIPAA, and GDPR impose strict controls on AI-generated customer communications. MultiMail's approval audit log gives compliance teams a per-message record of what was sent, when, and by which agent identity.
The integration requires no Salesforce package installation. You call the MultiMail REST API from an Apex class, a Flow's HTTP callout action, or an external agent process that consumes Salesforce event data via Platform Events or Change Data Capture.
Salesforce can fire a trigger the moment a deal closes or a case breaches SLA. MultiMail's gated_send mode intercepts the agent's outbound email and holds it for human review before delivery—preventing premature or incorrect customer communications from shipping automatically.
Agents operating across multiple Salesforce orgs or business units can be bound to specific MultiMail mailboxes. Each mailbox has a verified sending identity, so customer-facing email always comes from the correct domain and passes DKIM and SPF checks—not from a shared alias or unverified relay.
Every message processed by MultiMail—whether approved, rejected, or cancelled—is logged with agent identity, timestamp, oversight mode, and approval decision. This satisfies GDPR Article 22 documentation requirements and FINRA record-keeping rules for AI-assisted customer outreach.
If an agent dispatches an email and a human reviewer catches an error, a POST to the mailbox's email-cancel route revokes delivery before it leaves the queue. Salesforce's native email actions have no equivalent recall mechanism once triggered.
MultiMail webhooks deliver inbound email payloads to any HTTPS endpoint, including Salesforce Platform Event ingestion endpoints or external agent processes. Customer replies to agent-sent emails can be parsed, classified, and written back to the relevant Case or Opportunity record.
No code, no dashboard. Paste this to your AI agent — it connects MultiMail, creates an inbox, and builds the flow for you.
Sign up at multimail.dev and create a mailbox for your Salesforce-connected agent. Use a subdomain of your company domain (e.g., sales@acme.multimail.dev) or verify your own domain to send from support@yourdomain.com. Copy your API key from the dashboard—it starts with mm_live_ for production or mm_test_ for sandbox testing.
In Salesforce Setup, create a Custom Label named MultiMail_API_Key and paste your mm_live_ key as the value. Custom Labels are org-level constants that Apex can read at runtime without hardcoding credentials. For Named Credentials, configure an external endpoint pointing to https://api.multimail.dev with the Authorization header set to Bearer {your_key}.
Oversight is configured on the mailbox, not per send. Create the mailbox with gated_send for any customer-facing email that needs human review. Use monitored if you want autonomous sends with a notification trail, or autonomous only after your team has validated the agent's output quality. Start with gated_send during development.
In the MultiMail dashboard under Settings > Webhooks, add your endpoint URL (e.g., https://your-agent-host.com/webhooks/multimail). Subscribe to the email.received, email.delivered, and email.bounced event types. Your handler matches each event back to the originating Salesforce record by the thread or address it carries.
Use a Salesforce Developer Edition or sandbox org paired with a MultiMail mm_test_ key. Trigger your Flow or Apex callout manually, confirm the message appears in list_pending, approve it from the dashboard, and verify your webhook handler receives the message.approved event and writes the outcome back to the Salesforce record.
Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a hosted MCP server. Formally verified in Lean 4.