Ironclad integration: Import contracts
Overview
Ramp can connect to your Ironclad workspace and import completed contracts into Ramp. After setup, Ramp checks for new contracts daily, creates Ramp contract records with source documents, links them to vendors when possible, and gives your team a sync history for monitoring imports.
Use Ironclad contract ingestion if your team stores executed agreements in Ironclad and wants those agreements visible in Ramp for vendor contract tracking, renewal workflows, and procurement visibility.
Ironclad contract import is available when your business has access to Contracts & renewals, Ironclad is connected to Ramp, and your user role can manage integrations and create contracts.
Prepare Ironclad contract import
Before importing contracts, confirm that:
- Your business has access to Contracts & renewals.
- Your user role can manage integrations and create contracts.
- An Ironclad Admin has connected Ironclad to Ramp and authorized Ramp for your Ironclad workspace.
- Each Ironclad record you want to import has an executed signed copy.
- Vendor names in Ramp Vendors are similar to the corresponding counterparty names in Ironclad. This helps Ramp match contracts to the correct vendor.
If you cannot manage integrations and create contracts, ask a Ramp Admin or Owner to connect Ironclad and turn on contract import.
Turn on automatic Ironclad contract import
Once Ironclad is connected, a user with permission to manage integrations and create contracts can turn on automatic import:
- Open Contracts & renewals.
- Select New contract, then Import from Ironclad.
- Turn on Automatically import contracts from Ironclad.
- Review the confirmation and select Import contracts.
The first import backfills eligible existing Ironclad contracts. Keep automatic import on for daily incremental syncs. To start an additional sync, return to the Ironclad import drawer and select Sync contracts.
Understand Ironclad contract sync behavior
Ramp creates contract records from eligible Ironclad records, attaches the signed copy and additional attachments, and links each contract to a Ramp vendor when it can identify a match. The import drawer provides sync history for monitoring results.
Contract ingestion is a one-time transfer for each Ironclad record, not ongoing mirroring. Later changes to a successfully imported Ironclad record do not update the Ramp contract, and changes made in Ramp do not sync back to Ironclad. Update the Ramp contract separately when its source record changes. Ramp also skips Ironclad workflows launched from Ramp Procurement so the completed workflow does not create a duplicate contract.
Check which Ironclad records Ramp imports
Ramp imports an Ironclad record when all of the following are true:
- The record has an executed signed copy.
- At least one attached document is identified as a contract.
- Ramp can identify a matching vendor from the Ironclad counterparty or contract document.
- One contract document contains the vendor, start date, and total contract value.
When one document meets these requirements, Ramp imports the Ironclad record with its signed copy and additional attachments. Records that do not meet every requirement remain available in Ironclad but are skipped in Ramp.
Resolve Ironclad contracts that do not import
Contracts without a vendor match retry automatically during later daily syncs. Other ineligible records do not retry automatically. After correcting one of those records in Ironclad, create or upload the contract from Contracts & renewals.
| Possible cause | What it means | What to do |
|---|---|---|
| Missing signed copy | The Ironclad record does not have an executed signed copy available to import. | Add the executed contract document in Ironclad, then create or upload the contract in Ramp. |
| Not a contract | Ramp did not identify any attached file as a contract. | Add the actual contract document in Ironclad, then create or upload the contract in Ramp. |
| No vendor match | Ramp could not match the counterparty or contract document to a Ramp vendor. | Create the vendor in Ramp Vendors, or make the Ramp vendor and Ironclad counterparty names more similar. Ramp retries the match during future daily syncs. |
| Missing key contract fields | No single contract document includes the vendor, start date, and total contract value. | Correct the executed document in Ironclad, then create or upload the contract in Ramp. |
| Duplicate contract | Ramp found the same document or an existing contract with matching vendor, dates, and value. | Check the existing Ramp contract. No action is usually required. |
| Ramp-originated workflow | The Ironclad workflow was launched from Ramp Procurement. | No action is required. Ramp skips it to prevent a duplicate contract. |
Troubleshoot Ironclad contract import
Import from Ironclad is missing: Confirm that Ironclad is connected, you can manage integrations and contracts, and contract import is available for your business. If the option is still missing, contact Ramp Support.
An expected contract did not import: Confirm the Ironclad record has a signed copy, an identifiable contract document, a matching Ramp vendor, and one document with the vendor, start date, and total contract value. Vendor-match skips retry daily after you create or rename the Ramp vendor. For other corrected records, create or upload the contract in Ramp.
A sync failed: Select Sync contracts to retry. If the sync continues to fail, contact Ramp Support and include the failure message shown in the import drawer.
Frequently asked questions
Can I disconnect Ironclad after importing contracts?
Yes. Disconnect Ironclad from Integrations to stop future syncs. Contracts already imported into Ramp remain available after you disconnect the integration.
Can I still launch Ironclad workflows from Ramp Procurement?
Yes. Contract import is separate from using Ironclad in procurement approval workflows. See Ironclad integration: Set up to configure and launch Ironclad workflows from Ramp.