Resources · Make integration

Autentique Make integrationAutomate Autentique with Make.

What if every signed contract filed itself the second the last signer finished? The Autentique Make integration gives you 27 modules, including 4 instant triggers, to act on documents and signatures. This page walks you through the connection, a first scenario and each module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Autentique Make integration do for Autentique?

The Autentique Make integration links your Autentique account to Make so that a signature, a new document or a team change can start an automation on its own. In Make you build a scenario, a chain of modules where each module is one brick: a trigger that listens, an action that does something, or a search that looks things up.

Contracts that go out on their own. When a deal is won in your sales tool, Create a Document builds the contract and sends it to the signers in the same step. If a second decision maker shows up later, Add a Signer puts that person on the existing document.

Signed files that land in the right place. Watch Document Signatures wakes the scenario as soon as a document is signed; Move a Document to a Folder then files it with the client, and Sign a Document can add your company's countersignature.

Tighter control over identity checks. Signatures waiting on biometric verification can be approved or rejected from a scenario, after your own review step, with the two dedicated modules.

What the integration does not do: there is no Make an API Call module for Autentique. The fallback is Make a GraphQL Query, which runs any authorized query you write. The Make doc for this app also warns that it is AI-generated from the vendor documentation, so confirm critical details with Autentique.

Still choosing a tool? The n8n vs Make comparison sets the two side by side, the Make pricing guide explains plans, and the Make training covers scenario building from scratch.

Connect

How do you connect Autentique to Make?

  1. 01

    Copy your API key in Autentique

    Log in to Autentique, open your profile section and click API keys. Copy the key shown on screen. This key is what Make uses to act on your behalf, so keep it somewhere private.

  2. 02

    Add an Autentique module in Make

    In your Make scenario, add any Autentique module and click Create a connection. A connection is your Autentique account linked to Make once, then reused by every Autentique module. Naming it in Connection name is optional but helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied, or follow the instructions Make shows on screen, then save. From now on, Make can list your documents and folders when you fill in a module.

First scenario

Your first scenario: file every signed Autentique document

GoalWhen a document is signed in Autentique, Make fetches it and moves it to the folder you chose.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Search for Autentique and pick Watch Document Signatures.

  2. 02

    Set up the webhook and connection

    Click Create a webhook, then Create a connection and paste your API key. The webhook is the address Autentique calls each time a document is signed.

  3. 03

    Fetch the signed document

    Click the + on the right of the trigger and add Get a Document by ID. Map the document ID the trigger received so Make pulls the full document.

  4. 04

    Move it to a folder

    Add Move a Document to a Folder, map the same document and pick the target folder from the list Make shows once the connection exists.

  5. 05

    Test with Run once

    Click Run once, then sign a test document in Autentique. Open each module to read the bundle it received: a bundle is one item passed along, here one document.

  6. 06

    Switch it on

    When the test looks right, switch the scenario on. Since the trigger is instant, Make waits for Autentique to call the webhook instead of checking on a schedule.

Triggers

What can start an Autentique scenario?

4 modules start a scenario when something happens in Autentique. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Autentique as soon as it happens.

Autentique1Watch Document Events

Watch Document Events

Instant trigger

In MakeTriggers whenever any selected document event registered to your endpoint is triggered.

Watch Document Events gives you one entry point for the document events you tick in the module, so a single scenario can follow a document through several stages without anyone checking the Autentique dashboard.

How it fires
instant. Autentique calls Make through a webhook as soon as a selected event happens.
When to use it
you want one flow that reacts differently depending on what just happened to a document, and you would rather not maintain a scenario per event.
Watch out
tick only the events you act on. Each event that reaches Make starts a run, and every module that runs counts as an operation on your plan.
Autentique2Watch Document Signatures

Watch Document Signatures

Instant trigger

In MakeTriggers whenever a document of the user's active organization is signed.

Watch Document Signatures hands your scenario each document signed inside your active Autentique organization. It is the most direct trigger when all you care about is the signature itself.

