Skip to main content
This integration makes Ironclad the system of record for your Trust Center NDAs. Requesters from companies with an active NDA in Ironclad get access without signing again, and every NDA signed through Wolfia lands in Ironclad automatically with the signed copy attached.

​
What the integration does

Ironclad plays two roles in the Trust Center access flow:

Skip signing when an NDA exists

When someone requests access, Wolfia checks whether their company already has an active NDA in your Ironclad repository. If it does, the signing step is skipped and access proceeds under the existing agreement.

Mirror new NDAs into Ironclad

When a requester signs your NDA through Wolfia (click-accept, Wolfia e-signature, or DocuSign), Wolfia creates a record in Ironclad with the signed copy attached, so your legal team sees it where they already work.

​
How the access flow works

When a visitor requests access to your Trust Center and your portal requires an NDA:
  1. Wolfia looks up the requester’s company in your connected Ironclad repository.
  2. If an active NDA with a signed copy is on file, signing is skipped. The account timeline records “Checked Ironclad for existing NDA: found, signing skipped”, and the Slack notification for the request notes that an active NDA is already on file.
  3. If no NDA is found, the requester signs through your configured signing method (click-accept, Wolfia e-signature, or DocuSign).
  4. After signing, Wolfia creates an Ironclad record for the agreement, attaches the signed PDF, and fills the record’s fields using your field mapping.
Wolfia keeps a mirror of your Ironclad NDA records and refreshes it on a schedule, so lookups are instant and newly pushed records are visible to future access requests right away. Accounts with an NDA found in Ironclad show a “Synced from Ironclad” indicator on the account details page.

​
Prerequisites

  • An Ironclad account with API access and a repository (records) workspace.
  • Either an Ironclad API token with records read and write permission (created under Company Settings › API › Tokens), or an OAuth client credentials app scoped to read and create records, attachments, and schemas.
  • Your Ironclad region: na1, eu1, or au1. You can read it from your Ironclad URL.
  • A record type in Ironclad for NDAs, with an attachment slot for the signed copy and a property that holds the counterparty name.
  • Admin access to your Wolfia Trust Center.

​
Connect Ironclad to Wolfia

1

Open the NDA settings

In Wolfia, go to Trust Center › NDA and find the Mirror signed NDAs to Ironclad section, then click Connect Ironclad.
2

Enter your credentials

Choose your authentication method:Credentials are validated against Ironclad before anything is saved, and they are stored encrypted.
3

Map your record type and fields

Click Fetch from Ironclad to pull your live record schema, then choose:
  • The record type used for NDAs
  • The attachment slot where the signed copy should land
  • Field mappings for the record’s properties
Each mapping row pulls its value from Wolfia (company name, requester email, requester position, signer name, signature date), from Salesforce (account ID, region) if you have the Salesforce integration connected, from a fixed value you type in, or is skipped.
4

Click Connect

Click Connect to finish. The section now shows a Connected badge with your workspace, region, record type, company field, and attachment key. Wolfia starts syncing your existing Ironclad NDA records right away so lookups work immediately.

​
Managing the connection

  • Field mapping lets you adjust which Ironclad properties Wolfia fills, at any time.
  • Disconnect stops future lookups and pushes. Records already created in Ironclad are left untouched.
  • Per-account overrides still apply: marking an account as having an external NDA, or enabling Skip NDA for CRM-matched requesters, satisfies the NDA requirement before the Ironclad lookup runs.

​
Troubleshooting

Confirm the region matches your Ironclad URL and that the token or OAuth app has records read and write permission. Wolfia validates credentials by reading your records metadata, so a token scoped too narrowly fails at this step.
Wolfia matches on the company name the requester entered against the counterparty name on the Ironclad record, and only counts records that are active and have a signed copy attached. Check that the Ironclad record has the signed document in the configured attachment slot and that the counterparty name matches the company name on the access request. The account timeline shows the result of every Ironclad check.
Confirm the connection still shows the Connected badge on the NDA page and that the acting user (for OAuth) still exists in Ironclad. The record is created with the type and attachment slot from your field mapping, so a record type that was deleted or renamed in Ironclad blocks the push.

Trust Center

Set up your Trust Center, access requests, and NDA requirements.

DocuSign integration

Route NDA signing through DocuSign envelopes.

Salesforce integration

Connect your CRM to enrich access requests and field mappings.