> For the complete documentation index, see [llms.txt](https://docs.vomevolunteer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vomevolunteer.com/integrations-and-automations/blackbaud.md).

# Blackbaud

{% hint style="info" %}
**Need help?** If you run into any issues connecting Blackbaud, or if you'd like to request any additional functionality, contact us at [support.vomevolunteer.com](https://support.vomevolunteer.com/).
{% endhint %}

***

## Blackbaud Integration Setup

The Blackbaud integration keeps your Blackbaud constituents and your Vome profiles in step with each other over the SKY API. It is a two way sync that you build yourself: you decide which fields travel, which direction each one travels in, which system wins when both sides changed, and which people cross over at all.

**What you'll do in this guide**

1. **Connect** your Blackbaud environment over OAuth, choosing which Blackbaud product you use
2. **Configure** which fields may sync and in which direction, then write workflows if you want conditions
3. **Validate** by previewing a sync, switching on event delivery, and reading the Activity tab

***

### 1. Pre-Installation Checklist

Before starting, confirm you have all of the following.

#### Plan and access

* A Vome subscription on the **Ultimate** plan
* An administrator account in Vome
* A Blackbaud login with permission to see and edit the records you want to sync. Vome can only do what the person who connects it can do.

#### The step people miss

* An administrator in your Blackbaud organization must have **activated Vome in the Applications area** of your Blackbaud product. Consent alone is not enough, and this is the most common reason a first connection attempt fails.

#### Which product

Vome connects to three Blackbaud products. You choose which one before consent, and it cannot be changed later without reconnecting, because the three use different APIs.

| Product           | Supported                                                    |
| ----------------- | ------------------------------------------------------------ |
| Raiser's Edge NXT | Full sync, plus the Vome panel inside the constituent record |
| Blackbaud CRM     | Full sync                                                    |
| Blackbaud Altru   | Full sync                                                    |

***

### 2. Connect the Environment

{% stepper %}
{% step %}
**Open the integration**

In Vome, go to **Integrations & Apps** in the left hand navigation and open **Blackbaud**.
{% endstep %}

{% step %}
**Choose the product**

On the **Connection** tab, pick which Blackbaud product you are connecting: Raiser's Edge NXT, Blackbaud CRM or Altru.
{% endstep %}

{% step %}
**Authorize**

Click **Connect to Blackbaud**. You are taken to Blackbaud to sign in. Approve the connection and choose the environment you want to link if you are asked.
{% endstep %}

{% step %}
**Confirm**

You are returned to Vome and the environment appears under **Connection**. Click **Test connection**, which makes one real SKY API call and reports what came back.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Vome uses a single SKY application shared by all customers, so there are no client credentials for you to create or store. Your organization is bound to a Blackbaud environment because one person was simultaneously signed in to both when they consented.
{% endhint %}

***

### 3. Decide What May Sync

Nothing syncs until you switch a field on. Connecting establishes trust between the two systems and moves no records at all.

On the **Fields** tab, open a field, choose its direction, and switch it on.

| Field group                                                     | Directions available                               |
| --------------------------------------------------------------- | -------------------------------------------------- |
| Name, email, phone, mailing address, date of birth, gender      | Vome to Blackbaud, Blackbaud to Vome, or both ways |
| Archived becomes inactive                                       | Vome to Blackbaud only                             |
| Hours volunteered, shifts completed, first and last volunteered | Vome to Blackbaud only                             |

A direction is a rule rather than a preference. A field set to **Vome to Blackbaud** is invisible to anything running the other way: it is skipped, never reversed.

When a field syncs both ways you also choose which system wins if both sides changed since the last sync: **Vome wins**, **Blackbaud wins**, or **Most recently changed wins**.

***

### 4. Hours, Totals and Custom Fields

Raiser's Edge NXT does not accept volunteer timesheets through its API, so Vome writes your volunteering totals to a field on the constituent instead, where they are visible, reportable and queryable.

Create the field in Blackbaud first, then name it in Vome when you switch the mapping on.

**The one place the three products differ**

|                                    | Raiser's Edge NXT       | Blackbaud CRM and Altru  |
| ---------------------------------- | ----------------------- | ------------------------ |
| Called                             | Custom fields           | Constituent attributes   |
| Vome can list the ones you created | Yes, pick from a list   | No, type the name        |
| You declare the type               | No, read from Blackbaud | Yes, choose when pairing |

On Blackbaud CRM and Altru, type the attribute category name exactly as it appears in Blackbaud and tell Vome what kind of value it holds. Those products publish no list of the attributes an organization has defined, so there is nothing for Vome to read.

{% hint style="warning" %}
A mapping that writes to a custom field will not switch on until you have named the field. Vome refuses to enable a rule that would write into nothing.
{% endhint %}

***

### 5. Workflows: when, if, then

The **Workflows** tab decides when the fields you switched on actually move, and for whom. Write none and every switched-on field syncs whenever a profile changes, which is a perfectly good setup.

A workflow is one rule, written as a sentence.

**When** starts the rule and decides which system it writes into:

| Trigger                                                   | Writes into                           |
| --------------------------------------------------------- | ------------------------------------- |
| A profile is added, or added or updated, in Vome          | Blackbaud                             |
| A constituent is added, or added or updated, in Blackbaud | Vome                                  |
| Every hour, day, week or month                            | Blackbaud, over people already linked |

**If** is optional. Conditions test a field on the side the rule starts from, so a rule starting in Blackbaud can test a Blackbaud custom field. That is how "only the constituents our fundraisers marked as volunteers" is written.

**Then** is what it does:

* **Create them in Blackbaud** or **Create their profile in Vome.** A profile created from Blackbaud is offline and is not invited to anything.
* **Sync the mapped fields.** One action, however many fields are switched on.
* **Set a value in Vome** or **Set a value in Blackbaud.** Writes a fixed value you type into any field on that side, with the right control for the field.

{% hint style="warning" %}
**A workflow takes over.** While no workflow listens for a kind of change, every switched-on field syncs whenever that change happens. As soon as one listens, that workflow decides instead, and a workflow whose conditions do not match writes nothing. To keep the plain sync, add **Sync the mapped fields** as an action on the workflow.
{% endhint %}

***

### 6. Let Blackbaud Send Us Changes

A workflow that starts from a Blackbaud change does nothing until Blackbaud has been asked to tell Vome about changes.

1. Open the **Activity** tab.
2. Switch on **Let Blackbaud send us changes**.

Vome subscribes to the events it acts on: a constituent added or changed, a constituent custom field added or changed, and email address, phone and address changes. The custom field events matter most, because a constituent custom field edit does not raise the plain constituent change event, and that is usually where the "this person is a volunteer" marker lives.

{% hint style="info" %}
A subscription is created per event type. If Blackbaud declines one of them, the others are still created and the banner says which was refused and why.
{% endhint %}

***

### 7. How People Are Matched

The two systems find the same person by email address, in both directions, and they do it carefully.

**Going out to Blackbaud:** an existing link is used first, otherwise Vome searches Blackbaud for that exact address. Exactly one living, active constituent links. Several constituents sharing the address is reported as **Needs a decision** and links nobody, because guessing would write a volunteer's details onto the wrong donor. Deceased constituents are never matched.

**Coming back from Blackbaud:** Vome looks for a profile holding that address, checking both the sign-in address and the alternative one. Nobody matching means the constituent is skipped, unless a workflow says **Create their profile in Vome**. Two profiles sharing the address writes nothing and reports the clash.

***

### 8. Preview Before You Run

On the **Activity** tab, **Preview changes** reads both systems and shows exactly which people would be created, matched or skipped, without writing anything to Blackbaud. The live run stays disabled until you have previewed at least once.

Previewing costs far fewer API calls than writing, and the daily Blackbaud allowance is small, so always preview first.

***

### 9. The Vome Panel Inside Blackbaud

On **Raiser's Edge NXT**, the integration adds a Vome panel to the constituent record so your fundraising team sees volunteering without opening Vome. It shows hours volunteered, shifts completed, last and next shift, and the programs the person volunteers with.

It is read only and shows activity only. Notes, medical information, emergency contacts and custom fields stay in Vome, because the person reading the panel is a Blackbaud user and Vome's own permissions do not apply to them.

Blackbaud CRM and Altru get the full sync, including hours written to a constituent attribute, but not the panel.

***

### Troubleshooting

Open the **Activity** tab and read **Is this working?** at the top. It walks every step between the two systems in order and names the one that is stopping, with the fix beside it. Start there rather than guessing.

> **Nothing syncs at all?**
>
> Check that at least one field is switched on under **Fields**. Connecting is not the same as syncing, and this is the most common cause by far.

> **A workflow that starts in Blackbaud never runs?**
>
> Switch on **Let Blackbaud send us changes** on the Activity tab. Until then there is no event to start it. **Pull from Blackbaud** on the same tab runs your inbound workflows by hand without waiting for an event, and only ever reads from Blackbaud.

> **A workflow matched somebody and wrote nothing?**
>
> The field that changed is probably not switched on in that direction. The Activity tab names the fields that were eligible.

> **Nobody is matching?**
>
> More than one record shares that email address, or the person exists in one system only and no workflow asks for them to be created.

> **A constituent is not being created?**
>
> Blackbaud will not create a constituent without a last name. Check the Vome profile has one.

> **The connection says Reconnect needed?**
>
> Someone in Blackbaud may have deactivated the application, or the connection has aged out. Click **Reconnect**.

If you need help or have additional questions, reach out to us at [support.vomevolunteer.com](https://support.vomevolunteer.com/).
