Power Automate to Update Prospect Status?

Jessica White

Trying to build an automation to update the prospect status for people daily based on a list. I'm not finding anything in Power Automate for prospects other than “get” the prospect status. Am I missing something and if not, anyone have any workarounds?

Alex Wong

@Jessica White
no, you are not missing something, the endpoint is missing. Here are a few ideas in the IdeaBank about this that you can vote on

https://blackbaud-developer.ideas.aha.io/ideas/API-I-306

https://blackbaud-developer.ideas.aha.io/ideas/API-I-220

https://blackbaud-developer.ideas.aha.io/ideas/API-I-456

A workaround would be for your power automate to generate an import file that has the constituent id, and propsect status to update. This is the header in the CSV to use.

ConsID

ProspectStat

then send the CSV as email attachment to yourselves to import in database view.

This is likely the most “automation” you can do follow by manual import in dbview

Shelby Lewis

@Jessica White Funny, I was just looking into this exact thing and voted on those idea banks before seeing your posts! Would love to be able to eliminate my regular manual import of this too. Hope we get some more endpoints soon.

Lucien Piekut

Hi @Jessica White, in my experience some automation workarounds end up being better than a field change if they fall in better with the process!

One approach to try is simulate a Moves Management or Workflow Designer step that triggers a Prospect Status change in system, but use the API to do that action instead.

Some in-system actions I recall shift the prospect status (e.g., assigning a fundraiser, adding/modify/add an opportunity, constituent field change, or changing a rating)

I would start by identifying which prospect status(es) your automation will modify.
Then:
• Test the front end entry that triggers the change. (who, what field, what dates get posted, etc.)
• Make a Power Automate workflow that steps through your user list and posts the appropriate "front end" change via the API. So you might hit a different endpoint for a status change.
• Optional but recommended: Verify via the RE NXT Prospect webhook the status change was made before going to next entry.

The route I would start with is if Workflow Designer can modify it, then simply post API change which can trigger the designer. I haven't tried it yet, but this seems like a promising path. If you're interested in walking through or want to bounce more ideas around, feel free to PM me.