Skip to main content
PDF4me APIIntegrationsKnowledge BaseExtensionsAPI TesterBlog

AI-Process Contract in Make

What this module does

PDF4me AI-Process Contract extracts structured metadata from PDF or image legal contracts inside your Make scenario using AI. Supply an MSA, NDA, SOW, employment agreement, or any business contract and the module returns all parties (with names, addresses, and roles), execution date, effective date, expiration date, contract duration, and governing jurisdiction — the exact fields needed for contract lifecycle management (CLM), expiration tracking, automated renewal reminders, contract repository indexing, and compliance reporting. No template setup. Works across common-law and civil-law drafting conventions worldwide.

Authenticating Your API Request​

Every PDF4me module in Make requires a valid Connection. Create or select one that holds your PDF4me API key so the scenario can authenticate AI contract extraction requests securely.

Get your API Key

Important Facts You Should Not Miss​

Parties output is an array — supports multi-party contracts
Two-party agreements, three-party consortium contracts, and complex distribution networks all use the same structured parties array. Each entry includes name, address, and reference designation (Buyer, Seller, Licensor, Disclosing Party, etc.) — no special handling required for multi-party scenarios.
ISO 8601 date strings drive expiration tracking
executionDateStr, effectiveDateStr, and expirationDateStr all return in ISO 8601 (YYYY-MM-DD) format. Schedule a daily Make scenario to query contracts expiring within 30/60/90 days and trigger renewal reminders — eliminate missed renewals and unintended auto-renewals.
Jurisdiction object captures governing law and venue
The jurisdiction output is a structured object with the governing law, the agreed court or arbitration venue, and the region. Use it for compliance dashboards, sanctions screening, and routing contracts to the right legal counsel based on the applicable jurisdiction.
Make PDF4me AI-Process Contract module configured with Connection set to My PDF4me connection, File set to Map with Contract Name and Document mapped from the previous file source step, ready to extract parties, execution date, effective date, expiration date, contract duration, and governing jurisdiction

Set File to Map, wire Contract Name and Document from the prior module. Output exposes parties, key dates, duration, and jurisdiction — the foundation of CLM and compliance workflows.

Parameters​

Required: Connection, Contract Name, and Document must always be provided. The matching input field (Binary Property, Base64 Content, or Contract URL) is required based on the chosen Input Data Type.

ParameterRequiredWhat it doesExample
ConnectionYesPDF4me API connection. Click Add and paste your API key the first time. Reused automatically across all PDF4me modules in your scenarios.My PDF4me connection
Input Data TypeYesHow the contract file is supplied. Binary Data reads from a previous module (most common for DocuSign/Adobe Sign integrations). Base64 String accepts encoded payloads. URL downloads from a public link.Binary Data
Input Binary FieldConditionalBinary content of the contract file. Required when Input Data Type is Binary Data. Wire from DocuSign, Adobe Sign, SharePoint, Dropbox, or any document-source module.1. Data
Base64 Contract ContentConditionalBase64-encoded contract content. Required when Input Data Type is Base64 String. Useful when the contract arrives via secure API or e-signature webhook.JVBERi0xLjQK...
Contract URLConditionalPublic URL to the contract file. Required when Input Data Type is URL. The URL must not require authentication.https://example.com/msa.pdf
Contract NameYesFilename of the contract with proper extension (.pdf, .png, .jpg, .jpeg). Used for format detection and AI processing optimization.msa-2024.pdf

Output Fields​

FieldTypeWhat it contains
partiesArrayArray of contract parties. Each entry has name, address, and a reference designation (Disclosing Party, Receiving Party, Buyer, Seller, Licensor, Licensee, etc.). Supports two-party and multi-party contracts.
executionDateStrStringDate when the contract was executed or signed, in ISO 8601 format (YYYY-MM-DD).
effectiveDateStrStringDate when the contract becomes effective, in ISO 8601 format. May differ from the execution date.
expirationDateStrStringDate when the contract expires, in ISO 8601 format. Use for renewal reminders and expiration tracking.
contractDurationStringDuration or term of the contract as stated in the document (e.g. "3 years", "12 months", "perpetual until terminated").
jurisdictionObjectJurisdiction object containing the governing law, the agreed court or arbitration venue, and the region. Use for compliance routing and sanctions screening.
successBooleanTrue if the AI extraction completed successfully; false if it failed.
messageStringHuman-readable status message confirming success or describing the error.

Quick Setup​

  1. Add PDF4me → AI-Process Contract to your Make scenario.
  2. Select Connection (or click Add to create one with your PDF4me API key).
  3. Choose Input Data Type — Binary Data for files from DocuSign, Adobe Sign, SharePoint, or any document module.
  4. Under File, choose Map to reveal Contract Name and Document fields.
  5. Map Contract Name to the filename with extension (.pdf, .png, .jpg, or .jpeg).
  6. Map Document to the binary content from the source module — the Data field of DocuSign, Adobe Sign, SharePoint, OneDrive, or Dropbox modules.
  7. Click Save and run the scenario. Wire the output bundle into a CLM platform (Ironclad, ContractWorks, DocuSign CLM), a contract repository (SharePoint, Airtable), or compliance dashboards.

