Integrations: Email Activity Notifications

Receive email notifications from your event activity as it occurs — registrations created, updated and cancelled, and invitations created, sent and updated!

Overview

When something happens in your event, getregistered will send email notifications to the email addresses you have configured:

A registration is created, updated or cancelled.
An invitation is created, sent or updated.

You choose which of those six triggers a channel receives. A single event can have several email notification integrations pointing at different email addresses with different triggers.

Prerequisites

The organisation-level Email Notifications feature flag must be on. It is off by default and is set by getregistered support on the organisation record — ask your account contact to enable Email Activity Notifications Integration for your organisation. Until it is on, you will be unable to use this feature.

Adding email addresses to receive notifications in getregistered

Navigate to your event in getregistered admin.
Go to Integrations > Email Notifications
Select New Email Integration.
Fill in:
1. Recipient Email Addresses: The email addresses to receive notifications on event activity. Multiple addresses can be added, separated by a comma after each address. At least one email address is required!
2. Notification Triggers: Which activity this channel receives (Registration Created, Invitation Sent etc).
Select Save Email Integration.

Notification Triggers

Registration Created | Someone registers for the event
Registration Updated | A registration changes (including a name or email edit)
Registration Cancelled | A registration is cancelled
Invitation Created | An invitation is created
Invitation Sent | An invitation is sent or resent
Invitation Updated | An invitation changes other than being sent

At least one trigger is required.

Volume controls

Email notifications get the same protections as Slack and Teams, so a busy event does not flood the channel:

Bulk operations post one summary: A bulk confirm of 100 registrations posts a single "100 registrations confirmed" card, not 100 emails.
Organic bursts are digested: If many registrations arrive at once outside a bulk operation — an import, or a rush when registration opens — the first few will notify individually and the rest collapse into one summary once the burst settles.
Matching track/admission type configurations: Activity can be limited to specific track or admission types to reduce noise in your inbox.