For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
The Ironclad connector is part of the Integration Hub. It connects the two places a vendor contract lives: the Ironclad workflow where the business owner requests and negotiates it, and the Coverbase intake request and due diligence that decide whether the vendor is acceptable.
Supported workflows
Workflows you do not pick, such as NDAs, are ignored. An NDA does not start due diligence on its own, because not every NDA turns into a vendor engagement.
Ongoing monitoring that is not tied to a contract, such as quarterly SLA reviews of critical vendors, stays in Coverbase. Your team starts it in Coverbase, not Ironclad.
How a request flows
- Launch in Ironclad. The business owner fills in the launch form for a vendor agreement. Ironclad tells Coverbase straight away through a webhook.
- Request opens in Coverbase. Coverbase reads the workflow from Ironclad’s API and opens an intake request. The vendor is matched to an existing vendor by website, then by name. If none matches, a new vendor record is created. Nothing is approved by this step.
- Questionnaire drafted. Coverbase drafts the inherent risk questionnaire from the workflow: the vendor, service, business purpose and contract value, plus up to 60 other attributes on the launch form (those with a value, in alphabetical order, each up to 500 characters). The business owner gets an email to review the draft, correct it and submit it.
- Review and due diligence. Your TPRM team reviews the request as usual. Approving it can launch an assessment, depending on your intake approval settings.
- Result back in Ironclad. When due diligence completes, or the request is declined, Coverbase updates the workflow and comments on it. When due diligence completes, and you set an approver role, it also approves that role. A declined request never approves it.
- Executed contract filed. When the workflow completes, the executed record and its signed copy file under the vendor in Coverbase.
Before you start
You need:- The Ironclad API add-on, and an Ironclad admin who can create an OAuth client under Company Settings → API.
- An Ironclad user for Coverbase to act as, for example
coverbase-integration@yourcompany.com. Every API call runs with that user’s permissions, so the user needs access to the workflows and records Coverbase reads and writes. - A Coverbase admin with permission to manage integrations. The Integration Hub is part of the third-party lifecycle features, which your Coverbase representative turns on.
- Business owners who launch workflows should have a Coverbase login. A business owner without one cannot receive the questionnaire; the request goes to the Coverbase admin who connected Ironclad instead.
Step 1: Create the OAuth client in Ironclad
- In Ironclad, open Company Settings → API and create a new client application.
- Under Grant Types, select Client Credentials.
- Select these scopes:
- Copy the Client ID and Client Secret. Ironclad shows the secret once.
Step 2: Add the write-back fields to your templates
Coverbase writes its result into workflow attributes, so each template you pick needs a field for each value you want back. Ask your Ironclad admin to add these to the launch form as text fields that are not required, and note each field’s ID:Ironclad accepts attribute and approval changes only while a workflow is in the Review step. If the workflow is not in Review when due diligence finishes, Coverbase still comments on it, and writes the fields and approval on a later sync once the workflow is in Review.
Step 3: Connect Ironclad in Coverbase
- Open Configuration → External Integrations and click Ironclad, or open Integration Hub and click Ironclad.
- On Authentication, enter:
- Instance URL: the address you sign in to Ironclad at, such as
https://na1.ironcladapp.comorhttps://eu1.ironcladapp.com. - Client ID and Client Secret from step 1.
- Acting User Email: the Ironclad user Coverbase acts as.
- Instance URL: the address you sign in to Ironclad at, such as
- Click Connect, then Test connection. A failed test names what Ironclad refused, usually a missing scope.
Step 4: Choose the templates that start due diligence
- On Authentication, under Workflow Intake, click Load templates from Ironclad.
- For each template, choose what it starts:
- New vendor due diligence for new vendor agreements, order forms and partner agreements.
- Renewal or amendment review for renewals and amendments of an existing vendor.
- Nothing for templates that should not involve TPRM, such as NDAs.
- Under Workflow Attributes, enter the field ID that holds each value on the launch form. Vendor Name is required. Vendor Website improves vendor matching, and Service Name, Business Purpose and Contract Value give the questionnaire draft more to work from. Leave Business Owner Email blank to send the questionnaire to whoever launched the workflow.
- Click Save.

The Authentication tab with templates, workflow attributes, write-back options and the webhook.
Step 5: Choose what Coverbase writes back
- Under Write Back to Ironclad on Authentication:
- Leave Comment on the workflow when due diligence is complete or declined on to post a comment that mentions the business owner.
- Enter the Approver Role ID if Coverbase should approve a role when due diligence completes. Leave it blank if Coverbase is not an approver.
- Open Field Mappings. Under Workflows, enter the field ID from step 2 for each value you want written back, and switch off the rest.
- Under Contracts, check the outbound rows if you also want the vendor’s risk rating, required clause pack and blocking issues written onto executed records.
- Click Save mappings.

Workflow write-back mappings on the Field Mappings tab.
Step 6: Register the webhook
- On Authentication, under Webhooks, click Register webhook in Ironclad.
Step 7: Test it end to end
- In Ironclad, launch a workflow from a template you picked, with a test vendor name.
- In Coverbase, open the Ironclad connection’s Sync Log. The workflow appears as Created with the vendor it was matched to. A template you did not pick appears as Skipped, with the reason.
- Check that the business owner received the questionnaire email, then submit the request and approve it.
- Click Sync now or wait for the next sync. The Sync Log shows an outbound Workflows row, and the workflow in Ironclad shows the written fields and Coverbase’s comment.
- Complete the workflow in Ironclad. The executed record appears in the Sync Log as a Contract row, and the contract with its signed copy appears under the vendor in Coverbase.
What the sync log tells you

A sync run with a request opened, an NDA skipped, a result written back and an executed contract filed.
Troubleshooting
Onboarding checklist
- The Ironclad API add-on and an OAuth client with the scopes in step 1.
- An Ironclad user for Coverbase to act as.
- The templates that start due diligence, and which are renewals.
- The launch form field IDs for vendor name and, ideally, vendor website, service, business purpose and contract value.
- Write-back fields on those templates, and an approver role if Coverbase approves.
- Business owners set up as Coverbase requesters.
Related
Integration Hub guide
Field mappings, the sync log and webhooks.
Requesting a vendor
What the business owner sees when they complete the request.
Front Door triage
How TPRM reviews and approves the request.
Contract intake and approval
What happens when a contract is executed.