Resources · Make integration

Adobe Acrobat Sign Make integrationAutomate Adobe Acrobat Sign with Make.

What if agreements went out and got tracked without anyone copying data by hand? The Adobe Acrobat Sign Make integration gives you 14 modules: one instant trigger, eight actions and five searches. This guide links your account and walks you through a first scenario.

Try the Adobe Acrobat Sign integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Adobe Acrobat Sign Make integration do for you?

The Adobe Acrobat Sign Make integration links your Acrobat Sign account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Your agreements can then be sent, checked and listed from other apps without writing code.

Contracts that leave on their own. A deal is marked as won in your CRM or a row lands in a sheet, and Create an Agreement builds the agreement and emails it to the signer. Sales stops preparing each envelope by hand.

A signature status everybody can see. Watch Events lets Acrobat Sign warn Make the moment something happens on an agreement. Add Get an Agreement right after it to read the current status, then push that status to the tool your team already opens.

A clean inventory of templates and groups. List Workflows, List Web Forms and List Groups return what exists in the account, so an admin can copy it into a sheet and spot what nobody uses anymore. Search Agreements does the same for agreements.

What the integration does not do: the 14 listed modules do not cover every part of the Acrobat Sign API. For the rest, Make an API Call reuses your connection to reach any other endpoint. The same app also has an n8n node, and our n8n vs Make comparison lays out the criteria. If you are new to the editor, Make training covers the basics, and Make pricing explains how operations are counted.

Connect

How do you connect Adobe Acrobat Sign to Make?

  1. 01

    Prepare your API credentials

    You need an active Acrobat Sign account with access to API credentials. In Acrobat Sign, open Account, then Adobe Sign API, then API Applications, create an application with the CUSTOMER domain, click Configure OAuth for Application, pick the scopes and copy the Client ID and the Client secret.

  2. 02

    Add a module and open the connection

    In Make, add any Adobe Acrobat Sign module to your scenario and click Create a connection. A connection is your Acrobat Sign account linked to Make once, then reused by every module of the app. Give it a name in Connection name if you want.

  3. 03

    Paste the credentials and confirm

    Enter the Client ID and Client secret you copied, or follow the instructions Make shows on screen, and save. From then on, Make can list the agreements, groups and workflows it reads in your account when you fill a module.

First scenario

Build your first scenario with Adobe Acrobat Sign

GoalWhen a new row lands in another app, Make creates an agreement in Adobe Acrobat Sign and emails it to the signer.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where your signer data lives, such as a sheet or a CRM, and its watch module.

  2. 02

    Add Create an Agreement

    Click the + on the right of that first module, search Adobe Acrobat Sign and choose Create an Agreement. Select your connection, or click Create a connection if this is your first module of the app.

  3. 03

    Map the signer data

    Fill the module fields by mapping data from the first module: each row that arrives becomes a bundle, one item passed to the next module, and each bundle produces one agreement sent by email.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Read the bundles each module received, and check in Acrobat Sign that the test agreement exists.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as an operation, the unit Make counts on your plan.

Triggers

What starts an Adobe Acrobat Sign scenario

1 module starts a scenario when something happens in Adobe Acrobat Sign. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Adobe Acrobat Sign as soon as it happens.

Adobe Acrobat Sign1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a new event given in the parameters is occured.”

You get a scenario that starts as soon as the event you choose happens in Acrobat Sign, without Make having to check the account over and over. You pick the event in the module settings, and each occurrence arrives as one bundle ready for the next modules.

How it fires
instant, Acrobat Sign calls Make through a webhook as soon as the event happens.
When to use it
when a change on an agreement has to reach another tool right away, for example to warn the account owner in a chat.
Watch out
this module carries the instant tag, so click Create a webhook before Create a connection when you set it up.
Modules

What Adobe Acrobat Sign can do in Make

Adobe Acrobat Sign gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Adobe Acrobat Sign1

Create an Agreement

Action

In Make“Creates a new agreement and sends it by email.”

This is the module that saves you from preparing each envelope: it creates a new agreement in Acrobat Sign and sends it by email to the people who must sign. It is the natural end of a scenario that starts in a CRM or a form.

When to use it
as soon as a deal is won or a request is approved in another app.
Watch out
the email leaves on every run, so test with your own address before you map real signers.
Adobe Acrobat Sign2

Get a Group

Action

In Make“Retrieves detailed information about the group.”

You obtain the full details of one group of your Acrobat Sign account, fetched by the scenario instead of looked up in the admin screens. It works on a single group that you already know.

When to use it
after List Groups, when the scenario needs the details of one group it found there.
Watch out
to cover every group, start from List Groups; this module only reads the one you point it to.
Adobe Acrobat Sign3

Get a MegaSign

Action

In Make“Gets detailed information of the specified MegaSign parent agreement.”

With this module you read the detailed information of one MegaSign parent agreement and can reuse it in the following modules, for a report or a message to the sender.

When to use it
when a MegaSign sending is already identified, for instance by List MegaSigns, and you want its details.
Watch out
it reads the parent agreement only; pick it from a previous bundle rather than typing it by hand.
Adobe Acrobat Sign4

Get an Agreement

Action

In Make“Retrieves the current status of an agreement.”

Here you learn where a single agreement stands: the module returns its current status so the scenario can decide what comes next. It pairs well with Watch Events: the trigger says something happened, this module tells you where the agreement stands now.

