Looking for 'Validate a user identity token' action

Options

Greetings,

I've been looking at the Invoke a flow tutorial to see if it would be a good option for a feature I'd like to add.

The tutorial mentions validating the user using the ‘Validate a user identity token’ action in Power Automate. But when I create my flow, I do not see that in my list of actions.

Do others have access to this action? What endpoint is it using in SKY API?

Thanks.

Comments

  • Hi Ben,

    The “Validate a user identity token” action is available in the Blackbaud Church Management connector, but it's currently mid-flight in the release pipeline for the RENXT connector. Unfortunately, we've hit some deployment issues on the Microsoft side. Essentially the RENXT connector has reached a practical size limit and their pipeline is timing out trying to deploy it. So they are recommending that we build new connectors going forward (the current connector is fine to keep using and won't change/break when we introduce new connectors).

    What that means is…right now, that action isn't in the RENXT connector. But it is in the Church Management Connector, so technically you can use that (because it doesn't make any API calls or expect an actual Church Management database under the hood). It's admittedly not ideal, and understandably a little confusing but it does work for now while we work through factoring the connector so we can include more functionality going forward.

    [and fwiw - the approach we're likely to take is to leave the RENXT connector as-is, which is usable and stable and produce a handful of new connectors scoped to domain functionality within RENXT, like Event Management, Constituent Management, etc. Would love your feedback on that approach if you have thoughts!]

    So when you select that action in the Church connector, you'll just need to create a connection to the same “environment” that your RENXT connector is using. Does that make sense?

    Let me know if you have any questions! Also happy to talk through the Invoke a flow scenario you're envisioning, just let me know!

  • Thanks for the info, @Ben Lambert. That's too bad about the size limit - maybe Microsoft didn't expect anyone to make such thorough connectors! Splitting it into several connectors sounds like the best workaround available, especially if the new connectors are organized in such a way that makes it easy to figure out which one you need to use. Categories like Event Management, Constituent Management and so on make sense to me.

    I wonder if Microsoft will need to address the size limitation in the future - from what I can tell, the Power Platform has been taking off, and if they want to enable people to create complex flows, they're going to need to allow connectors enough room to include all of the functionality available.

    Until then, our flows will just need to have a few more connections!

Categories