- Home
- Resources
- Integrations
- Adobe Acrobat Sign
Adobe Acrobat Sign Zapier integrationAutomate Adobe Acrobat Sign with Zapier.
The Adobe Acrobat Sign Zapier integration offers 10 triggers, 6 actions and 5 searches. All ten triggers are instant: a signature, a rejection or an expired agreement reaches your Zap the moment it happens, on every plan, the free one included.
Verified Trustpilot reviews · AI, automation & growth agency
What the Adobe Acrobat Sign Zapier integration does for your contracts
The Adobe Acrobat Sign Zapier integration connects your e-signature account to the rest of your tools. When an agreement moves (created, viewed, signed, rejected, expired), Zapier runs the steps you chose. In the other direction, Zapier can upload a document, send it for signature, and pull back the signed PDF or its audit trail.
Three outcomes pay off fast. A signed copy filed without anyone downloading it: Agreement Signed by All Participants feeds Create a PDF of Signed Agreement, and the file goes wherever your next step sends it. Contracts sent from another tool: Upload a Document to Get Document ID, then Create an Agreement From Uploaded Document, turns a generated file into a signature request. Answers captured from the form: Find Form Field Data of Agreement in JSON Format brings back what signers typed into the agreement's fields.
What it does not do: none of the six actions recalls, cancels, reminds or edits an agreement. Recalls and reminders have a trigger, so a Zap can react to them, but no step can perform them. And sending always takes two steps, upload then create, unless you start from a library template.
The Adobe Acrobat Sign Make integration page covers the same app in Make; to weigh the two tools against each other, see Make vs Zapier.
Zapier vocabulary, in plain words
Eight words carry this whole page. Here is what each means for someone who sends contracts with Adobe Acrobat Sign.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event that starts the Zap, like an agreement signed by everyone. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that creates, uploads or sends something for you, in Acrobat Sign or elsewhere.
- Task
- The unit Zapier bills. Each action completed successfully counts as one, and your plan is a monthly count of those.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. Acrobat Sign has none of these.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a check.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something that already exists, like an agreement's status, so the steps after it can use what it found.
What an Adobe Acrobat Sign Zap really costs
Zapier bills actions, never triggers. Waiting for signatures costs nothing, whatever the volume of agreements.
- Tasks per month, free plan100
- Steps per Zap, free plan2 (one trigger, one action)
- Cost of a trigger0 tasks
- Premium appNo
Each action that succeeds is one task; a failed one is not counted. A Zap with three actions uses three tasks per run. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. A second action, a filter or a search turns it into a multi-step Zap (anything beyond one trigger and one action), which needs a paid plan. Adobe Acrobat Sign is not a premium app, and since every trigger is instant, the interval grid below never slows it down.
Connect your Adobe Acrobat Sign account in three steps
- 01
Open the Apps page
In Zapier, open Apps and click + Add connection. You need an Adobe Acrobat Sign account, plus read or write access to any agreement you do not own yourself but want the Zap to touch.
- 02
Pick Adobe Acrobat Sign
Search for Adobe Acrobat Sign in the dialog, select it and click Add connection. A new tab opens on the Adobe sign-in screen, which you fill in at the next step.
- 03
Sign in and grant access
Log in to Adobe Acrobat Sign and accept the access Zapier asks for. That connection (your account linked once to Zapier) is then reused by every Acrobat Sign step in every Zap.
Your first Zap: file the signed contract and its audit trail
GoalWhen every participant has signed, create the signed PDF and the audit trail PDF, so the final contract and its proof are ready together.
- 01
Build: pick the trigger
Create a Zap, choose Adobe Acrobat Sign and the event Agreement Signed by All Participants. Select your connection and type a Name for the webhook, such as "Signed contracts to archive".
- 02
Test the trigger
Run the test. Zapier brings back the three most recent completed agreements of the account, so you map the next steps on a real one, not on a blank sample.
- 03
Create the signed PDF
Add the action Create a PDF of Signed Agreement and map the agreement's identifier from the trigger's test item into Agreement ID.
- 04
Add the audit trail
Add Create a PDF of the Agreement's Audit Trail with the same Agreement ID. Two actions make this a multi-step Zap, which needs a paid plan.
- 05
Test, then Publish
Test each action once and open both files to check that they belong to the right contract. When they look right, click Publish to switch the Zap on.
Adobe Acrobat Sign triggers on Zapier
10 events start a Zap when something happens in Adobe Acrobat Sign, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.
Agreement Signed by a Participant
Instant triggerIn Zapier“Triggers when an Agreement is Signed by a Participant”
Starts the Zap each time one participant signs, before the agreement is complete. On a contract with three signers, it can fire three times.
Agreement Created
Instant triggerIn Zapier“Triggers when a new Agreement is Created.”
Fires when a new agreement is created in Adobe Acrobat Sign. It is the earliest point you can catch a contract on its way out.
Agreement Email Viewed
Instant triggerIn Zapier“Triggers when an Agreement Email is Viewed”
Reacts when a recipient opens the agreement email. It tells you the contract has been seen, which is a different signal from being signed.
Agreement Event Occurred
Instant triggerIn Zapier“Triggers when Any Agreement Event Occurred.”
Catches any event on any agreement. It is the widest net of the app: everything the more specific triggers report, and whatever else happens to an agreement.
Agreement Expired
Instant triggerIn Zapier“Triggers when an Agreement has Expired.”
Fires when an agreement reaches its expiry without being completed. That is a lost signature, and usually a deal or a hire that stalled.
Agreement Recalled
Instant triggerIn Zapier“Triggers when an Agreement is Recalled.”
Tells you when the sender recalls an agreement, which withdraws it from the signers. Useful to keep other tools from still treating the contract as pending.
Agreement Rejected
Instant triggerIn Zapier“Triggers when an Agreement is Rejected.”
Runs when a participant declines to sign. A rejection is the signal that needs a human the fastest, so this trigger often feeds an alert.
Agreement Reminder Sent
Instant triggerIn Zapier“Triggers when an Agreement Reminder is Sent.”
Fires when Adobe Acrobat Sign sends a reminder for an agreement still waiting. It shows where signatures are dragging.
Agreement State Changed
Instant triggerIn Zapier“Triggers when an Agreement is Created, Recalled, Rejected, Expired, Signed by a Participant or Workflow Completed.”
Groups six moments in one trigger: created, recalled, rejected, expired, signed by a participant, signed by all. One Zap can follow the whole life of a contract.
Agreement Signed by All Participants
Instant triggerIn Zapier“Triggers when an Agreement Workflow is Completed”
Waits until every participant has signed, then starts the Zap once. It is the trigger for anything that should only happen on a finished contract.
Adobe Acrobat Sign actions on Zapier
Adobe Acrobat Sign gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create an Agreement From Uploaded Document
ActionIn Zapier“Create an Agreement From Uploaded Document and Send for Signature”
Builds an agreement from an uploaded document and sends it for signature. You give it the Document ID, an agreement name, and at least one participant with order, role and email.
Create an Agreement From a Library Template
ActionIn Zapier“Create an Agreement from a Library Template and Send for Signature”
Sends an agreement based on a template saved in your Adobe Acrobat Sign library, with a name and at least one participant.
Create a PDF of Signed Agreement
ActionIn Zapier“Create a PDF of the Signed Agreement”
Produces the signed agreement as one PDF, from its Agreement ID, ready for the next step to store or send.
Upload a Document to Get Document ID
ActionIn Zapier“Upload a Document to Get Document ID”
Uploads a file to Adobe Acrobat Sign and hands back a Document ID. It needs a file name and the file content, and it is the first half of sending a fresh document.
Create a PDF of the Agreement's Audit Trail
ActionIn Zapier“Create a PDF of the Agreement's Audit Trail”
Generates the audit trail of an agreement as a PDF, from its Agreement ID: the record of what happened to it and when.
Create a Document From an Agreement
ActionIn Zapier“Create a Document From an Agreement”
Pulls one specific document out of an agreement, from both the Agreement ID and the Document ID.
Adobe Acrobat Sign searches on Zapier
5 search steps look for data that already exists in Adobe Acrobat Sign, so a later step can use it.
A search step looks up something that already exists in Adobe Acrobat Sign and passes it to the steps after it. In the editor, searches sit at the bottom of the Action event list under SEARCH, and some fields offer + Add search step to insert one for you. This app has no find-or-create variant: its searches only read. Three settings decide what happens when results are odd.
Find a List of All Agreements
SearchIn Zapier“Find a List of All Agreements”
Returns the agreements held in the name of a given user. That required field is what scopes the list.
Find the Agreement Status
SearchIn Zapier“Find the Agreement Status”
Looks up where an agreement stands right now, from its Agreement ID, so a later step can act on it.
Find a List of All Document IDs of Agreement
SearchIn Zapier“Find a List of All Document IDs of Agreement”
Lists the Document IDs inside an agreement. It exists mainly to feed Create a Document From an Agreement.
Find Form Field Data of Agreement in JSON Format
SearchIn Zapier“Find Form Field Data of Agreement in JSON Format”
Returns what participants entered in the form fields of an agreement, from its Agreement ID, in a structured format.
Find the Signing URL
SearchIn Zapier“Find the Signing URL”
Gets the link a participant uses to sign an agreement, from its Agreement ID.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there. Switch it on and the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Turns a search into a find-or-create. None of the Acrobat Sign searches offer it, so they never create anything.
- If multiple search results are found?Keep the first match (the default), stop the Zap, or hand all of them on at once.
When an Adobe Acrobat Sign Zap breaks
Zapier links one help article to this app, How to get started with Adobe Acrobat Sign on Zapier. Beyond that, the breakdowns to plan for are Zapier's general limits, read through how signatures work.
Watch three things: what the Zap cannot see, what it restarts on its own, and the order of the steps when you send. When a run fails, head to Zapier troubleshooting.
No catch-up on old agreements
A Zap only reacts to what happens after you publish it. Contracts signed or rejected before that are never picked up; moving that history is a separate job.A Zap that sends to itself
Agreement Created with an action that creates agreements restarts the Zap with every contract it sends, and the loop burns through your tasks.Bulk sends held back
A sudden batch of events, after a mass send or a migration, can be held by Zapier's flood protection instead of running all at once.Sending without a Document ID
Create an Agreement From Uploaded Document needs the ID from Upload a Document to Get Document ID. Skip the upload step and the send fails.
Need help automating Adobe Acrobat Sign with Zapier?
A person reads every message.