How it fires
instant. Autentique notifies Make through a webhook the moment the document is signed.
When to use it
a signed agreement should be filed with the client, announced to the account owner or countersigned by your company.
Watch out
only the organization currently active on your account is covered. If you belong to several, run Get the Current Organization once to see which one the trigger listens to.
Autentique3Watch Member Events

Watch Member Events

Instant trigger

In MakeTriggers whenever any selected member event registered to your endpoint is triggered.

Watch Member Events turns changes on the people side of your Autentique account into a scenario start, for the member events you choose in the module. Documents are not involved here.

How it fires
instant. Autentique pings Make through a webhook as soon as the selected member event takes place.
When to use it
your IT or admin team keeps a record of who has access to which tools and wants Autentique to feed that record without manual updates.
Watch out
the Make doc does not list the member events available, so open the module after connecting and read the choices before planning the rest of the flow.
Autentique4Watch Signature Events

Watch Signature Events

Instant trigger

In MakeTriggers whenever any selected signature event registered to your endpoint is triggered.

Watch Signature Events reacts to the signature events you select, which lets you follow each signer's progress rather than only the finished document.

How it fires
instant. Autentique alerts Make through a webhook as soon as one of those events occurs.
When to use it
a sales rep wants to hear when a specific signer acts, so the follow-up call happens while the deal is still warm.
Watch out
this trigger and Watch Document Signatures can both react to a signature. Decide which one owns that job before building, or you end up with two scenarios doing the same work.
Modules

What can Make do in Autentique?

Autentique gives you 23 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Autentique1

Add a Signer

Action

In MakeAdds a new signer to a document.

Add a Signer puts one more person on a document that already exists, so a late approver joins the signing round without you rebuilding the file.

When to use it
a deal in your CRM gains a second decision maker after the contract has already gone out.
Watch out
the module has to know which document to change, so place Get a Document by ID or a search before it when the previous step does not carry that document.
Autentique2

Approve Pending Biometric Verification

Action

In MakeApproves a signature with pending biometric verification.

Approve Pending Biometric Verification clears a signature that is waiting on a biometric check, letting your process move forward from inside a scenario.

When to use it
a reviewer confirms the signer's identity in another tool, and that confirmation should release the signature in Autentique.
Watch out
approving settles an identity question. Keep a human decision upstream instead of approving every pending signature that reaches the module.
Autentique3

Create a Document

Action

In MakeCreates a document and sends it to its signers.

Create a Document builds a new document in Autentique and sends it to its signers in the same step, which is how a contract leaves your sales tool with no copy and paste.

When to use it
a deal is marked won, or an onboarding form is completed, and the paperwork should follow at once.
Watch out
sending is part of this module. For your first Run once, use your own address as the signer so no client receives a test.
Autentique4

Create a Folder

Action

In MakeCreates a folder.

Create a Folder adds a folder in Autentique, giving each client, project or department its own place for documents from the first day.

When to use it
a new customer is added to your CRM and every future contract for that customer should sit together.
Watch out
if the scenario runs twice for the same customer, you get two folders. Check first with Get a List of Folders when duplicates would bother you.
Autentique5

Create Link to Signature

Action

In MakeCreates a public link to the signature. This link should not be shared with anyone but the signer.

Create Link to Signature produces a public link that opens one signature, so you can deliver it through your own channel instead of the standard Autentique email.

When to use it
your customers answer faster by text message or in a chat tool, and you want the signing link to arrive there.
Watch out
the doc is clear that this link is for the signer only. Never post it in a shared channel, a team sheet or a log.
Autentique6

Delete a Document

Action

In MakeDeletes the document of the specified id.

Delete a Document removes the document whose ID you pass, which keeps your Autentique space free of drafts nobody will sign.

When to use it
a deal is lost or cancelled in your CRM and the contract prepared for it no longer has any reason to exist.
Watch out
treat the deletion as final. Use Run once to check the exact ID the module receives before you switch the scenario on.
Autentique7

Delete a Folder

Action

In MakeDeletes folder by its id.

Delete a Folder removes an Autentique folder by its ID, handy for keeping the folder tree tidy when a project or client relationship ends.

