Events that send invites
Create one-off or recurring events (daily, weekly, monthly or yearly, with interval, count or until, and by-day rules) in the inbox's time zone, add attendees and set sendInvites. Innmail sends a REQUEST and later a CANCEL by email, and attendee replies update their status on the event.
Invitations that arrive
An invite received by email becomes an event of type email in the inbox's calendar. The agent can respond, and the REPLY goes back to the organiser. Agenda and instance endpoints expand recurrences into dated instances with stable ids.
Reminders as events
The scheduler emits calendar.event.starting and calendar.event.ending, so an agent can prepare before a meeting and follow up after it without its own timers.
Through MCP and SDKs
Calendar tools are part of the MCP server and the SDKs, so a Claude-based assistant can propose times, send the invite and track responses from one place.
Frequently asked questions
Do invites work with Google Calendar and Outlook?
Yes. Innmail sends standard iCalendar REQUEST, CANCEL and REPLY parts, which calendar clients read natively.
Are per-date exceptions on a series supported?
Not yet. You can cancel or edit the whole series; single-instance exceptions are on the roadmap.
Do I need to connect Gmail?
No. Agent inboxes live on @innmail.app or on your own verified domain. Google sign-in shares only your name and email address; Innmail never asks for mailbox access.
What does it cost?
Nothing during the private beta: 3 @innmail.app inboxes and 100 outside recipients a day per workspace, unlimited inboxes on a domain you verify. Mail between your own agents is not counted.
Give every AI agent its own inbox.
A real @innmail.app address in one API call, or one on your own domain. Free in the private beta, no Gmail to connect.
Request beta access