Workflow Examples​

Workflow ExamplesCommon Make scenario patterns using AI-Process Contract.
Signed DocuSign envelope → AI extract → CLM repository
  1. A DocuSign Completed Envelope trigger fires when a contract is fully signed by all parties.
  2. The signed PDF is passed to AI-Process Contract. The output bundle returns parties, executionDateStr, effectiveDateStr, expirationDateStr, and jurisdiction.
  3. A SharePoint Upload step stores the signed PDF in the contract repository under a folder named with the primary party and execution year.
  4. An Airtable Create Record step indexes the contract with all extracted metadata for searching, filtering, and reporting.
  5. A Slack notification announces the new contract to the legal-ops channel with all key dates and party names.
Scheduled scan → expiring contracts → renewal reminders
  1. A scheduled trigger fires every weekday morning at 09:00.
  2. An Airtable search step queries contracts with expirationDateStr falling within the next 30, 60, or 90 days.
  3. A Make Iterator processes each expiring contract. For 90-day-out contracts, a Slack message goes to the contract owner with a renewal-needed prompt; for 60-day, a follow-up email; for 30-day, an escalation to legal counsel.
  4. Each notification includes the parties, expirationDateStr, and a direct link to the signed contract in SharePoint.
  5. An Airtable update flags the contract row as Reminder Sent with timestamp so the next scheduled run does not re-send the same reminder.
Vendor contract upload → jurisdiction check → counsel routing
  1. A SharePoint Watch Files trigger fires when procurement uploads a draft vendor contract for legal review.
  2. AI-Process Contract extracts the parties and jurisdiction object — governing law, court venue, region.
  3. A Router branches on jurisdiction.region. US contracts route to US counsel, EU contracts to EU counsel, Asia-Pacific to AP counsel — each branch sends an Asana task to the right legal team member.
  4. A Tools Set Variable step checks the parties array against a sanctions screening list. Any flagged party halts the workflow and notifies compliance immediately via Slack.
  5. The contract metadata is logged to Airtable with the assigned reviewer, jurisdiction, and a status of In Review — ready for the reviewer to update once their analysis completes.

Frequently Asked Questions​

What contract fields does AI-Process Contract extract?+
The module returns the key metadata fields used for contract lifecycle management: parties (array of all contract parties with names, addresses, and reference designations like Buyer, Seller, Licensor, Licensee, Disclosing Party, Receiving Party), executionDateStr (signing date in ISO 8601), effectiveDateStr (start date in ISO 8601), expirationDateStr (end date in ISO 8601), contractDuration (term or duration string), and jurisdiction (object with governing law, court venue, and region). Together these are the fields most CLM platforms, contract repositories, and compliance dashboards need for tracking, renewal, and audit.
What types of contracts work best with the parser?+
The AI handles a wide range of business contracts: Master Service Agreements (MSAs), Statements of Work (SOWs), Non-Disclosure Agreements (NDAs), employment contracts, supply contracts, distribution agreements, software licensing contracts, lease agreements, partnership agreements, consulting agreements, and vendor contracts. Both digitally produced contracts (Word or contract software output) and scanned executed contracts (signed paper versions) are supported in PDF, PNG, JPG, and JPEG formats.
How can I track contract expiration dates automatically with this parser?+
Pair AI-Process Contract with a Make scheduled scenario. Extract the expirationDateStr from every contract uploaded to your repository and log it to Airtable, Google Sheets, or a CLM system. A separate scheduled scenario queries that table daily for contracts expiring in 30, 60, or 90 days and sends Slack messages or emails to the contract owner with the expiration date and a link to the signed PDF. This eliminates missed renewals and surprise expirations — a leading cause of unintended contract auto-renewals and compliance gaps.
Does the parser identify all parties in multi-party contracts?+
Yes. The parties output is an array — each entry contains the party name, registered address, and reference designation (Disclosing Party, Receiving Party, Buyer, Seller, Licensor, Licensee, etc.). This works correctly for two-party contracts (vendor-customer, employer-employee) and complex multi-party agreements (consortium agreements, distribution networks, partnership agreements with three or more parties) without any configuration changes. Iterate over the parties array in Make to handle each party in your downstream workflow.
How accurate is the AI at extracting jurisdiction and governing law?+
The jurisdiction output is a structured object that captures the governing-law clause: the law cited (State of Delaware, Laws of England and Wales, German law, etc.), the agreed court or arbitration venue, and the broader region. The AI is trained on contract templates from major jurisdictions including the US (state-by-state), UK, EU member states, India, Australia, Singapore, and UAE, and handles both common-law and civil-law drafting conventions accurately. Use the jurisdiction.region field to route contracts to the correct legal counsel automatically.

Get Help​

Make IntegrationGet your API KeyMake Documentation