Resources · Make integration

pdfFiller Make integrationAutomate pdfFiller with Make.

What happens to a PDF once it is signed or filled? The pdfFiller Make integration answers that with 26 modules: one instant trigger, 20 actions and 5 searches. This page shows ops and sales teams how to plug their account in and build a first scenario without writing code.

Try the pdfFiller integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the pdfFiller Make integration automate?

The pdfFiller Make integration links your pdfFiller account to Make so that forms, signature requests and documents move on their own. You build a scenario, which is the automation itself: a chain of modules, each module being one brick such as a trigger, an action or a search. pdfFiller becomes one link in that chain.

Signed contracts that file themselves. Watch Events fires when a signature request is completed, then Download a Document pulls the signed file and the next module drops it wherever your team keeps contracts. Nobody has to open pdfFiller to check who signed.

Forms that turn into data. A client returns an intake form; Get a Filled Form Data reads what was typed so the answers can land in a spreadsheet or a CRM record. If you already run a base there, the Airtable Make integration page covers the other side.

Paperwork sent from your own tools. Create a Fill Request or Create Signature Requests starts the pdfFiller side when something happens elsewhere, a deal marked as won for instance. Send a Signature Request Reminder then nudges the slow signer.

Know the edges before you start. Create a Template from Template does not support templates that contain radio fields, and Add Signature Request Recipients only applies to a request sent to a group. Anything the 26 modules skip can go through Make an API Call with the same connection.

The same app often has an n8n node as well. If you are weighing both tools, read n8n vs Make, and check Make pricing to see how operations are counted on each plan.

Connect

How do you connect pdfFiller to Make?

  1. 01

    Grab your API credentials

    In pdfFiller, open the Settings panel, then the API Applications or Integrations section. Select an application or create one, and copy the Client ID and the Client secret shown on screen.

  2. 02

    Add a pdfFiller module

    In your Make scenario, add any pdfFiller module and click Create a connection. A connection is your pdfFiller account linked to Make once, then reused by every pdfFiller module you add later.

  3. 03

    Paste and save

    Give the connection a name in Connection name if you run several accounts (the field is optional), paste the credentials you copied, and follow the on-screen instructions until Make confirms the link.

First scenario

Your first scenario: save every filled form as a PDF

GoalWhen someone finishes a fill request in pdfFiller, Make downloads the completed form as a PDF.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Search for pdfFiller and pick Watch Events.

  2. 02

    Create the webhook and connection

    Click Create a webhook, then Create a connection and paste your Client ID and Client secret. From now on pdfFiller calls Make itself whenever an event happens.

  3. 03

    Add Download a Filled Form

    Click the + on the right of the trigger, pick Download a Filled Form and map the filled form ID from the bundle, meaning the item the trigger passed along.

  4. 04

    Test with Run once

    Click Run once, then fill a test form in pdfFiller. Open each module's bubble to read the bundle it received and confirm that the PDF came through.

  5. 05

    Switch it on

    Turn the scenario on. Since Watch Events is instant, there is no interval to set: each finished form starts a run and uses operations, the unit Make counts on your plan.

Triggers

What starts a pdfFiller scenario

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

pdfFiller1Watch Events

Watch Events

Instant trigger

In Make“Triggers by the completion of a fill request, a signature request or a document constructor.”

Watch Events starts your scenario the moment a fill request is completed, a signature request is completed or a document built with the template constructor is finished, so the follow-up work runs without anyone checking pdfFiller by hand.

How it fires
it is an instant trigger. pdfFiller calls Make through a webhook as soon as the event happens, so there is no polling interval to wait for.
When to use it
a signed sales contract should reach the account manager and the client folder as soon as the last person signs.
Watch out
Make asks you to click Create a webhook before Create a connection, so keep your Client ID and Client secret nearby.
Modules

Everything pdfFiller can do in Make

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

pdfFiller1

Add Signature Request Recipients

Action

In Make“Adds additional recipients to a "sendtogroup" signature request by the signature request ID.”

Extra signers join a request that is already out, so you do not cancel it and start again. You point the module at the signature request ID.

When to use it
the buyer adds a second approver after the purchase agreement has already been sent.
Watch out
the module is described for sendtogroup requests only, so check how the original request was sent.
pdfFiller2

Cancel a Fill Request

Action

In Make“Cancels a document fill request by the fill request ID.”

A form you sent out stops accepting answers: this module cancels the fill request by its ID, so nobody keeps working on a version you no longer want.

When to use it
a candidate drops out of a hiring process and the onboarding form should close with the application.
Watch out
place List Fill Requests before it when you do not already hold the ID, so the right request gets cancelled.
pdfFiller3

Cancel a Signature Request

Action

In Make“Cancels a document signature request by the signature request ID.”

Pull a contract back before anyone signs it. Give the module the signature request ID and pdfFiller cancels the request.

