Sharing my Power Automate Flow(s): Get Query Results as JSON

Ashley Moose
Ashley Moose Blackbaud Employee
Eighth Anniversary Kudos 5 First Reply Name Dropper

While we already have the templates to get query results in a .CSV file, we can now get query results as JSON thanks to the updated Query connectors. After running this flow you can then use the JSON output for further manipulating and processing directly within Power Automate.

Attached you will find 4 different templates: 2 for RENXT, and 2 for FENXT. The ones noted with (gmail) include the gmail connector instead of the Outlook connector for email notifications.

Steps to update:

  1. Update Initialize variable emailToNotify with the email address that should be used to notify of flow/query failures.
  2. Update Start a query job to include the query you need to run.
  3. Update the schema in Parse JSON query results.
    • To update the schema you'll need to run the flow once.
    • Click into the run history of that run and copy the output from Compose JSON results.
    • Go back to Edit the Flow and on the Parse JSON action, click Use sample payload to generate schema.
    • Then paste in the output copied above. Click Done.

Note: On 2/10/2026 something changed that causes another configuration step to be needed. See notes below from Austen Brown on 2/10 and 8:56 AM. I'll work on getting the .zip files updated, but until then, please follow Austen's notes!

GetRENXTqueryresultsasJSON_20250311145820.zip

GetRENXTqueryresultsasJSON(withgmail)_20250311145559.zip

GetFENXTqueryresultsasJSON_20250311145354.zip

GetFENXTqueryresultsasJSON(gmail)_20250311145314.zip

Comments

  • @Ashley Moose Thank you so much for this! I got this to work for me to have fundraiser notification emails be sent automatically when one of their assigned donors gives a gift (with link to donor record included). This will help them thank their donors much quicker.

  • Elizabeth Johnson
    Elizabeth Johnson Community All-Star
    Tenth Anniversary Kudos 5 First Reply All-Star Challenge: End of Year Fundraising Toolkit

    @Ashley Moose, thanks for the Gmail versions!

  • Austen Brown
    Austen Brown Community All-Star
    Tenth Anniversary Kudos 5 PowerUp Challenge: Product Update Briefing Feedback Task 3 bbcon 2025 Attendee Badge

    Adding in, as of this morning running the Body output from the HTTP action following the query call is causing errors.

    image.png

    To resolve the error, you need to remove the json() expression within the Parse JSON action to be only the dynamic output from the HTTP action above.

    With the change, the flow runs as expected.

    image.png



    Ashley (can't tag you for some reason), you may want to update your templates to remove the json() expression from this step.

  • Ashley Moose
    Ashley Moose Blackbaud Employee
    Eighth Anniversary Kudos 5 First Reply Name Dropper

    Thanks @Austen Brown. I just uncovered the same thing while working in one of my flows and was like "hmm" didn't I just see this in my Community email?? Not sure what changed. I'll aim to get the templates updated one of these days. Until then, noting above :)

Categories