Seeking Best Practices for Integrating Power Automate & Sky API Add-ins into NXT

Amber Morgan

I'm looking to gather some best practice insights on utilizing Power Automate/Sky API Apps to integrate add-ins into the NXT environment. Specifically, I’m curious about whether your organizations use generic accounts like Developer@abcdefg.com or individual user accounts for this purpose.

What are the pros and cons of each approach? I want to ensure that our setup is robust and resilient, even if a team member were to leave unexpectedly.

Thanks in advance for your suggestions and experiences!

Erik Leaver

@Amber Morgan Great question! We recommend having two accts – a generic account and an individual user account. The individual acct can be used for the dev work and then be shared with the generic account and then you can schedule all of the flows through the generic account. This safeguards for staff turnover.

Josh Gould

@Amber Morgan
We use a generic account so that we don't have to worry about losing anything. If you have everything tied to an individual account your IT team can still move the flows after the user leaves the org, but if the flows are using older connectors you will run into issues.

Joe Killian

@Erik Leaver, @Josh Gould I'm curious, how are orgs handling MFA for a generic BBID account (e.g. ITDept@org.org)

Ben Regier

@Joe Killian
We use BitWarden for Business. Allows us to share credentials across the team, and you can set up the TOTP in BitWarden so anyone on your team can generate the MFA codes.

Joe Killian

@Ben Regier

Thank you for the reply, we'll look into that and see if it's viable for our org.