When to use it
a deal is marked as lost in your CRM and the pending agreement should not stay open in the client's inbox.
Watch out
cancelling is not editing; to change a clause, cancel here and send a fresh request with Create Signature Requests.
pdfFiller4

Copy a Document

Action

In Make“Copies a document to a destination folder.”

You keep the original untouched and work on a duplicate placed in the folder you choose. Handy when a master file must stay clean.

When to use it
each new client needs their own copy of your standard service agreement in a dedicated folder.
Watch out
the copy lands in a destination folder, so decide on your folder structure in pdfFiller before you map this field.
pdfFiller5

Create a Fill Request

Action

In Make“Creates a new fill request by the template ID.”

Turns a pdfFiller template into a form someone can complete, created from the template ID. This is the starting point of any intake flow.

When to use it
a new tenant is approved and should receive the rental application straight away, without anyone preparing it by hand.
Watch out
the answers come back later; pair this module with Watch Events to react when the form is done.
pdfFiller7

Create a Template from Template

Action

In Make“Creates a new template by filling a template. Template containing radio fields are not supported.”

Produces a new template by filling an existing one, so variations of a master file appear without manual editing. Its Make key is createDocumentFromTemplate.

When to use it
each region needs a version of the price quote form with its own details already filled in.
Watch out
templates that contain radio fields are not supported; swap them for another field type first.
pdfFiller8

Create Signature Requests

Action

In Make“Creates new signature requests from an existing document.”

Sends an existing document out for signature, straight from your scenario. The contract leaves as soon as the deal is ready, not when someone remembers.

When to use it
a quote is accepted in your sales tool and the matching agreement already sits in pdfFiller.
Watch out
the module works from a document that already exists; upload or copy it first if the scenario creates it on the fly.
pdfFiller9

Delete a Document

Action

In Make“Removes a document by the document ID.”

Clears a document out of pdfFiller by its ID, which keeps the account tidy once files have been archived elsewhere.

When to use it
a signed contract has been downloaded and stored in your file system, and the pdfFiller copy is no longer needed.
Watch out
put this module last and test with Run once on a dummy file, because a wrong mapping removes the wrong document.
pdfFiller10

Download a Document

Action

In Make“Downloads a document or a template as a file.”

Gets you the actual file of a document or a template, ready to pass to the next module as a real attachment rather than a link.

When to use it
a finished agreement should be emailed to the client or saved in a shared drive.
Watch out
for completed forms, Download a Filled Form is the module built for that job; this one targets documents and templates.
pdfFiller11

Download a Filled Form

Action

In Make“Downloads a filled form as PDF by the filled form ID.”

The completed form arrives as a PDF you can store, send or attach, fetched with the filled form ID.

When to use it
each patient registration or job application should end up as a PDF in the right folder once the person hits submit.
Watch out
on the Free plan, Make handles files up to 5 MB, so check the size of heavy scanned forms before relying on this step.
pdfFiller12

Download an Additional Document

Action

In Make“Downloads an additional document of a filled form by the filled form ID.”

Retrieves the extra file a person attached to a filled form, such as an ID scan or a certificate, using the filled form ID.

When to use it
a supplier onboarding form asks for proof of insurance and that proof must reach your compliance folder too.
Watch out
the main form and its extra documents are separate downloads, so plan one module for each.
pdfFiller13

Get a Filled Form

Action

In Make“Retrieves a filled form by its ID and the fill request ID.”

Pulls up one filled form so later modules know which submission they are handling. It needs both the form ID and the fill request ID.

When to use it
a scenario follows up on one specific submission and must check it before routing it on.
Watch out
when you only have the fill request ID, run List Filled Forms first to get the form IDs.
pdfFiller14

Get a Filled Form Data

Action

In Make“Retrieves details of a filled form by its ID.”

Reads what the person typed into a filled form so the answers can travel to another app as data, not as a PDF.

When to use it
a client intake form should create a contact in your CRM with the name and details already filled in.
Watch out
run it once with Run once and open the bundle to see which answers come back before you map them.
pdfFiller15

Get a Signature Request

Action

In Make“Retrieves a signature request by the signature request ID.”

Shows where one signature request stands, looked up by its ID, so your scenario can decide what to do next.

When to use it
before sending a reminder, check the request to avoid nudging someone about a contract that is already cancelled.
Watch out
it looks at one request at a time; List Signature Requests covers the broader search.
pdfFiller16

Make an API Call

Action

In Make“Performs an arbitrary authorized API Call.”

Covers what the listed modules leave out: any endpoint of the pdfFiller API can be called from the scenario, with the same connection you already created.

When to use it
you need a pdfFiller feature that the listed modules do not expose.
Watch out
you write the request yourself, so keep the pdfFiller API documentation open and test with Run once.
pdfFiller17

Move a Document

Action

In Make“Moves a document to a destination folder.”

Relocates a document into a destination folder, so your pdfFiller account mirrors the stage each file has reached.

When to use it
once a contract is signed, move it from a pending folder to a completed one.
Watch out
unlike Copy a Document, the file leaves its original folder; pick Copy when the source must stay put.
pdfFiller18

