An agent that gets invited to meetings should respond like a real attendee. Not with a polite "I'm an AI assistant, please contact my human" auto-reply. Not by silently dropping the invite on the floor. It should look at the meeting, look at its own calendar, and click Yes, No, or Maybe — the same three buttons every other person on the invite gets.
Most "AI calendar" demos run the other direction. They point a model at a human's Google Calendar and let it organize: propose times, send invites, chase RSVPs. That's the organizer flow, and it's useful. But the moment your agent has its own email address and people start inviting it to things, you need the mirror image. The agent is now an invitee, and invitees don't organize — they respond.
This post is about that response. An invite lands in the agent's mailbox, Nylas turns it into an event on the agent's calendar, your code decides yes/no/maybe based on whether the agent is actually free, and you fire a single send-rsvp call that updates the organizer's calendar the way any human's RSVP would. I work on the Nylas CLI, so the terminal commands below are the exact ones I reach for, and I'll pair every one with the raw HTTP call so you can wire it into a backend with no SDK.
