onboard_events | A new workspace’s first session, in every window | Loads your upcoming and past events from what you already have (a CRM, a calendar, mail or an export), one collab per event, upcoming events first and past events once. Reads first, proposes, and writes only what you accept. See Your first session. |
record_roster | Before or after any event | Puts one event’s guests into heyBTW: creates or finds the collab from its link, records who registered from the guest list, marks only the people who attended, and checks the counts. See Record who came. |
next_event_standup | Any day, in every window | Where one event stands today, as five lines for the team channel: which event, days to go and window, RSVPs against the target with pace, what is open and who owns it, and after the event who is still untouched. Reads only and writes nothing. |
invite_sprint | The two weeks before an event (sprint and event_week windows) | Where the event stands against its RSVP target, who to ask and through whom, partner seat asks, and a Luma send last, sized to what is left. Reads first, proposes, and writes only what you accept. See Fill the room. |
debrief | The first days after (wind_down) | Walks the attendees with you, records who met them and what was said, and commits the follow-ups you accept, with owners from your own CRM. See The morning after. |
follow_through | From the third day after (wind_down) | Who has not been followed up, by owner, what was committed against what the CRM shows, and nudges you send through your own connectors. Changes no task. See Follow-up and ROI. |
format_attendee_list | Any time | Turns an attendee list that is not a table (an email thread, a badge dump, pasted names) into the CSV record_signups takes. Never use it on a file that is already a table. |