Best Of

I also contacted support about this recently. I don't understand dropping existing reports or features and asking us to submit ideas.

@Alex Wong
In that case, how does one update multiple participants to constituents?

Here's a little diagram I created with our integration config and different options that is available.

This is the only field in RE where we track how our constituents come to us, as well as when there is an address update. Important field for the Society.

We use Constituent codes for this - it would either be Student (which we update to Alumni when they graduate), Friend of … (if they 'joined' as a donor first but didn't study here) and Family /Events Program - through attending events etc

One of my clients had the same issue and our IT team resolved it.

I agree these are needed fields. I'm asked to pull alum that work in a specific industry. Have one such request on my desk right now.

Like @Joe Moretti and others, I don't understand why some data points were carried over and others have not been and need to be added now. Going back and forth between web view and db view is frustrating. And leaves those who only work in NXT in the dark as they do not have the info.

We recently implemented an automated contact-to-constituent pipeline for a youth organization using Gravity Forms on WordPress → Microsoft Power Automate → Blackbaud RE NXT REST API, and wanted to share the approach.

The challenge:
Our client captures contact inquiries and membership interest through Gravity Forms on their WordPress site. Every new submission was being manually entered into RE NXT a time-consuming process prone to errors.

The solution — automated POST to RE NXT via Power Automate:

Step 1 — Trigger (Gravity Forms Webhook)
Configured Gravity Forms' built-in Webhook Add-on to fire a JSON payload to a Power Automate HTTP trigger URL on every new form submission.

Step 2 — Power Automate Flow (HTTP → Parse JSON → Compose)
The flow receives the webhook, parses the form fields (first name, last name, email, phone, address), and maps them to the RE NXT constituent schema.

Step 3 — POST to RE NXT Constituents API
Using the HTTP connector in Power Automate, we POST to:https://api.sky.blackbaud.com/constituent/v1/constituents


Headers include the Blackbaud SKY API Bb-Api-Subscription-Key and OAuth 2.0 Bearer token (refreshed automatically via a separate flow).

Step 4 — POST Phone & Address as linked records
After constituent creation, we extract the returned id and fire two additional POSTs:
• /constituent/v1/phones — adds phone linked to constituent ID
• /constituent/v1/addresses — adds mailing address

Step 5 — Duplicate check before POST
Before creating, we call GET /constituent/v1/constituents/search?email=... to check for existing records and skip or update rather than duplicate.

Step 6 — Error handling & notifications

Power Automate's Configure run after handles failures — a Teams/email notification fires if any POST returns a non-200 status, including the error response body for quick diagnosis.

Key RE NXT API payload (constituent POST):{
"type": "Individual",
"first": "Jane",
"last": "Doe",
"email": {
"address": "jane.doe@example.com",
"type": "Email",
"primary": true
}
}


Results for our client:
🏆 Zero manual data entry for contact form submissions
🏆 New constituents appear in RE NXT within seconds of form submission
🏆 Duplicate prevention keeps the database clean
🏆 Full audit trail via Power Automate run history