How to Build an Email-Based Workflow with Codex

Codex CLI operates in your terminal and works well with local files and code. Email is a gap: out of the box, it can’t send messages or receive replies. AgentPatch closes that gap by giving Codex three email capabilities — claim a dedicated address, send emails, and check an inbox — which is everything you need to build a complete, autonomous email workflow.

Why This Matters

A lot of developer workflows have an email component that currently requires a human: sending release notes, gathering stakeholder feedback, notifying users of status changes, following up on open questions. If the agent can both send and receive, it becomes a participant in those workflows rather than a tool you configure and then take over from.

With AgentPatch connected, Codex can initiate an email thread, monitor the inbox for replies, and act on the responses — all from a single terminal session.

Setup

Add AgentPatch to ~/.codex/config.toml:

[mcp_servers.agentpatch]
url = "https://agentpatch.ai/mcp"
bearer_token_env_var = "AGENTPATCH_API_KEY"

Then set your API key:

export AGENTPATCH_API_KEY=your_api_key

Replace your_api_key with your actual key from the AgentPatch dashboard. Codex discovers all AgentPatch tools automatically on next start.

Example

Say you’re managing a security audit and need external reviewers to confirm they’ve received a document and acknowledged a deadline.

“Claim a project email address. Then send a message to each person in reviewers.json asking them to confirm receipt of the security audit document and acknowledge the review deadline. CC the document link.”

Codex reads the file, claims an address, and sends a personalized confirmation request to each reviewer from the project address.

A day later:

“Check the project inbox and tell me which reviewers have confirmed receipt.”

Codex calls the Check Inbox tool and gives you a status report — who responded, who hasn’t.

“Send a reminder to anyone who hasn’t confirmed yet. Keep it short and friendly.”

Codex composes and sends follow-up messages to the non-responders. You didn’t have to cross-reference any list or open an email client. The agent tracked the state of the workflow and took the appropriate next action.

This pattern generalizes to any multi-step process that involves external parties: vendor evaluations, user research recruitment, beta access confirmations, compliance acknowledgements.

Wrapping Up

Building an email workflow with Codex requires one AgentPatch configuration. That same connection also gives you YouTube transcripts, web search, image generation, and the rest of the marketplace. Visit agentpatch.ai to explore everything available.

← Back to blog