Rename a Document

Action

In Make“Renames a document by the document ID.”

Gives a document a clear name built from your data, so anyone scanning the list finds the right file at a glance.

When to use it
uploaded files arrive with generic names and should carry the client name and a reference instead.
Watch out
the module works by document ID, so map the ID from the module that uploaded or found the file.
pdfFiller19

Send a Signature Request Reminder

Action

In Make“Reminds a recipient about the signature request by the recipient ID.”

Nudges one signer who has not acted yet, targeted by the recipient ID, without you writing a follow-up email.

When to use it
a lease is waiting on one co-signer and your scenario spots it with Get a Signature Request.
Watch out
the reminder goes to a recipient, not to the whole request; List Signature Request Recipients gives you the IDs.
pdfFiller20

Upload a Document

Action

In Make“Uploads a document by its URL or file.”

Brings a file into pdfFiller, either from a URL or from a file passed by an earlier module, so it can be signed, filled or stored there.

When to use it
invoices generated in your billing tool should land in pdfFiller ready for signature.
Watch out
on the Free plan, Make caps files at 5 MB, and each upload counts as one operation.
pdfFiller21

List Documents

Search

In Make“Searches documents by criteria.”

Finds documents that match your criteria and returns each as its own bundle, which later modules process one after the other.

When to use it
a cleanup scenario gathers the files to archive before moving or deleting them.
Watch out
a search can return zero, one or many results, and each result consumes operations further down.
pdfFiller22

List Filled Forms

Search

In Make“Lists all filled forms by the fill request ID.”

Brings back every filled form tied to one fill request, so you see all submissions for the same form together.

When to use it
an event registration form went to many attendees and you want each answer sheet in one pass.
Watch out
it needs the fill request ID; List Fill Requests can find it when you only know the form by criteria.
pdfFiller23

List Fill Requests

Search

In Make“Searches document fill requests by criteria.”

Searches the forms you sent out for filling and returns the matching requests, handy when the ID is not in your scenario yet.

When to use it
before cancelling or checking a form, locate the right request from its criteria.
Watch out
several requests may match, so add a filter between modules when only one should continue.
pdfFiller24

List Signature Request Recipients

Search

In Make“Retrieves a list of signature request recipients by the signature request ID.”

Lays out who is on a signature request, by its ID, with one bundle per recipient that you can route individually.

When to use it
you need recipient IDs to send targeted reminders, or to log every signer in a spreadsheet.
Watch out
each recipient becomes a separate bundle, so the following modules run once per person.
pdfFiller25

List Signature Requests

Search

In Make“Searches document signature requests by criteria.”

Scans your signature requests by criteria and returns the matches, giving you a view across all contracts in play.

When to use it
a follow-up scenario collects every open request to chase or report on them.
Watch out
narrow the criteria, because every match is a bundle and each module after it costs operations per bundle.
Need help

Need help automating pdfFiller with Make?

A person reads every message.

FAQ

pdfFiller and Make: common questions

01Is the pdfFiller Make integration free?
Yes on the Make side. pdfFiller is a standard app, so it works from the Free plan, which gives you 2 active scenarios, runs no closer than every 15 minutes for scheduled scenarios, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow unlimited active scenarios. You still need an active pdfFiller account with API access, and pdfFiller sets its own pricing.
02What do you need to connect pdfFiller to Make?
You need an active pdfFiller account and API credentials. In pdfFiller, open Settings, then API Applications or Integrations, select or create an application, and copy the Client ID and the Client secret. In Make, add a pdfFiller module, click Create a connection, name it if you like, and paste both values. For Watch Events, click Create a webhook first, then Create a connection. The same connection then serves every pdfFiller module in your scenarios.
03Does the pdfFiller trigger in Make react in real time?
Yes. Watch Events is an instant trigger: pdfFiller calls Make through a webhook as soon as a fill request, a signature request or a template constructor document is completed. The scenario does not wait for a polling interval. It is the only trigger of the app, so a scenario that should start from something else, a CRM update for example, begins with a module from that other app and then uses the pdfFiller actions.
04What if a pdfFiller module is missing in Make?
Use Make an API Call. It calls any endpoint of the pdfFiller API from your scenario with the connection you already have, so you are not limited to the 26 listed modules. Two known gaps are worth checking first: Create a Template from Template does not support templates with radio fields, and Add Signature Request Recipients only works on group requests. Before writing a raw call, click Run once and read the bundles each module received.
05Make or n8n for pdfFiller?
It depends on what you need to cover. On Make, pdfFiller comes with 26 modules: one instant trigger for completed forms and signatures, 20 actions and 5 searches, plus Make an API Call for the rest. The same app often has an n8n node too, so list the steps your process needs and check that each tool covers them. Pick the one where your whole flow fits without workarounds. The n8n vs Make comparison linked above goes through the general differences.
Same platform

Other docs you might need on this stack.

Browse all integrations