RSVP

Put this in a Google Calendar event's description:

#already:rsvp

The event's card and its detail page get an RSVP button, in every card layout. A visitor enters a name, an email and a party size; you get an email for every RSVP with the attendee's address as Reply-To, so answering them is a reply. Turn it on for every event instead with the view editor's "Collect RSVPs on every event" switch.

What a visitor sees

The button opens a short form in place: name, email, how many are coming. On success it reads "You're on the list: 2 going". Submitting again with the same email updates that RSVP instead of adding one. The button disappears once the event has started. If the event stops taking RSVPs while the page is open, the form says so instead of asking the visitor to try again. A party can be 1 to 20 people, and a name can be up to 80 characters.

Where the RSVPs are

Each one arrives by email at your account address, up to the limits below. RSVPs are also listed in the dashboard (the most recent 2,000): open the view and click RSVPs. You can remove an RSVP there.

Details

• Recurring events take RSVPs per occurrence: each Friday has its own list.
• Cards appear in the grid and list views. In the month, week and day views, visitors RSVP from the event's detail page.
• An all-day event takes RSVPs until its day begins in its calendar's time zone; a timed event takes them until it starts. An iCal feed carries no calendar time zone, so its all-day events use the view's time zone, or UTC when the view has no Google calendar.
• #already:rsvp:https://… (the flag followed by a link) is a URL-valued tag: it renders a link button to an outside form and collects nothing here.
• #already:hidden events never take RSVPs.
• The flag and the switch do not apply to the preview pages or to the demo calendar.
• Each embedded view sends at most 15 RSVP emails an hour, and the service sends at most 40 a day across every calendar, so heavy traffic elsewhere can stop yours until midnight UTC. RSVPs past those limits are still stored but not emailed; they are in the view's RSVP list in the dashboard, within its most recent 2,000.
• Not yet: a confirmation email to the attendee, cancellation links, capacity limits.