Email and calendar for your AI agents. A complete communication identity, provisioned with a single API call.
You can get an AI agent working. Then it has to communicate with someone. That’s where things start to break.
Today, we’re launching Nylas Agent Accounts. Every AI agent your team builds can have its own email address and calendar on your domain, created with a single API call. The agent can send, receive, schedule, and respond to invitations from a single inbox and calendar that Nylas hosts and you own.
An identity of its own
Until now, most AI agents have communicated through accounts that belong to someone else: a shared support inbox, an employee’s OAuth seat, or a transactional sender that only handles outbound. The agent is operating through someone else’s identity, not its own. Replies land in the wrong place, threads break, and the moment scheduling enters the workflow the team bolts on a second system.
Agent Accounts changes that. The agents you build get mailboxes they own, on your domain. Outbound messages come from the agent’s own address and replies come back to the same inbox. The calendar on that same identity handles invitations, RSVPs, and reschedules. Email and calendar are one account, not two.
The agent owns the conversation from the first email to the booked meeting.
How it works
Create an Agent Account from the Nylas Dashboard, or from the terminal:
nylas agent account create agent@yourcompany.com
The CLI wraps a single API call you can also send straight from your application:
POST /v3/connect/custom{ "provider": "nylas", "settings": { "email": "[email protected]" }}
You get back a grant_id. From there, the account works with every existing Nylas endpoint. The same /messages/send, the same /events, the same webhooks your team already uses for connected accounts.
When a reply arrives, message.created fires on delivery. The payload includes a thread_id so the agent can match the reply to the right conversation without parsing headers. When the agent confirms a meeting, the invitation goes out from the same address and lands natively in Gmail, Outlook, or Apple Calendar. RSVPs come back to the same account. A workflow that starts with outbound email and ends with a confirmed meeting stays in one identity from start to finish.
The same platform you already use
Agent Accounts runs on the same Nylas platform your team already uses. If you’ve built on Nylas before, provisioning an agent looks like any other Nylas call: one POST, a returned grant_id, and from there every endpoint you already use works for the agent too. The same Nylas Dashboard shows the agent’s activity, and your existing security approval already covers it.
What an agent can finish, not just start
Here are a few workflows your team can design once an agent has its own inbox and calendar.
A customer support agent owns the inbox at [email protected]. It reads incoming tickets, replies to the ones it can resolve, and escalates the rest with the full thread attached so a human picks up exactly where the agent left off. The customer never sees a handoff. They write to one address, and the right answer comes back, whether the agent or the team wrote it.
A BDR or CRM nurture agent runs personalized outbound from its own address. Replies land in the agent’s inbox, where it reads each response and decides what to do next: continue the sequence or escalate the lead. Because the messages come from a domain you control, deliverability and reputation are yours, not a shared sender’s.
An interview scheduling agent owns recruiting@ at your domain. When a candidate moves forward, the agent reaches out from that address with a few proposed times, pulled from the hiring manager’s actual availability. The candidate replies, accepting, asking for a different slot, or asking a question first. Each reply pings the agent, which reads the whole thread and responds: confirming, suggesting an alternative, or escalating to a recruiter. The calendar invitation comes from the same recruiting@ address and lands on the candidate’s phone as a normal event. The hiring manager only sees confirmed meetings on their calendar. Email and calendar share the same identity, so the loop closes inside one account.
In a multi-agent system, every agent has its own address. The agents reach each other and reach people over standard email and calendar, the same way humans do. Each agent’s sender reputation is its own.
One identity, top to bottom
Every other approach to agent communication stops at the inbox. Get the messages working, parse the replies, and the moment a workflow needs to schedule a meeting, you’re wiring in a second system with a separate identity and a separate source of truth.
Agent Accounts puts email and calendar on one account, on the same grant, behind the same API. The mailbox and calendar are one identity, not two systems with a bridge between them. A workflow can start with outreach and end with a confirmed meeting without ever leaving the account.
Built for production
Agent Accounts runs on the infrastructure Nylas has been operating for more than a decade, across billions of messages and thousands of production applications. Every Agent Account is covered by SOC 2 Type II, ISO 27001, ISO 27701, HIPAA, and GDPR on every plan, from the first account you create.
Works with the tools your team already uses
Agent Accounts ships with a native CLI, a hosted MCP server at mcp.us.nylas.com, and skill packs that pre-load Claude, Cursor, Codex CLI, and 40+ other coding agents with current Nylas context. Plus working examples for LangGraph, CrewAI, the Anthropic SDK, and the OpenAI Agents SDK that your team can use as a starting point.
Get started
Provision your first Agent Account on a free Nylas sandbox address in under five minutes. Send your first message, book your first meeting, and watch a reply land back in the agent’s inbox before your next standup.
Your agent is ready to do the part that used to break. Give it an address.
Email and Contacts API 
Calendar API & Scheduler 
Notetaker API 
Agent Accounts 
Sales & CRM 
Recruiting & ATS 
Healthcare
Financial
Legal
Real Estate
Education
Field Services
Docs
SDKs
Guides
Integrations
API status
Changelog
Support
Enterprise
