Build and publish the schedule
Add sessions to an event, choose how guests sign up for each one, and publish them so guests can see them.
A schedule is a list of sessions (agenda items). Each session has a time, an optional place, and a sign-up style. Sessions start as drafts that guests can’t see, and you publish them when they’re ready.
Steps
-
Read what’s there. Call
agenda_items__getScheduleBundleso you don’t create duplicates. -
Places (optional). Look up existing locations in the schedule bundle. To add one, use
locations__createLocation. -
Create each session with
agenda_items__createAgendaItem. Required fields areeventId,name,startsAtandendsAt, as local times. Choose the sign-up style withrsvpMode:rsvpModeWhat guests see Use it for requiredIt’s on their schedule; they can’t decline Welcome dinner, keynote, transfers. Pair it with isRequired: truersvpConfirm or decline; seats count Limited-seat excursions. This is the only style where capacity, waitlists, the reservation window (reservationsOpenAt/reservationsCloseAt) and approval (preApproved: false) applyoptionalA star to add it to their schedule Open sessions with no limit displayInformation only Free time, “Bus departs lobby” Call it with
dryRun: truefirst. Cross-field rules are checked then; for example,capacityonly works withrsvp. -
Edit with
agenda_items__updateAgendaItem. Send only the fields that change, and passnullto clear a field. Moving a session into or out of a choice group is a special case: see Choice groups and activities. -
Publish each session with
agenda_items__agendaItemPublish; this is the only way to make it visible.agenda_items__agendaItemUnpublishmoves a session back to draft. It refuses if guests have confirmed.agenda_items__agendaItemCancelcancels a session and releases every RSVP. Dry-run it first and tell the organizer how many guests lose their place.
-
Tracks (optional). Tracks are colour tags guests can filter by. They are not a way to make guests choose. Create one with
agenda_items__createTrack, then tag sessions withagenda_items__tagAgendaItemTrack.
Check the dry-run for
- Validation errors, such as a capacity on a non-
rsvpsession or an end time before the start. - For a cancel, the number of RSVPs that would be released.
Rules
- Never set
statusthrough an update. Use publish, unpublish or cancel. visibility(who can see a session) andaccessMode(who may sign up) are different settings. See Private sessions and invite lists.- Draft sessions are hidden from guests, but RSVPs that already exist still count.