When to use it
a client is archived on your side and the empty folder created for them should go too.
Watch out
the Make doc does not say what happens to documents still inside. Run Get Documents from Folder first and move anything you want to keep.
Autentique8

Delete a Signer

Action

In MakeDeletes a signer from a document.

Delete a Signer takes a person off a document before they sign, so the wrong contact stops receiving requests.

When to use it
your contact at a supplier leaves the company, and their replacement should sign instead.
Watch out
removing someone does not add anyone. Pair it with Add a Signer in the same scenario when the goal is a swap rather than a plain removal.
Autentique9

Get a Document by ID

Action

In MakeRetrieves a document by id.

Get a Document by ID pulls the full details of one document when all you have is its ID, typically the ID a trigger just delivered.

When to use it
right after Watch Document Signatures, to hand the complete document to the next step, whether that is filing, a notification or a CRM update.
Watch out
the module returns exactly one document. To go through many, start from Get a List of Documents instead.
Autentique10

Get a Folder by ID

Action

In MakeRetrieves folder info by id.

Get a Folder by ID returns the information of one folder, so a notification or a report can show a readable folder rather than a bare ID.

When to use it
a message to your team should say which client folder a new signed file went into.
Watch out
you need the folder ID. If you only know its name, run Get a List of Folders and pick it from the results.
Autentique11

Get Authenticated User

Action

In MakeGets the current user of the API.

Get Authenticated User tells you which Autentique user sits behind the API key of the connection, a quick way to confirm who Make is acting as.

When to use it
several colleagues share a Make team and you want to be sure a scenario runs under the expected account.
Watch out
this matters most before Sign a Document, which signs as that same user, so check it once during setup.
Autentique12

Get the Current Organization

Action

In MakeRetrieves the current active organization of the user.

Get the Current Organization returns the organization active on your Autentique account, the one Watch Document Signatures covers.

When to use it
you belong to more than one organization and want the scenario to confirm where it works before it creates or signs anything.
Watch out
it returns only the active one. To see every organization you belong to, use Get a List of Organizations.
Autentique13

Make a GraphQL Query

Action

In MakePerforms an arbitrary authorized GraphQL query.

Make a GraphQL Query runs any authorized GraphQL query you write against Autentique, for the cases the ready-made modules leave out.

When to use it
you need a piece of data or an operation that none of the other Autentique modules offers.
Watch out
this app has no Make an API Call module, so this is your only open door. You write the query yourself, which calls for someone comfortable with GraphQL.
Autentique14

Move a Document to a Folder

Action

In MakeMoves the given document to the specified folder.

Move a Document to a Folder relocates a document to the folder you choose, so signed files stop piling up in one place.

When to use it
a contract has just been signed and belongs in the client folder or in a shared Signed folder your finance team reads.
Watch out
it needs both a document and a folder. Get a List of Folders helps when the target changes from one run to the next.
Autentique15

Reject Pending Biometric Verification

Action

In MakeRejects a signature with pending biometric verification.

Reject Pending Biometric Verification refuses a signature still waiting on its biometric check, closing the case from your scenario rather than by hand.

When to use it
your compliance review in another tool concludes that the person signing is not who they claim to be.
Watch out
the doc does not describe what the signer sees afterwards. Try it on a test signature of your own before using it with customers.
Autentique16

Resend Signatures

Action

In MakeResend the document signatures. This action may cost credits.

Resend Signatures sends the signing requests of a document again, a nudge for people who have not signed yet.

When to use it
a deal's close date is getting near in your CRM and the contract is still waiting on one signer.
Watch out
the doc warns that this action may cost credits. Put it behind a clear condition rather than on every document your search returns.
Autentique17

Sign a Document

Action

In MakeSigns the document using it's ID, as the user that holds the API token.

Sign a Document applies a signature to a document by its ID, in the name of the user who owns the API key.

When to use it
your company countersigns once the client has signed, and that step should no longer wait for someone to log in.
Watch out
the signature belongs to the API key owner. Check with Get Authenticated User that the key comes from the person entitled to sign.
Autentique18

Update a Document

Action

In MakeUpdates the given document info.

