Task · Workflows
Send attendees to Blackbaud
Create or update a constituent in Raiser’s Edge NXT as tickets are bought and changed.
5 steps · About 6 minutes
This adds your attendees to Raiser’s Edge NXT as tickets are bought and changed, so they're in your fundraising database without an export. It matches on email address, so somebody who's already a constituent is updated instead of added again.
You'll need a Blackbaud login that can edit constituents, and somebody with the Marketplace admin role in your Blackbaud environment.
-
Add Tito to your Blackbaud environment
In Blackbaud, open the Marketplace and choose to connect an application. It asks for an application ID. Tito's is:
70b95b9d-c204-4c9f-97c5-98986ce6e887This is a one-off, and it's separate from signing in. Until it's done, the connect step below can't complete.
Only a Marketplace admin can do this. -
Connect Blackbaud
Open Connections in account settings. Select Connect, sign in, and allow access. Blackbaud sends you back here.
What the connection can do in Raiser’s Edge NXT is whatever the person who signed in can do, so sign in as somebody who can edit constituents.
If you have more than one Blackbaud environment, the one you sign in to is where every attendee goes.
-
Start from the template
Open Workflows, select Connections and choose Send attendees to Blackbaud.
Your accountWorkflowsgo.tito.io/acme/admin/workflowsThat creates an ordinary workflow you can edit, already set up to fire when a ticket is bought or changed. It arrives switched off.
-
Check what's being sent
Open the workflow and look at what it sends. It runs in two parts.
First it searches Raiser’s Edge NXT for the attendee's email address. Then it either creates a constituent with their first name, last name and email, or, if the search found somebody, updates that constituent's first and last name.
An update only writes the name. Everything else on a constituent record stays as you have it.
-
Turn it on
Switch the workflow on. It starts with the next ticket.
To bring across the tickets sold before you turned it on, see Catch up a workflow on tickets already sold.
Good to know
An attendee with no email address can't be sent, because there's nothing to search on. Those runs fail and say so.
Blackbaud limits how many calls a day Tito can make across every account it writes to, and each attendee takes two. If a busy on-sale reaches that limit, Tito waits and retries for a few hours. Contact Tito support beforehand if you're expecting to sell thousands of tickets in a day.
A new constituent is created as an individual. Tito doesn't create event participants.
A refunded or voided ticket leaves the constituent record as it is.
If a run fails, the run log has Blackbaud's own reply in it.