Register for Event
Add this contact to an event's list, so they become eligible for its reminders — a named event, or the next published one coming up.
Quick start
- Go to Automate → Workflows and open a workflow. Click + and pick Register for Event.
- Create the event first under Events, then leave the dropdown on The next published event for a session that repeats.
- Or pick one specific event from the same dropdown.
- Set Status to Published in the top toolbar, Save, confirm Publish. Agents: ask an owner or admin.
Watch out
- Upcoming drafts are listed too, marked “(draft)”; picking one registers into it, with no reminders until published. Only “The next published event” skips drafts.



Details
Getting here
Automate → Workflows, open a workflow, click + on the canvas, then pick Register for Event 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.
- Create the event first under Events. A new event starts as a draft; publish it there for its reminders to go out. The step still saves with no event, but has nothing to register into until one exists.
Set up
- Open the workflow and click + where the registration belongs.
- Pick Register for Event.
- Leave the dropdown on The next published event for a session that repeats — the flow then never needs editing between sessions — or pick a specific 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
- The next published event (dropdown)
- Which event to register the contact for. The dropdown has no label on screen.
- Default: The next published event
- Limits: “The next published event” only ever considers events that are published and have not started yet. The dropdown also lists upcoming drafts, marked “(draft)”, and a picked event is registered into whatever its status.
How it works
- The step resolves the contact behind this conversation and adds them to the named event's registration list, which is what makes them eligible for that event's reminders.
- Left on the next published event, it picks the soonest published event that has not started yet — a session already underway is never enrolled into.
- A contact can only be registered once per event: registering someone already on the list, with the registration already registered, changes nothing but the conversation link below and shows no error.
- A canceled registration is turned back to registered. Attended and no-show are never changed, so re-running this step cannot undo a measured fact.
- A registered or canceled registration with no conversation attached gets this run's conversation added to it. An attended or no-show one is left exactly as it is, conversation included, and the step still counts as done.
When it fails
- This conversation has no linked contact: the step fails with this conversation has no contact to register.
- A named event id does not exist in this workspace: the step fails with that event no longer exists in this workspace.
- Left on the default with nothing coming up: the step fails with no published event is coming up to register into.
- Saving the registration can fail with could not save the registration, or, rarely, the registration disappeared while saving.
- It can also fail with the registration kept changing while saving: three times in a row, another run or a person changed the registration between this step reading it and saving it.
- When the contact is already on the list, re-checking their registration can fail with could not read the registration, and putting it back or adding the conversation can fail with could not update the registration.
- Reading this run's conversation can also fail. That one reports no specific reason, so the run's Activity tab shows the fixed line failed without a reported reason instead.
- A failed registration 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 only ever adds a contact to the list — it cannot cancel a registration or record what happened at the event; that is Record Attendance.
- “The next published event” never picks a draft — a session still being built is skipped until it is published.
- It cannot register anyone without a linked contact on this conversation.
- Registering the same contact twice is not an error, but it is also not a second registration — there is exactly one row per contact per event.
Use cases
- A weekly webinar flow left on the next published event, so the same workflow keeps registering people into whichever session is coming up without being edited.
- Register a contact for a specific product launch event named in the step, right after they answer yes to an Ask a Question step asking if they want a reminder.
Reading this with an AI assistant? Plain Markdown version.