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.

Do first
Find the event and the people in it

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

  1. Read what’s there. Call agenda_items__getScheduleBundle so you don’t create duplicates.

  2. Places (optional). Look up existing locations in the schedule bundle. To add one, use locations__createLocation.

  3. Create each session with agenda_items__createAgendaItem. Required fields are eventId, name, startsAt and endsAt, as local times. Choose the sign-up style with rsvpMode:

    rsvpModeWhat guests seeUse it for
    requiredIt’s on their schedule; they can’t declineWelcome dinner, keynote, transfers. Pair it with isRequired: true
    rsvpConfirm or decline; seats countLimited-seat excursions. This is the only style where capacity, waitlists, the reservation window (reservationsOpenAt/reservationsCloseAt) and approval (preApproved: false) apply
    optionalA star to add it to their scheduleOpen sessions with no limit
    displayInformation onlyFree time, “Bus departs lobby”

    Call it with dryRun: true first. Cross-field rules are checked then; for example, capacity only works with rsvp.

  4. Edit with agenda_items__updateAgendaItem. Send only the fields that change, and pass null to clear a field. Moving a session into or out of a choice group is a special case: see Choice groups and activities.

  5. Publish each session with agenda_items__agendaItemPublish; this is the only way to make it visible.

    • agenda_items__agendaItemUnpublish moves a session back to draft. It refuses if guests have confirmed.
    • agenda_items__agendaItemCancel cancels a session and releases every RSVP. Dry-run it first and tell the organizer how many guests lose their place.
  6. 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 with agenda_items__tagAgendaItemTrack.

Check the dry-run for

  • Validation errors, such as a capacity on a non-rsvp session or an end time before the start.
  • For a cancel, the number of RSVPs that would be released.

Rules

  • Never set status through an update. Use publish, unpublish or cancel.
  • visibility (who can see a session) and accessMode (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.

Updated 2026-11-02 · View as Markdown