To-dos, forms and due dates

Ask guests to do something (a form, a passport upload, a waiver) before a due date, see who has finished it, and fill it in for them.

Do first
Find the event and the people in it

A to-do is a task guests see in their app. It has 1 to 10 ordered steps: a form step (questions) or a check step (“Mark as done”). A plain to-do is one check step.

Steps

  1. Read what exists with todos__getFormsBundle: the event’s to-dos, their steps, and the guest groups you can target.
  2. Start from a template if one fits. templates__listTodoTemplates returns ready-made steps, including the official dietary, accessibility and emergency-contact forms, that you can pass straight to steps.
  3. Create the to-do with todos__createTodo. Dry-run first: it returns the to-do as it would be saved.
    • audience is who it’s for: the whole event, one choice group, one session (agendaItemId), a guest group, a ticket type, or named guests (guestIds).
    • dueAt is the due date, as a local time.
    • steps holds {kind:"form", config:{fields:[…]}} or {kind:"check"}.
  4. Edit with todos__updateTodo. You can change the title, body, status and the full ordered step list (existing steps by id, new ones without), but not the audience. Removing a step deletes its answers; the dry-run shows how many.
  5. See who has finished with todos__listTodoResponses, or look at one guest with todos__listGuestForms.
  6. Fill it in for a guest, when they sent the answers another way: todos__setGuestTodoResponse. Dry-run first.
  7. Delete with todos__deleteTodo. This also deletes its answers; the dry-run gives the counts.

Chase the guests who haven’t finished with todo_incomplete in Message people who…, or automatically before the due date with Reminders (scopeKind: "todo").

Updated 2026-11-02 · View as Markdown