GuidesAPI ReferenceRecipes
Guides
Request a Demo
Start typing to search…

Setting Up the Ironclad Power Automate Connector



Overview

The Ironclad Power Automate Connector is available as an open-source solution that must be manually uploaded to your Power Platform environment. This guide walks you through downloading the connector from GitHub and configuring it in Power Automate.

Prerequisites

Power Platform Requirements

  1. Microsoft Account: You need a Microsoft account with access to Power Automate
  2. Power Automate or Power Apps Premium License: Custom connectors require a 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: Must allow custom connectors in your environment

Ironclad Requirements

  • OAuth Client Configuration: Before uploading the connector, ensure you have configured an OAuth app in Ironclad:
  • Navigate to Company Settings → API in Ironclad
  • Create a new OAuth application
  • Note your Client ID and Client Secret (you'll need these later)
  • Leave the Redirect URI blank for now (you'll update this after uploading the connector)
  • Select Authorization Code for the Grant Type
  • For OAuth Scopes, select all scopes to ensure full access
  • Detailed instructions for setting up the OAuth app can be found here: https://developer.ironcladapp.com/reference/register-oauth-client

Development 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

Uploading the Custom Connector to Power Automate

Step 1: Download the Connector from GitHub

  1. Open your terminal or command prompt
  2. Clone the repository:

bash

git clone https://github.com/maxhenkentech/MSPP-IroncladCLM.git

  1. Navigate to the cloned directory:

bash

cd MSPP-IroncladCLM

Step 2: Open in Visual Studio Code

  1. Launch Visual Studio Code
  2. Open the cloned repository folder
  3. Ensure all required extensions are installed (VS Code will prompt you if any are missing)

Step 3: Upload the Connector to Power Platform

3.1 Authenticate with Power Platform

  1. Open the terminal in VS Code (View → Terminal)
  2. Run the authentication command:

bash

paconn login

  1. This will provide a URL and authentication code
  2. Copy the URL and open it in your browser
  3. Enter the provided code when prompted
  4. Sign in with your Microsoft account that has access to Power Automate

3.2 Upload the Connector

  1. In the VS Code terminal, run the upload script:

bash

paconn create --api-prop apiProperties.json --api-def apiDefinition.swagger.json --icon icon.
png --scrip script.csx --secret dummy
Note: Replace [YOUR-ENVIRONMENT-ID] with your actual environment ID, or omit the environment parameter to be prompted for selection
  1. If prompted, select your Power Platform environment from the list
  2. The upload process will take approximately 30-60 seconds
  3. Wait for the confirmation message that the connector has been successfully uploaded

Step 4: Configure the Custom Connector in Power Automate

CRITICAL: Follow these steps exactly as described. The configuration is sensitive and incorrect settings will break the connector.

4.1 Navigate to Custom Connectors

  1. Log into Power Automate
  2. In the left navigation, expand "Data" and select "Custom connectors"
  3. You should see "IroncladCLM" in the list of custom connectors

4.2 Edit the Connector Security Settings

  1. Click on the IroncladCLM connector

  2. Click the "Edit" button (pencil icon)

  3. IMPORTANT: Do not modify anything on the General tab

  4. Navigate to the "2. Security" tab

  5. In the Authentication type dropdown, ensure "OAuth 2.0" is selected

  6. IMPORTANT: Do not modify anything on OAuth 2.0 tab**.** It will resemble screen below:

  7. Copy the Redirect URL shown in the connector configuration (it will look like: https://global.consent.azure-apim.net/redirect/ironcladclm)

4.3 Update Ironclad OAuth Configuration with the Redirect URL

  1. Return to Ironclad (Company Settings → API)
  2. Edit your OAuth application
  3. Paste the Redirect URL you copied from Power Automate
  4. Ensure the application is Active
  5. Save the OAuth application
  6. Copy the Client ID and Client Secret from Ironclad

4.4 Complete Power Automate Connector Configuration

  1. Return to the Power Automate custom connector configuration
  2. CRITICAL: Do NOT click "Update connector"
  3. Instead, click the back arrow to exit without saving

Step 5: Create a Connection in Power Automate

5.1 Test the Connector with a New Flow

  1. Navigate to "My flows" in Power Automate
  2. Click "New flow" → "Automated cloud flow"
  3. Give your flow a test name
  4. For the trigger, search for "Ironclad"
  5. Select any IroncladCLM trigger (e.g., "When a workflow is created")

5.2 Authenticate the Connection

  1. When prompted to create a connection, click "Sign in"
  2. Provide a connection name (e.g., "IroncladProduction")
  3. Enter your Ironclad instance URL (e.g., "https://demo.ironcladapp.com")
  4. Enter the Client ID from your Ironclad OAuth app
  5. Enter the Client Secret from your Ironclad OAuth app
  6. Leave Version as "default"
  7. Click "Sign in"
  8. You'll be redirected to Ironclad to authenticate
  9. Log in with your Ironclad credentials
  10. Click "Allow access" when prompted
  11. You should be redirected back to Power Automate with a successful connection

Step 6: Verify the Connection

  1. The connection should now appear in your list of connections
  2. Test the connection by:
  3. Creating a simple flow using an Ironclad trigger
  4. Running a test to ensure data is retrieved successfully
  5. Checking that available actions populate correctly

Troubleshooting

Common Issues and Solutions

Issue: "Unauthorized" error when creating connection

  • Solution: Verify Client ID and Secret are correct and the OAuth app is active in Ironclad

Issue: Redirect URL mismatch error

  • Solution: Ensure the Redirect URL in Ironclad exactly matches the one from Power Automate (including https://)

Issue: No scopes available

  • Solution: Check that OAuth scopes are properly configured in your Ironclad OAuth application

Issue: Connector upload fails

  • Solution:
  • Verify you have the correct permissions in Power Platform
  • Ensure you're authenticated with paconn login
  • Check that your environment allows custom connectors

Issue: Cannot see the custom connector after upload

  • Solution:
  • Refresh the Power Automate page
  • Check you're in the correct environment
  • Verify the upload completed successfully in VS Code

Once your connector is successfully configured and tested, you can proceed with:

  1. Creating automated flows between Dynamics 365 and Ironclad
  2. Setting up workflow triggers and actions
  3. Implementing the integration patterns described in this document

Remember to test thoroughly in a non-production environment before deploying to production.

Updated about 16 hours ago