Record Attendance
Write the outcome — attended, no-show or canceled — onto this contact's event registration, with optional minutes attended, so later steps can tell who stayed long enough.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Record Attendance.
- Choose Attended, No show or Canceled.
- A new step comes with a
minutesvalue pre-filled. Clear it if what starts your workflow sends no minutes. - Leave the event dropdown as is — it records attendance for their most recent event that has already started.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- A new step comes with a
minutesvalue pre-filled. Any run that does not send minutes fails on this step unless you clear it.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Record Attendance under Add Steps.
Before you start
- An owner, admin or agent can add this step and save the workflow. Publishing that workflow — the thing that makes it run on live conversations — is an owner or admin action.
- Building and running workflows depends on your plan; see pricing.
- The contact must already be registered for the event — Register for Event first. This step only updates an existing registration; it never creates one.
Set up
- Open the workflow and click + where the record belongs.
- Pick Record Attendance.
- Choose Attended, No show or Canceled.
- A fresh step pre-fills the minutes field with a placeholder reading the webhook's own
minutesfield — clear it if this run has no such field, or it will fail every time; see Limits. - Leave the event dropdown on the most recent event they registered for, or name one.
- Save the step. To publish: set Status to Published in the toolbar at the top of the editor, click Save, then confirm with Publish. The dropdown on its own changes nothing until you save.
Fields
- Attended / No show / Canceled (dropdown)
- The outcome to record. The dropdown has no label on screen.
- Default: Attended
- Minutes attended (placeholder text, no label)
- How long they stayed.
- Default: A placeholder reading the webhook's own
minutesfield, on a freshly added step — not blank; see Set up. - Limits: If set (including the default), it must resolve to a real number or the whole step fails — see When it fails.
- The most recent event they registered for (dropdown)
- Which registration to update. The dropdown has no label on screen either, and lists only events that have not started yet — see Limits for what that means for naming a past one.
- Default: The most recent event they registered for
How it works
- The step resolves the contact behind this conversation and updates their existing registration for the named event — or, left unnamed, for whichever event they registered for that has most recently started. It never registers anyone; that is Register for Event's job.
- Without a named event, the pick is deliberately the session that has already happened, most recently — not the nearest event either way — so a report about last night cannot land on next week's registration.
- A NAMED event skips that check entirely: it is not required to have started, so the guard against grading a session that has not happened yet only applies when the event is left unnamed.
- If Minutes attended is set, it must resolve to a real, non-negative number or the step fails without saving anything.
- Saving a status with no minutes would quietly send every attendee down whichever branch does not check minutes, so the step refuses instead of guessing.
- The status and the minutes are independent: a run can save the status with minutes left blank, and a later run with the same status can add minutes to that same registration.
- Each field only writes when it actually changed.
- Recording the same status and the same minutes a second time — a replayed webhook, or two reports saying the same thing — changes nothing, starts nothing and shows no error.
- A real status change fires this workspace's Event Registration Changed trigger for other workflows, using this run's own conversation — not necessarily the one the registration was first made from.
- A minutes-only correction, with the status unchanged, does not fire that trigger — it is not treated as a state transition, so a flow chained off the status change does not re-run for a correction.
When it fails
- This conversation has no linked contact: the step fails with this conversation has no contact whose attendance to record.
- Minutes attended was set but does not resolve to a number — for example an empty value or a negative number.
- The step fails with minutes attended did not resolve to a number (got “<text>”), and nothing is saved. This is also what happens if the default placeholder is left in place on a run that sends no
minutesfield. - The contact has no registration for the named event: the step fails with this contact is not registered for that event.
- The contact has no registration for any event at all: the step fails with this contact is not registered for any event.
- Left unnamed, none of the contact's registrations are for an event that has started yet: the step fails with no event this contact registered for has started yet.
- A database error reading or saving the registration fails the step with a specific reason (could not read this contact's registrations or could not save the attendance).
- A failed record does not stop the run: the step shows as failed in the run's Activity tab and the flow moves straight to the next one.
Limits
- It cannot register a contact — only update a registration Register for Event already created.
- Left unnamed, it only ever considers events that have already started, and picks the most recently started one — a contact with two past sessions on file gets only the newer one graded by this step.
- The event dropdown lists only events that have not started yet — the same list Register for Event offers. A past event cannot be picked; to grade one, leave the dropdown on The most recent event they registered for.
- A fresh step defaults Minutes attended to a placeholder reading the webhook's own
minutesfield. - That fails the step on any run whose trigger does not populate it — clear the field if the status alone is what this run should record.
- It does not repeat a status transition's trigger for a minutes-only correction — a flow reacting to attendance will not see a second run just because the minutes were adjusted afterwards.
Use cases
- A webinar platform posts each attendee's report to a workflow triggered by Incoming Webhook; this step records Attended, and the default placeholder reads the
minutesfield from that report. - Mark Canceled when a contact replies that they can no longer make it — clear Minutes attended first, since the default placeholder has nothing to resolve from a chat reply and would fail the step otherwise.
Reading this with an AI assistant? Plain Markdown version.