Prerequisites

Ironclad CLM

1. API Access: Your Ironclad environment will need to have API access enabled, since the Power Automate connector makes use of the Ironclad public APIs to enable the integration.
2. Authentication: Ironclad uses the OAuth 2.0 Authorization Framework to authenticate API requests. In order to allow your Power Automate flows to access the Ironclad API, you’ll need to configure an OAuth client application for them. See the following documentation to Register your OAuth client application.
   (Set the Redirect URI to: https://global.consent.azure-apim.net/redirect/ironcladclm
   For OAuth Scopes, select the ones that match your intended API endpoints. If you’re uncertain which scopes you need, you can include all available OAuth Scopes to ensure full access.) Important: Select Authorization Code for the Grant Type
3. Ironclad User Account: Several of the solution patterns require specifying an Ironclad user for actions (e.g., who is approving, who is commenting, etc.). Creating a generic Ironclad user account that your integration can use to register actions is recommended for consistency and simplicity.
4. Ironclad Workflow(s): Workflows will need to have been created in your Ironclad instance in order to test your Power Automate connector. Please review the Workflow Designer Step-by-step instructions for general instructions on using the Workflow Designer in Ironclad. The details required for the workflow used by our example are spelled out in the section Basic Setup below .
5. Reference Documentation: Please see Ironclad’s API Reference documentation for the most up-to-date details on our endpoints. For information on building workflows in Ironclad, please see Ironclad Academy for guided training and Ironclad Support Center for product articles.

Power Automate

To create an integration you will need to use the Ironclad Power Automate Connector, and native Microsoft connectors such as Dataverse Connectors. Here is a list of prerequisites:

1. Microsoft Account: You will need a Microsoft account to sign in to Power Automate. Access to Power Automate is part of your Office 365 or Microsoft subscription.
2. PowerAutomate or PowerApps Premium License: The use of this custom connector required the implementing user to have an adequate premium license.
3. Environment Maker Role: Required to create and manage custom connectors.
4. Admin Approval: May be needed for custom connector deployment.
5. Data-Loss-Prevention Policy: Your policy needs to be configured to allow the Ironclad Connector in the same connector category as any other connector you will use in conjunction with it. By default, the connector will be in the “Non-Business” category.
6. Visit Microsoft’s Power Automate learning center for various resources related to connectors, flows, and other components we leverage in this guide.

Developer Tools

1. Visual Studio Code: Download and install from https://code.visualstudio.com/
2. Power Platform CLI: Install the Power Platform CLI tools
3. Git: For cloning the repository