Automations add registrants to a custom list when they match conditions you set, and remove them when they stop matching. Members you add by hand stay on the list. Members get the list's permissions and content access like any other member.
Before you start
You need to be an organization admin or an event admin.
Only custom lists have an Automations tab. Ticket type lists don't.
Automations change who is on the list. What members can do comes from the list's Permissions & access tab. See How permissions work when someone is on several lists.
Where to find it
People > Lists > Custom > open a list > Automations in the admin panel.
Set up the conditions
Select Add condition group.
In the group, select Add condition and choose a condition. The menu groups them under Sessions, Networking, Status, Sponsors and Custom fields. Hover the info icon next to a condition to read what it matches.
Fill in the condition's values. See the list of conditions.
To add another condition to the same group, select Add condition again. Next to Match, choose ALL (every condition in the group must match) or ANY (one match is enough).
To require more, select Add condition group again. A registrant must match every group.
Read the sentence under In plain language, then select Save automations. The message "Automations saved" confirms it.
Brella fills the list in the background right after you save. Open the Members tab to see the result; reload it if the count has not changed yet.
For example, build a list of joined attendees who requested or received an accepted or pending meeting:
In the first group, choose ANY. Add Accepted meetings at least
1and Pending meetings at least1.Add a second group with Registrant status set to Joined.
Read In plain language, then select Save automations.
A joined attendee with either kind of meeting matches. A joined attendee with no meetings does not. An invited attendee does not match, even with a meeting. Every group must match; ANY applies only inside the first group. These meeting counts cover the requester and receiver, not additional guests.
Every group needs at least one condition. Otherwise the save fails with "Conditions must contain at least one condition".
Drag groups and conditions to reorder them. The order does not change who matches.
Changing a condition's type resets its values.
Remove a condition or a group with its X. Save automations stays disabled until you change something.
Saving replaces the whole set of conditions. Saving with no groups removes every automatic member; manual members stay.
Conditions
Count conditions take an operator (at least, more than, exactly, at most, fewer than) and a whole number of 0 or more.
Sessions
Bookmarked session: the registrant bookmarked the session you choose.
RSVP'd to session: the registrant has a confirmed or attended registration for the session you choose. Requests waiting for approval, waitlist places and rejected requests don't count.
Sessions RSVP'd: count of sessions the registrant has a confirmed or attended registration for.
Session ratings given: count of session ratings the registrant gave.
Networking
Accepted meetings: count of the registrant's accepted meetings, as requester or receiver.
Pending meetings: count of the registrant's pending and rescheduled requests, as requester or receiver.
Rescheduled meetings: count of the registrant's rescheduled requests.
Rejected meetings: count of declined meeting requests the registrant sent or received.
Accepted hosted buyer meetings, Rescheduled hosted buyer meetings: the same counts, for meetings arranged by the organizer only.
Meeting ratings given: count of meeting ratings the registrant gave.
Pending chats: count of chat requests without a reply. Accepted chats: count of chat requests that got a reply.
Lead scans received: how many times a sponsor representative scanned the registrant.
Lead scans performed: how many leads the registrant scanned as a sponsor representative.
Times reported or blocked: how many times other registrants blocked or reported the registrant in this event.
Status
Registrant status: Joined or Invited. Default Joined.
Sponsors
Rep for sponsor: the registrant is a representative of the sponsor you choose.
Visited sponsor booth: the registrant opened the booth of the sponsor you choose in the app.
Custom fields
Custom field value: the registrant's answer to a registrant custom field. Choose the field, then the values. For a field with options, pick from Select values. For other fields, type each value and press Enter. With 2 or more values, choose Any of (one value is enough) or All of (every value must be in the answer).
When Brella runs the automations
Right after you save the Automations tab, and after you add or remove exclusions.
When something a condition depends on changes for one registrant:
the registrant is added or joins
their custom field answers change
a meeting or chat changes state or is deleted
they RSVP or cancel an RSVP, their RSVP is confirmed or turned away, or they bookmark or rate
they scan or get scanned
they are linked to or removed from a booth, or visit a booth
someone blocks or reports them
Every hour, for every custom list with automations in an event that has not ended. An event counts as ended one day after its end date.
When you duplicate an event, the copied custom lists keep their automations and Brella fills them at once. Exclusions are copied only when the registrants are copied too. If a condition names a session, sponsor or custom field that is not copied, the duplication fails.
Members you add by hand
Members added with Add members, by a CSV import (custom_list_ids) or through the Integration API are manual members. The tab shows the notice "Manual additions are protected": automations never remove them, even when they stop matching. Remove them yourself in the Members tab.
The Members tab does not show whether a member was added by hand or by an automation.
Exclusions
Exclusions at the top of the tab lists registrants the automations never add. The panel shows how many people are excluded.
Removing a member in the Members tab (Remove from list, then Remove and exclude) adds them to Exclusions. The dialog says they "won't be automatically re-added".
Add registrants to exclusions opens Exclude registrants. Pick people, select the Exclude button (it shows the number of people picked) and confirm with Exclude. Anyone you exclude who is on the list is removed from it.
Review all, shown once someone is excluded, opens Excluded registrants. Search by name or email, then select Remove exclusion on a row, or select several rows and Remove from exclusions. Confirm with Remove from exclusions. Brella runs the automations again right away, so people who match are added back.
Adding an excluded person with Add members, a CSV import or the Integration API removes their exclusion and makes them a manual member.
Limits
Automations exist on custom lists only.
Session conditions accept one session each (child sessions are not offered); sponsor conditions accept one sponsor each. Add a condition per session or sponsor and set the group to ANY to match any of them.
Removing a manual member through a CSV import (
custom_list_ids) or the Integration API does not exclude them. If they match the conditions, they become an automatic member again.The hourly run skips events that have ended. Changes to a registrant still trigger a run.
Troubleshooting
Someone matches the conditions but is not on the list
They are in Exclusions, or the automation has not run since they started matching. Open Review all and remove the exclusion. Otherwise, the hourly run adds them while the event has not ended.
Someone no longer matches but is still on the list
They were added by hand. Remove them in the Members tab.
"Some conditions couldn’t be saved"
A condition is incomplete or invalid, for example a count without a number, a session, sponsor or value not chosen, or an empty group. The alert lists each problem; the conditions themselves are not highlighted. Fix them and save again.