USE CASE · SCHEDULING

Build an AI scheduling agent that coordinates by email

e2a helps developers build scheduling agents that receive meeting requests, propose times, process replies, send confirmations, and preserve the agent's conversation state across multi-turn email threads.

Build your scheduling agent →See the runnable example ↗

THE WORKFLOW

What the agent does

  1. 01A participant emails the scheduling agent with a meeting request.
  2. 02The agent extracts attendees, constraints, and scheduling intent.
  3. 03It checks the application's availability source.
  4. 04It proposes times and waits for a reply.
  5. 05It updates state when participants accept, decline, or request changes.
  6. 06It sends a final confirmation and future reminders when appropriate.

WHY E2A

  • ✓Inbound webhook, WebSocket, REST, or MCP delivery
  • ✓conversation_id correlation for multi-turn state
  • ✓Threaded replies and message history
  • ✓Scheduled sending for supported beta workflows
  • ✓Optional review before confirmations or reminders are sent

START BUILDING

The integration stays small

Scheduling secretary runbook ↗
event = await client.inbound.next("[email protected]")
request = await scheduler.extract(event.data["text"])

reply = await scheduler.propose_times(request)
await client.messages.reply(
    event.data["delivered_to"],
    event.data["message_id"],
    {"text": reply},
)
# Bind conversation_id to your scheduler's session state

The agent owns the business logic. e2a handles the email identity, delivery, authentication evidence, and reply routing.

KEEP GOING

Connect the pieces

Quickstart →
Create an inbox and send your first message.
MCP server →
Give a local or hosted agent an inbox without an API key.
API reference →
Explore the stable /v1 operations.
Blog tutorials →
Follow framework-specific integration guides.

FAQ

Can an AI scheduling agent handle multiple replies in one conversation?

Yes. e2a preserves reply threading and exposes conversation_id so the application can rebuild scheduling state across multiple email turns.

How does an email scheduling agent remember the meeting context?

The application binds e2a's conversation_id to its own session or workflow state, while e2a handles inbound delivery, reply routing, and the email thread.

Can a scheduling agent work with local or private applications?

Yes. The agent can consume mail over WebSocket, REST polling, or MCP without exposing a public webhook endpoint, which works well for private calendar and scheduling systems.

Can scheduled messages be reviewed before they are sent?

For workflows using e2a's supported scheduled-sending and review features, outbound messages can be configured to require human approval before dispatch.

Build your scheduling agent

Open-source, free to start, and ready for your first agent workflow.

Get started →