Visual AI Email Workflows with Rivet

Add email sending, reading, and management to Rivet's visual agent builder — with full oversight controls and real-time debugging of every email action.


Rivet is a visual AI agent builder by Ironclad that lets you design, test, and debug complex AI workflows through a node-based graph editor. By integrating MultiMail, your Rivet graphs gain email capabilities that include sending, reading, replying, and managing contacts — all visible in Rivet's real-time execution debugger.

MultiMail's oversight modes pair naturally with Rivet's debugging philosophy. You can see exactly how your agent decided to compose an email, then review it in MultiMail's gated_send queue before delivery. This end-to-end visibility from agent reasoning to email delivery makes building trustworthy email agents straightforward.

Connect Rivet to MultiMail using HTTP Request nodes that call the REST API, or build custom Rivet plugins that wrap MultiMail endpoints for reusable email nodes in your graphs.

Built for Rivet developers

End-to-End Debugging Visibility

Rivet's execution visualizer shows agent decision-making in real time. Combined with MultiMail's audit log, you get complete traceability from the moment an agent decides to send an email through to delivery.

Graduated Trust for Visual Workflows

Start your Rivet email workflows in gated_send mode where every email is queued for human approval. As you refine and debug the graph, progressively relax oversight to monitored or autonomous mode.

Plugin-Based Email Nodes

Rivet's plugin system lets you wrap MultiMail API calls into reusable nodes. Create custom send_email, check_inbox, and reply_email nodes that appear natively in Rivet's node palette.

Dataset-Driven Testing

Rivet's dataset feature lets you test email workflows against multiple scenarios. Feed different email contexts through your graph and verify the agent composes appropriate responses before going live.


Try it with your agent

No code, no dashboard. Paste this to your AI agent — it connects MultiMail, creates an inbox, and builds the flow for you.

1. Get MultiMail ready. Read https://multimail.dev/llms.txt, follow it exactly to connect the MultiMail MCP server, create a free inbox for this Rivet agent, and set up a verified sending domain. Use only the MultiMail capabilities documented there. 2. Wire MultiMail into Rivet using Rivet’s real integration path: build or update the Rivet graph with External Call nodes, then expose the corresponding host-side functions through @ironclad/rivet-node externalFunctions when running the graph. Those functions should call the connected MultiMail MCP server, not invented HTTP APIs. 3. Give the agent three email capabilities through those External Call nodes: check the inbox, draft a reply, and send or schedule an email. Keep message composition separate from sending so the graph can review drafts before delivery. 4. Send a test email from the verified sender to a developer-controlled address, then check the MultiMail inbox and Rivet live debugger output to confirm the graph records each email action clearly. 5. Run MultiMail in gated_send oversight mode for this setup. Before any email sends, require the developer to review and approve the recipient, subject, body, and timing; do not switch to monitored or autonomous until explicitly asked.

Step by step

1

Create a MultiMail Account and API Key

Sign up at multimail.dev, create a mailbox, and generate an API key from your dashboard. Your key will start with mm_live_.

2

Install Rivet

Download the Rivet desktop application or install the Node.js SDK for programmatic graph execution.

3

Add HTTP Call Nodes

In your Rivet graph, add HTTP Call nodes pointed at MultiMail API endpoints. Set the Authorization header to your API key and configure request bodies for send, inbox, and reply operations.

4

Test with the Debugger

Run your graph in Rivet's visual debugger to see each node's execution in real time. Verify that email API calls return the expected responses and that the agent's reasoning is sound.

5

Approve Pending Emails

If your mailbox uses gated_send mode (the default), review and approve pending emails in the MultiMail dashboard before they are delivered.


Common questions

Does Rivet have a built-in MultiMail integration?
There is no built-in MultiMail node in Rivet. You integrate MultiMail using Rivet's HTTP Call nodes to call the REST API, or by building a custom plugin that exposes MultiMail tools as native graph nodes. Both approaches give you full access to email capabilities.
Can I debug email actions in Rivet's visual debugger?
Yes. Rivet's real-time execution visualizer shows the input and output of every node, including HTTP Call nodes that interact with MultiMail. You can see the exact API request, response, and how the agent used the email data in subsequent reasoning steps.
How do I test email workflows without sending real emails?
Use MultiMail's gated_send mode during development. All emails are queued for approval rather than sent immediately, so you can inspect what your Rivet graph would send without any messages actually being delivered. You can also use Rivet's dataset testing to validate against multiple scenarios.
Can I share Rivet graphs that use MultiMail?
Yes. Rivet project files are portable. Store your MultiMail API key in Rivet's settings or environment variables rather than hardcoding it in the graph, so shared projects don't expose credentials. Each collaborator configures their own API key.

Explore more

The only agent email with a verifiable sender

Email infrastructure built for AI agents. Verifiable identity, graduated oversight, and a hosted MCP server. Formally verified in Lean 4.