nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sharing my Power Automate Flow: Upcoming Opportunity Notification

Austen Brown

Summary
This flow sends a notification email monthly (on the 25th) with upcoming opportunities. The digest includes summary information about each upcoming opportunity as well as hyperlinks to the opportunity and constituent records.

Required Connections
Blackbaud Raiser's Edge NXT Constituents
Blackbaud Raiser's Edge NXT Prospects

Outlook

Suggested Skill Level
Beginner

Configuration Needs

Start in NXT by building an Opportunity list for the flow. My version of this list looks for Opportunities assigned to a specific fundraiser with an ask date next month.
While importing the flow into your environment, configure your connections to the RE NXT Constituents and Prospects new connectors, and Outlook.
Enter your Org's unique Environment ID into the "Initialize Environment ID Variable - String" action in the "value" field. If you are confused on where to find your Environment ID take a look at any URL from your Web View Environment it is the string of numbers and letters after "envid=" and before the "&svcid=renxt".
Select your previously created Opportunity List in the "List Opportunities from NXT" step.
Review the digest code in the "Apply to Each Opportunity Found" Loop > "Append to array variable 2"; add/remove elements to match your organization's preferences.
Edit the notification emails on both sides of the conditional - recipient email, message body, and "advanced options" reply to email.

Troubleshooting Tips

Format Number tends to ‘break’ frequently when editing this flow. If you get an error that involves this element - delete the listing and re-add it to the flow; then update the listing in the “Append to array variable 2” element.

Edits: updated the flow to include the new connectors and changed the hyperlink syntax for the digest table; updated the body of this post to match the changes. If you have any questions, post them here.

Edits 2026: removed extra loops that didn't do anything, and cleaned up confusing parts of the flow. Shared a new version of the flow

UpcomingOpportunityNotification-SharedtoBBCommunity_20260619143750.zip

Find more posts tagged with

Microsoft Power Platform

Showcase Template

Comments

Lindsey Rix

This is awesome, thanks so much for sharing!

Nate Laning

Austen, this is spectacular! Thank you for posting!

Austen Brown

I have updated the flow to include the update syntax for hyperlinks, alleviating this problem. Let me know if you have any questions.

Old Post: Some of the hyperlinks within this flow may not work as they are currently written. Check out this post for more information on how to update them within the imported flow:

Austen Brown

I have updated the shared template to include actions from the new connectors and fixed a few other troublesome spots. Let me know if you have any questions about the changes or the flow.

Hallie Guiseppe

@Austen Brown
Hi my friend! I have been using this flow for a while now to send our MGO's notifications of upcoming opportunities. My team loves it! I'm now trying to adapt this flow to accommodate a different but similar use case. My goal is to send a notification to all fundraisers assigned to the opportunity when it has been modified. I used the “addDays(utcNow(),-1)” expression in the modified on or after field of “List Opportunities” step in hopes it will only pull modified opportunities from the list into the flow. I'm not sure that will work yet, because I can't get past the issue of sending the email to the assigned fundraisers.

To get the fundraisers assigned I added the following steps to append the fundraiser email address to a string variable:

a144356189752268e8054f9ba6d3a809-huge-im — Get fundraiser email

After that I use the “fundraiseremail” variable in the email To: field and then set the variable to “null” after the email sends.

2aa744044f46770c8bc2b0d0c534df30-huge-im — Fundraiser Email

The result is that the flow is adding the fundraiser email address multiple times if they are on multiple opportunities and if there is a second fundraiser assigned it adds that in the mix too.

1b276a0b268177fdd5e6482c09cb167d-huge-im

I'm not sure how to tell the flow how to separate them out based on the opportunity. For example, if Hallie & Laurel on a single opportunity, they would get that notification, if Hallie is only on one of them (on the list) only Hallie will get that one.

I'm hoping you might know of another sample flow out there that has done a similar thing.

Thanks!

Michele Frick

@Austen Brown - Thank you for sharing this workflow! I'm trying to build a similar flow that sends an email with opportunities with funded status from the week prior. Is there a way to include the "Opportunity Assigned to" fundraiser info to the table in the email?

Austen Brown

Yep - You'll want the "Fundraiser(s) Constituent ID" from the output of a "Get an Opportunity" action. PA will put this into an apply to each. Use the "Get a Constituent" action to get the Fundraiser's name. Depending on how you want to list this in the email - I recommend using an Variable Array to collect the names. Then once out of the loop - use a join() expression to convert the array of names to a string/list of names.

Jessica Daggett

First day of BB Dev Days conference and feeling overwhelmed but am trying my first Automate flow and chose this one! At the step to choose the Opportunity List, it keeps failing and I can't see why. I am grabbing the part of the url I see when I "share this list" which comes after "Host.nxt.blackbaud.com/lists/shared-list/". Is that wrong?