When to use it
right after an event, to route the agreement to the right follow up.
Watch out
it reads one agreement per run; for many agreements, use Search Agreements first.
Adobe Acrobat Sign5

Get a Web Form

Action

In Make“Retrieves the details of a web form.”

You get the details of one web form, pulled straight into the scenario so you can copy them elsewhere or check them before another step.

When to use it
when a web form picked by List Web Forms needs a closer look, for example to document it in a shared sheet.
Watch out
this module reads a form and changes nothing; it is safe to test with Run once as often as needed.
Adobe Acrobat Sign6

Get a Workflow

Action

In Make“Retrieves the details of a workflow.”

This module hands you the details of one Acrobat Sign workflow, so a scenario can show how that workflow is set up without anyone opening the account.

When to use it
during an audit of the account, after List Workflows returned the workflow you care about.
Watch out
it works one workflow at a time, so a full audit chains List Workflows and this module in the same scenario.
Adobe Acrobat Sign7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

When none of the listed modules does what you need, this one lets you call any endpoint of the Acrobat Sign API from the scenario, with the connection you already set up. No second login is required.

When to use it
for a task outside the 14 listed modules.
Watch out
you write the request yourself, so keep the Acrobat Sign API documentation open next to the module.
Adobe Acrobat Sign8

Update an Agreement Status

Action

In Make“Updates an agreement status.”

You change the status of an existing agreement from the scenario, which keeps Acrobat Sign in line with a decision made in another tool.

When to use it
when a deal falls through in your CRM and the matching agreement must follow.
Watch out
if Watch Events listens to the same agreements, the update may count as a new event and restart the scenario; check it with Run once first.
Adobe Acrobat Sign9

List Groups

Search

In Make“Retrieves all the groups in an account.”

You receive every group of the account, one bundle per group, which is the simplest way to keep a list of your teams outside Acrobat Sign.

When to use it
to fill a sheet or feed Get a Group for each group in turn.
Watch out
like any search, it can return zero, one or many bundles, and every module after it runs once per group, which counts operations.
Adobe Acrobat Sign10

List MegaSigns

Search

In Make“Retrieves MegaSign parent agreements for a user.”

This search brings back the MegaSign parent agreements of a user, so you can follow those bulk sendings from a single table.

When to use it
before Get a MegaSign, when the scenario must look at each MegaSign sending in turn.
Watch out
it can return nothing at all; plan what the next modules should do when no bundle comes out.
Adobe Acrobat Sign11

List Web Forms

Search

In Make“Retrieves web forms for a user.”

You see all the web forms of a user at once, each one arriving as its own bundle that the next module can process.

When to use it
to keep an inventory of your web forms, or to send each one to Get a Web Form for its details.
Watch out
the results belong to one user, so check which account the connection uses before you trust the list.
Adobe Acrobat Sign12

List Workflows

Search

In Make“Retrieves workflows for a user.”

This module returns the workflows available to a user, which makes a quick overview possible without clicking through the account settings.

When to use it
when you want to spot duplicate or forgotten workflows in a sheet.
Watch out
each workflow becomes a bundle, and each later module runs once per bundle; a filter right after it keeps the operation count down.
Adobe Acrobat Sign13

Search Agreements

Search

In Make“Searches for agreements.”

You find agreements in the account and get them back as bundles, ready to be checked, copied or updated by the next modules.

When to use it
when the scenario starts from a list of agreements rather than a single event, for example to build a table of pending contracts.
Watch out
a search can return many agreements, so run it once with Run once and read the bundles before you chain an update.
Need help

Need help automating Adobe Acrobat Sign with Make?

A person reads every message.

FAQ

Adobe Acrobat Sign and Make: frequent questions

01Is the Adobe Acrobat Sign Make integration free?
Yes, on the Make side: Adobe Acrobat Sign is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. You still need your own Acrobat Sign subscription, which Adobe prices separately.
02What do you need to connect Adobe Acrobat Sign to Make?
An active Acrobat Sign account with access to API credentials. In Acrobat Sign you create an API application under Account, Adobe Sign API, API Applications, choose the CUSTOMER domain, configure OAuth, select the scopes and copy the Client ID and Client secret. In Make you click Create a connection on any module and paste those two values, or follow the instructions shown on screen. For the instant trigger, create the webhook first, then the connection, as the Make documentation asks.
03Does the Adobe Acrobat Sign trigger in Make react in real time?
Yes. Watch Events is an instant trigger: Acrobat Sign calls Make through a webhook as soon as the chosen event happens, so the scenario does not wait for a scheduled check. It is the only trigger of the app. All the other modules are actions and searches, which run when the scenario reaches them, whether it was started by this webhook, by another app or on a schedule. That is why a scenario built on Watch Events usually needs no schedule on its first module.
04What if an Adobe Acrobat Sign module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Acrobat Sign API with the connection you already have, so you can cover a task that the listed modules do not handle without creating a second login. You write the request yourself, so keep the Acrobat Sign API documentation at hand. The Make documentation for this app also notes that part of its content is AI generated and advises checking important points with Adobe.
05Should you use Make or n8n for Adobe Acrobat Sign?
It depends on the tool your team already runs. Acrobat Sign often has a node in n8n too, so the choice rarely comes down to whether the app exists. In Make you get 14 ready modules, including an instant trigger and a generic API call, and you build visually in the scenario editor. Compare how each tool counts usage and which one your colleagues know before you commit, then test a small scenario in each one.
Same platform

Other docs you might need on this stack.

Browse all integrations