Task · Workflows

Send attendees to Brella

Every ticket becomes a Brella registrant, stays current as details change, and is removed when the ticket is voided.

6 steps · About 7 minutes

We have an integration with the Brella event app. Attendees use it to find people to network with and follow the event agenda, while sponsors use it to scan leads. You can send attendees from Tito to Brella and keep them updated automatically.

You'll need a Core API token from Brella, plus the organization id and event id Brella uses for this event. Creating a token needs an organization admin account in Brella.

1. Create a Core API token in Brella

   In Brella, open API and choose Create token. Give it a name you'll recognize later, such as Tito.

   Leave Expires empty for a token that never expires, or set a date to limit how long a leaked token keeps working. The sync stops when a token expires, and runs again once you paste a new one into Tito.

   Brella shows the token once, so copy it before you close the box. Rotating a token later gives it a new value to paste into Tito.

   A new token has no scopes and can't read anything until you add them. Choose Add scope, and give it three:

   • Registrants, with read, create, update and delete.
   • Ticket types, with read.
   • Events, with read.

   Where Brella asks which fields a scope covers, the registrant scope needs to write external_id, external_email, external_first_name, external_last_name, external_company, external_title, pitch, persona, function, industry, ticket_type_list_id, custom_fields_attributes and send_email. It also reads external_id, external_email, external_first_name, external_last_name and status, and filters on external_id. That is how Tito finds a registrant it sent before, and tells a ticket that has gone to somebody else from an address you corrected. A token whose scope doesn't read the names treats every changed address as a ticket passed on.

   One token covers every event in the organization, so this happens once.

2. Paste the token on the account

   Open Connections in account settings. Paste the token into API key and select Connect.

3. Point the event at its Brella event

   Open the event, then Settings and Connections. Fill in the Brella organization id and event id, and choose whether Brella sends its own invitation email, which is how an attendee reaches the app.

   Save checks the token can see that event before it stores anything.

   go.tito.io/acme/summer-fetes-summer-fete/admin/settings/integrations

4. Set it up for the event

   Select Set up. It reads your event, reads Brella, and proposes the whole shape on one screen.

   Ticket types offers each of yours an existing Brella ticket type where the names match, and a new one where they don't.

   The section under it holds Brella's own fields: company, job title, pitch and three more. Each one is already pointed at whichever of your questions looks like the answer, so most of them need nothing from you.

   Your other questions is everything left over, offered as new Brella fields. Consents and personal details are set to Don’t send, and you can change any row either way.

   If the event has a portal, Portal is one of these rows. It sends each attendee the name of the portal their ticket came through, and nothing for anyone whose ticket came through none.

   Continue shows exactly what it will make in Brella before it makes anything. Nothing is created there until you confirm it on that screen.

   New ticket types are created in Brella as in-person.

   Brella needs to be told, and Tito has nothing to tell it from. Change it in Brella afterwards if the event is virtual or hybrid.

5. Check what gets sent

   Set up also makes the workflow, under The workflow that sends them. It covers this event and fires when a ticket is bought, changed or voided. Leave it switched on and attendees reach Brella within a few seconds of buying.

   To see what Brella receives, open Workflows and select the Brella workflow. What gets sent shows it filled in from one of your recent orders, and Empty fields underneath lists every row that comes out blank.

   Your accountWorkflows

6. Send the tickets you already sold

   Select Catch up on the workflow. Under Run for tickets already issued, pick the event, then continue and start it. A ticket already in Brella is matched on the id Tito sent with it and updated.

What Brella receives

Each ticket is one registrant in Brella. A field with no question pointed at it in Set up, or an empty answer, isn't sent.

Nothing comes back from Brella to Tito, but an attendee can edit their own profile in Brella. When a ticket changes, Tito sends the name, email address and ticket type every time. Everything else is sent only if it has changed in Tito since it was last sent, so an attendee’s own edit stays until the same detail changes in Tito.

Good to know

• Your token is encrypted before it's stored, and stays hidden from then on.
• A failed send is retried after a minute, then five, then thirty, then two hours. After that the run is marked failed, and its log holds what Brella said.
• When a ticket is passed on, Tito replaces the previous attendee in Brella with the new one, who gets Brella’s invitation if the event sends it.
• Correcting an address and keeping the name updates the attendee in Brella. If they hadn’t joined yet, they’re added again so Brella’s invitation reaches them.
• Moving a ticket to another type moves it in Brella too.
• Setting a ticket type back to Don’t send in Set up stops Tito sending those attendees. Anyone already in Brella stays there and stops being updated, so remove them in Brella if you meant them to go.
• Run Set up again whenever you add a ticket type. It asks only about the ones it hasn't been told about.
• A workflow made from the Brella template in Workflows covers no events until you tick them under Which events this covers. Set up ticks this event for you.