How to Export Guests From a Google Calendar or Outlook Invite to an Email List

To turn a calendar invite's guests into an email list, export them from the calendar, then sort by RSVP. In Google Calendar the organizer can choose Export guest responses to Sheets on a large event, and anyone can export a calendar as an .ics file that lists every guest of every event. In Outlook, Tracking > Copy Status to Clipboard (classic) or Tracking pane > Download as CSV (new Outlook for Windows) gives you each attendee with their response. Then drop the rooms, the organizer and the declines, merge people invited to several events, and check the addresses before the follow-up goes out.

The free calendar guests to email list tool does the sorting in your browser from an .ics, a guest responses CSV or a pasted list. The steps below cover where each file comes from and what to do with it.

Step 1: get the guests out of the calendar

Calendar	How	What you get
Google Calendar, large event, you are the organizer	Open the event > Export guest responses to Sheets	A sheet with each guest's reply, email and any note; download it as CSV
Google Calendar, any event	Settings > Import & export > Export (all calendars, as a .zip), or the calendar's Settings and sharing > Export calendar (one .ics)	Every event in that calendar, with an ATTENDEE line per guest
Classic Outlook (Microsoft 365, 2024, 2021)	Open the meeting > Tracking > Copy Status to Clipboard, paste into Excel	Name, address and response per attendee
New Outlook for Windows	Open the meeting > Tracking pane > More options > Download as CSV or Copy all tracking information	Name, address, required or optional, response
Apple Calendar	File > Export	An .ics file, read the same way as Google's

The sources: Google's collaboration tips describe exporting guest responses to Sheets for events of "200 people or more", where you can "see and download guest replies, email addresses, and any added notes". Google's export help covers the .ics route; it only works on a computer, needs "Make changes and manage sharing" permission on the calendar, and your Workspace admin may turn it off. Microsoft's attendee list article covers both Outlook versions; it doesn't cover Outlook on the web. All read 2 November 2026.

Use the organizer's copy. A guest's copy of an event often shows "no reply" for everyone else, and if the organizer hid the guest list, a guest's export won't have it at all.

Step 2: read the RSVPs

In an .ics file each guest is an ATTENDEE line, and the reply is its PARTSTAT parameter, defined in RFC 5545 section 3.2.12:

PARTSTAT	Calendar shows	Keep for a follow-up?
ACCEPTED	Yes	Yes
TENTATIVE	Maybe	Usually yes
NEEDS-ACTION	No reply / awaiting	Depends on the message: fine for "here's the recording", not for "thanks for coming"
DECLINED	No	Usually no

Two other kinds of line are not people:

• The organizer (ORGANIZER), which is usually you.
• Rooms and equipment, which are attendees with CUTYPE=ROOM or CUTYPE=RESOURCE. Google room calendars use addresses at resource.calendar.google.com. Mailing them does nothing useful.

A distribution list invited as one address (say sales-team@company.com) appears as that one address. Its members are not in the file.

Step 3: merge repeats across events

If you exported a whole calendar, the same guest appears once per event. Keep one row per address, with the count of events and the best response across them: accepted beats maybe, maybe beats no reply, no reply beats declined. That count is useful on its own. Someone who accepted five of six sessions in a series is a different follow-up from someone who was invited once and never answered.

The calendar guests tool does steps 2 and 3 for you: tick the responses to keep (accepted, maybe and no reply are ticked to start) and download the list with name, response and number of events.

Step 4: check the addresses

Calendar invites are a poor test of whether an address works. When an invite goes to a mailbox that no longer exists, nothing shows in the calendar. Any bounce lands in the organizer's inbox, among the auto-replies, and is easy to miss. Guest lists also collect typos from hand-typed invites and old addresses from recurring meetings set up years ago.

So check the list before the follow-up, especially if it goes out from a sending tool rather than as a reply in the same thread:

1. Run the file through the email list health check for syntax, typo domains and duplicates. It runs in your browser.
2. Upload it on the verify page for a mailbox check. Valid, risky and invalid come back as separate files.
3. Send the recording, slides or next invite to the valid file. Decide the risky rows by how well you know the person.

Limits to know about. Many company domains are catch-all, so a check can't confirm the mailbox and the row comes back risky. Microsoft's consumer domains (outlook.com, hotmail.com, live.com) can't currently be confirmed by our checker and also come back risky. Neither means the address is bad. Our catch-all post covers what to do with them.

Step 5: send the right message to the right group

Who said yes to a meeting agreed to the meeting. It is not an opt-in to your newsletter, and treating it as one is how event lists end up generating complaints. A safe pattern:

• Accepted and attended: the follow-up about the meeting, with a clear question if they want more.
• No reply or maybe: the recording or summary, phrased for someone who may not have come.
• Declined: nothing, or one note if the content is useful to them.

If the event was a trade show or a large webinar rather than a calendar meeting, our guide to cleaning an event attendee list covers badge scans and registration exports.

Where SimpleVerifier fits

The calendar export and sorting are free and stay in your browser. For the mailbox check, upload the list on the verify page; the first 100 checks are free with a Google sign-in. Pro is $39 a month with the first 100,000 checks a month at full speed, then slower, never cut off. See pricing.