AgentMail Gives Every Agent Inbox Its Own Calendar

AgentMail added a calendar to every inbox, the company said in its changelog. The calendar entered private beta in an Oct. 5 entry. On Oct. 8 AgentMail moved it to Labs. An organization admin can now switch it on without asking for beta access.

An agent can schedule and answer invitations by email

Every inbox has exactly one calendar, AgentMail’s documentation says. It uses the inbox address as its identity and is deleted with the inbox. Nothing needs to be created.

Agents can create one-off and recurring events through the API. With send_invites set to true, the inbox emails a standard iCalendar invitation to each attendee. It opens as a normal meeting invitation in Google Calendar, Outlook and Apple Calendar, the documentation says. The flag defaults to false. An agent can list attendees without emailing anyone.

The flow also runs the other way. When someone emails the inbox an invitation, the event appears on its calendar and the agent can accept or decline it. On Oct. 7 AgentMail added a field showing how the inbox has answered each event. An agent can find the invitations still waiting for a reply from the agenda alone. An invitation email now records the event it created. An agent can go from a message.received webhook straight to that event.

Webhooks tell the agent when a meeting starts and ends

AgentMail sends calendar.event.starting and calendar.event.ending webhooks for every one-off event and every date of a recurring one. The documentation says each is usually sent within a minute after the scheduled time and never early. An agent that wants to act ahead of time has to schedule that itself.

Four more event types cover changes: created, updated, deleted and responded. The API key that creates the webhook needs the calendar_event_read permission.

Invitation emails count against send limits

Invitations are ordinary mail from the inbox. Each one counts against the organization, pod and inbox send limits, one send per recipient. AgentMail charges the sends before it saves anything. A request that would exceed a limit returns 429 and changes nothing.

Labs is available only in US production at api.agentmail.to, not yet in the EU. An organization without access gets a 403. Each calendar holds 10,000 events by default. Edits use ETags and an optional If-Match header. Two writers can’t silently overwrite each other.

Key takeaways

• Every AgentMail inbox now has a calendar, in Labs since Oct. 8.
• Agents can send, accept and decline standard calendar invitations by email.
• Start and end webhooks arrive within about a minute after the scheduled moment, never early.
• Invitation emails count against send limits, one per recipient.
• Labs is US-only for now.

The take

We think the calendar fits the product. An agent that handles mail will soon be asked to schedule things. A calendar tied to the inbox keeps that work in one place. Invitations are mail, so they share the inbox’s address, logs and limits.

The send limits are the part to plan around. An invitation to five people costs five sends. Every change costs them again. A busy scheduling agent can burn through its quota. Check that count before turning the feature on. The ETag support deserves use as well. Two agents sharing one inbox can edit the same event. If-Match tells the second one it was too late.