Automation to add a Constituent Code

Sarah Woodard

Hi, I set up an automation to add a constituent code (Major Donor) to records if certain criteria are met. It also sends an email to the relevant people who can review it.

In some cases, they decide to remove this code from the record (the criteria is correct but in this particular case, we don't want the code). Is there a way to prevent the flow from adding it again?

Dan Snyder

@Sarah Woodard How are you identifying the donors to start? List, Query, something else? Also will those excluded be excluded forever (ie. beyond the end of the year/fiscal year)? Have you thought about moving the approval process to before the addition of the code?

Just a couple questions that could help to inform some thoughts for you as I am sure there is a way to do this.

Alex Wong

There will need to be logic that can identify who to exclude. That can be in the form of a constituent attribute or constituent note.

I would use constituent note (create a new notepad type, such as Major Donor Exclusion), that way the reasoning can be recorded as well in case in the future other fundraiser question why the record shouldn't be included.

In your automation, you can use the Note list (single constituent) API endpoint and filter on if there exists a note type = the type you created, if yes, ignore.

If you want to get fancy and remove more manually workload, you can do one of these 2 things:

1. create another automation that display an adaptive card for the fundraiser to provide a reason why the record needs to be excluded, this adaptive card can then add the notepad with all the correct data and remove the constituent code.
2. create another automation that runs "regularly" (daily or every few hours), that checks for constituent with Major Donor constituent code and the Major Donor Exclusion consituent notepad to automatically remove it.