Update a Document changes the information of an existing document, keeping Autentique in line with what changed elsewhere.

When to use it
a deal is renamed or reassigned in your CRM and the matching document should reflect it.
Watch out
the Make doc does not list which details can be edited. Open the module after connecting and read the fields Make offers before mapping anything.
Autentique19

Get a List of Documents

Search

In MakeRetrieves a list of documents.

Get a List of Documents fetches documents from your account as a search, returning zero, one or several bundles, one per document.

When to use it
you want an overview of your documents in a spreadsheet or a dashboard, or a starting point for bulk updates.
Watch out
every module placed after it runs once per document, and each run counts as an operation on your Make plan.
Autentique20

Get a List of Documents From a Query

Search

In MakeGet a List of Documents From a Query

Get a List of Documents From a Query narrows the document search to what your query describes, instead of pulling everything.

When to use it
you only want a subset, for example the documents tied to one customer, before acting on them.
Watch out
the doc gives no detail on the query format. Test a few queries with Run once and read the bundles before building on the result.
Autentique21

Get a List of Folders

Search

In MakeRetrieves a list of folders.

Get a List of Folders returns your Autentique folders as separate bundles, which is how you find the ID another module expects.

When to use it
just before Move a Document to a Folder or Create a Folder, to find the right target or avoid a duplicate.
Watch out
as a search, it can return several folders, and the next module then runs once for each of them.
Autentique22

Get a List of Organizations

Search

In MakeRetrieves a list of the user's organizations.

Get a List of Organizations lists every organization your Autentique user belongs to, each as its own bundle.

When to use it
an agency or a group works across several Autentique organizations and wants a scenario to report on each one.
Watch out
knowing an organization exists does not make it active. Watch Document Signatures still covers only the active one.
Autentique23

Get Documents from Folder

Search

In MakeLists documents from a folder.

Get Documents from Folder lists the documents stored in one folder, so a scenario can act on a whole client file at once.

When to use it
before deleting a folder, or when you want to resend pending requests for one client only.
Watch out
each document comes out as its own bundle. A large folder therefore means many operations for every module that follows.
Need help

Need help automating Autentique with Make?

A person reads every message.

FAQ

Autentique and Make: common questions

01Is the Autentique Make integration free?
Yes on the Make side: Autentique is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Since all four Autentique triggers are instant, the scheduling interval matters less here. Paid plans lower the interval to one minute and remove the cap on active scenarios. Autentique itself is a separate subscription, described on the Autentique pricing page. Note too that the doc warns Resend Signatures may cost credits.
02What do you need to connect Autentique to Make?
An active Autentique account and an API key. In Autentique, open your profile section, click API keys and copy the key shown. In Make, add any Autentique module, click Create a connection, optionally name it, and paste the key. For one of the four instant triggers, click Create a webhook first, then Create a connection. After that, every Autentique module in your scenarios reuses the same connection, so you only do this once per account.
03Does the Autentique Make integration react in real time?
Yes. All four Autentique triggers are instant: Watch Document Events, Watch Document Signatures, Watch Member Events and Watch Signature Events. Autentique calls Make through a webhook as soon as the event happens, so the scenario does not wait for a scheduled check. That is also why each of these triggers asks you to create a webhook before the connection. Once the scenario is switched on, there is no interval to tune for these triggers: the timing depends on Autentique sending the event.
04What if an Autentique module is missing in Make?
It depends on what you need. Autentique has no Make an API Call module, but Make a GraphQL Query runs any authorized GraphQL query, which can fill a gap if someone on the team can write one. Keep in mind that the Make documentation for this app is AI-generated from the vendor docs and may contain mistakes, so check important details with Autentique. If the query route feels too technical, the team behind this page can help you set it up.
05Should you use Make or n8n for Autentique?
It depends on your criteria. On Make, Autentique comes with 27 ready-made modules, four of them instant triggers, and runs from the Free plan. Many apps also have an n8n node, so check whether one exists for Autentique and what it covers before deciding. Compare the modules you actually need, who will maintain the scenarios and how your team already works; the comparison page linked above lays out the differences between the two tools.