Implementing the Power Automate connection: test and production checklist

This is the practical implementation guide for the Power Automate connection, with a checklist for both a test environment and production. The numbered steps below give the order; then use the checklists per environment. The full per-step explanation is in Setting up the Power Automate connection.

Checklist — test environment

• ☐ OAuth client created in i-Reserve (client ID + strong secret noted).
• ☐ Connection user created with the correct, limited rights.
• ☐ swagger.json downloaded from /api/rest/microsoft/swagger.
• ☐ Custom connector created in Power Automate via “Import an OpenAPI file”.
• ☐ Security configured: OAuth 2.0 with Authorization, Token and (identical) Refresh URL.
• ☐ Connector's Redirect URL entered back into the i-Reserve OAuth client.
• ☐ Connection created and tested with the connection user.
• ☐ First test flow built and tested end-to-end with a real event.

Checklist — production environment

• ☐ Separate OAuth client and connection user in the production environment (do not reuse test credentials).
• ☐ Fresh swagger.json from the production environment used (fields can differ per environment).
• ☐ Production Redirect URL registered on the OAuth client in production.
• ☐ Connection user's rights verified against least privilege.
• ☐ First live flow verified; error handling/notification on failure configured.
• ☐ Off switch known: disabling the connector/connection or the flow stops the automation.