--- title: "pdfFiller Integration" description: "pdfFiller, from airSlate, turns a PDF into something people can complete and sign online. Agents publish fillable links, read submissions back as data, send signature requests, pull the signed copy with its certificate, and organize documents into folders." url: https://flowrunner.ai/integrations/pdffiller date_modified: 2026-09-04T14:07:24-07:00 --- # pdfFiller [Documents](https://flowrunner.ai/integrations/category/documents-forms) pdfFiller, from airSlate, turns a PDF into something people can complete and sign online. Agents publish fillable links, read submissions back as data, send signature requests, pull the signed copy with its certificate, and organize documents into folders. 49 actions · Session · available [pdfFiller website](https://www.pdffiller.com/) · [Platform Documentation](https://github.com/pdffiller) · Capability data verified 2026-08-13 1. A new hire's start date is confirmed in the HR system 2. Agent reads the values it intends to prefill from the employee record 3. Copy Document makes a working copy of the master onboarding pack, leaving the master untouched 4. Get Document Fields lists the fillable fields, so the prefill map is built against the document rather than against an assumption 5. Get Document Previews returns page images, so the flow can see what it is about to distribute without downloading the whole PDF 6. Agent posts the preview and the intended distribution method to the people ops owner 7. The owner confirms whether this goes out as an addressed signature request or as a public link, before either one is created ## What This Integration Enables pdfFiller, from airSlate, is built around one object. Its version 2 API calls that object a template, but it is simply a document on the account, and everything else works from one: you make it fillable as a public link, send it for signature, or read back what people typed. That single object model is what makes pdfFiller the right tool when the job is completion at volume rather than negotiation. It is the connector to reach for when a hundred people need to fill in the same form and you need the answers as data at the end of it. FlowRunner agents upload and copy documents, read a document's fillable fields and its signing roles, turn a document into a public link anybody can complete without an account, read submissions back as structured data in four formats, send addressed signature requests and pull the signed copy with its certificate of completion, merge several documents into one pack, and organize everything into folders. Two practical notes for whoever sets this up. A connection needs application credentials plus an account sign in, so use a dedicated integration account rather than a person's. And the account holds exactly one global callback, so setting it replaces whatever was there, including a callback another tool on the same account depends on. Volume is what makes this connector useful and also what makes it worth gating. A form that reaches a hundred people reaches them all at once, and the same call that addresses a document to one named person can publish it to anybody with a URL. FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design leaves the assembly, the prefilling and the data extraction to the agent, and puts the question of who can open the result in front of a person. ### Without FlowRunner **Forms filled by hand, twice**: Data that already exists in the HR record gets retyped into a PDF, then retyped back out of it **One master document edited in place**: Everyone works from the same file, so a change made for one person survives into the next **Answers arrive as scanned paper**: Completed forms come back as documents, and somebody transcribes them into a system ### With FlowRunner **Forms filled from the record**: Fields are pre-filled from the system that holds them, so the person completes only what is genuinely new **Each run works from a copy**: The master is copied per use and left untouched, so no run can corrupt the source **Answers arrive as data**: Submissions export as JSON, Excel, CSV or HTML and land in a spreadsheet or a database ## Use Case Scenarios ### An onboarding pack assembled, pre-filled, and returned as data A new hire is created in [BambooHR](https://flowrunner.ai/integrations/bamboohr) or [Personio](https://flowrunner.ai/integrations/personio). The agent calls Merge Documents to combine the contract, the policy acknowledgment and the benefits form into a single pack, then Copy Document so this run works from a copy and the master is never touched. Get Document Fields reports the field names, the agent pre-fills the ones the HR record already answers, and the pack goes to the new hire. When it comes back, Export Submission Data returns what they typed as JSON, and the agent writes those values onto the employee record and into [Google Sheets](https://flowrunner.ai/integrations/google-sheets) for the onboarding tracker. Nobody transcribes a PDF. ### One document circulated through roles, in order Some documents need every named party on the same copy rather than each party on their own. The agent calls Get Document Roles to read the signing roles defined on the document, then Send Signature Request using the group method, which circulates a single copy through those roles instead of giving everyone a separate one. List Recipients tracks where each person has reached, and Remind Recipient nudges the one holding it up. When the request completes, the agent pulls both Download Signed Document and Get Signature Certificate, so the executed document and the evidence of who signed it, when and from where are filed together in [SharePoint](https://flowrunner.ai/integrations/sharepoint). ### A public form that stops being public on schedule For an open enrollment window or a company wide acknowledgment, the agent calls Create Fill Request to turn the document into a link anyone can complete without a pdfFiller account. Nobody is emailed; the link comes back for the team to distribute through its own channels. A daily sweep calls List Submissions to see who has completed it and posts the outstanding list into [Slack](https://flowrunner.ai/integrations/slack). When the window closes, Update Fill Request takes the link private rather than deleting it, so the completions already recorded stay readable while the door shuts. ## Human-in-Loop Highlight Create Fill Request is the operation on this connector with a blast radius most teams underestimate. It turns a document into a public link that anyone can open and complete without a pdfFiller account, and it accepts pre-filled fields so each person completes only what is left. Those two features are excellent separately and dangerous together. Every other document connector in this category binds a link to a recipient: an addressed email, a verification code, an access code. A pdfFiller fill request is bound to nobody. If the prefill carries one named employee's salary, address or national identifier, then whoever forwards the URL, and whoever they forward it to, sees it. An agent cannot tell the difference. A field map that prefills employee\_name and annual\_salary looks identical whether it is aimed at an addressed signature request or at an open link, and the call succeeds either way. So the gate sits on the distribution decision, before anything is created. The agent posts the page previews from Get Document Previews with the question: "Onboarding pack ready for 34 people. Prefill map includes name, start date, department and salary band. Send as 34 addressed signature requests, or publish one public fill link with no prefill? A public link with prefilled personal data is readable by anyone who receives the URL." The people ops owner answers, and the agent builds whichever one they chose. Nothing about that decision is technical, which is exactly why it belongs to a person. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 49 actions ### Documents 13 - **List Documents** Lists the documents on the account, newest first by default. pdfFiller calls these templates, and every other operation here takes an identifier one of them returns. - **Get Document** Reads one document's name, page count, folder and timestamps. - **Upload Document** Uploads a PDF from a URL your flow can reach and returns the identifier pdfFiller gives it. The first step of most flows, since everything else works from a document already on the account. - **Update Document** Renames a document or moves it to another folder, changing only what is supplied. - **Copy Document** Makes a copy under a new name, optionally in another folder, leaving the original untouched. This is the safe way to work from a master document, because a run that goes wrong ruins the copy. - **Delete Document** Permanently removes a document from the account. - **Download Document** Downloads a document as it currently stands, with anything filled in, into flow file storage. - **Download Original Document** Downloads the document as it was originally uploaded, before anything was filled in or signed. - **Download Signatures** Downloads the signature images captured on a document, as evidence of who signed it. - **Get Document Fields** Lists the fillable fields on a document with their names and types. This is what tells a flow which field names it may send, and it is read before a prefill map is built rather than after one fails. - **Get Document Roles** Lists the signing roles defined on a document with their identifiers. The group send method needs a role identifier per recipient, and this is where they come from. - **Get Document Previews** Returns preview images of a document's pages, so a flow can show what it is about to send without downloading the whole PDF. The proof step behind this page's human gate. - **List Filled Documents** Lists the completed copies produced from a document, one per person who filled it in. ### Fill Requests 5 - **Create Fill Request** Turns a document into a public link anyone can complete without a pdfFiller account. Nobody is emailed; the link is returned for you to distribute, and fields can be pre-filled. This is the operation the human gate on this page exists for. - **List Fill Requests** Lists the fill requests on the account. A fill request, which pdfFiller calls a LinkToFill, is that public completion link. - **Get Fill Request** Reads one fill request, including the public link people use to complete it. - **Update Fill Request** Changes an existing fill request, altering only what is supplied. This is how a link is taken private without deleting it, so completions already recorded stay readable. - **Delete Fill Request** Removes a fill request, which stops its public link working. ### Submissions 5 - **List Submissions** Lists what people have submitted through a fill request, one entry per completion. - **Get Submission** Reads one submission, including who completed it and when. - **Export Submission Data** Returns what someone typed into a form as data rather than as a PDF, in JSON, Excel, CSV or HTML. The operation that gets form answers into a spreadsheet or a database instead of into a filing cabinet. - **Download Submission** Downloads the completed PDF from one submission into flow file storage. - **Delete Submission** Removes one submission from a fill request. The fill request itself keeps working. ### Signature Requests 7 - **Send Signature Request** Emails a document to one or more people to sign. It sends immediately and cannot be recalled, only deleted. Send To Each gives every recipient their own copy, while Send To Group circulates one copy through the roles defined on the document. - **List Signature Requests** Lists the signature requests sent from the account with their current status. - **Get Signature Request** Reads one request, including each recipient and where they have reached. - **Delete Signature Request** Removes a signature request. This does not recall anything already delivered; it removes the request from the account. - **Get Signature Certificate** Returns the certificate of completion for a request: who signed, when, and from where. This is the evidence a signature actually happened. - **Download Signed Document** Downloads the signed document from a completed request into flow file storage. - **List Signature Inbox** Lists the documents other people have sent to this account for signature, as opposed to the ones it has sent out. ### Recipients 4 - **List Recipients** Lists the recipients on a signature request and where each of them has reached. - **Get Recipient** Reads one recipient of a signature request, including whether they have signed. - **Add Recipients** Adds more people to an existing signature request. They are emailed the same way the original recipients were. - **Remind Recipient** Emails one recipient again about a request they have not finished. This reaches a real person, so a flow checks their status before sending rather than reminding on a fixed schedule. ### Folders 5 - **List Folders** Lists the folders on the account. - **Get Folder** Reads one folder. - **Create Folder** Creates a folder, optionally inside another one. - **Update Folder** Renames a folder or moves it under another one. - **Delete Folder** Removes a folder from the account. ### Callbacks 8 - **List Callbacks** Lists the per-document callbacks registered on the account. - **Get Callback** Reads one callback registration. - **Create Callback** Registers a URL of your own to be called when something finishes on one particular document. - **Update Callback** Changes an existing callback's URL or the event that triggers it. - **Delete Callback** Removes a callback registration, so the URL stops being called. - **Get Global Callback** Reads the account-wide callback, which fires for every document rather than one. Worth reading before writing, because of what the write does. - **Set Global Callback** Sets the account-wide callback. There is exactly one of these, so setting it replaces whatever was there, including a callback another integration on the same account is relying on. - **Delete Global Callback** Removes the account-wide callback. ### Account and Tools 2 - **Get Current User** Reads the account the connection belongs to. Useful as a connection check, since it needs no identifiers of its own. - **Merge Documents** Combines several documents into one new document, in the order given. The operation behind assembling a pack before it is sent or published. ## Frequently Asked Questions ### What can FlowRunner do with pdfFiller? FlowRunner agents can run List Documents, Get Document, and Upload Document in pdfFiller, plus 46 more actions. ### Does connecting pdfFiller to FlowRunner require OAuth? No. pdfFiller connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can pdfFiller trigger a FlowRunner workflow automatically? pdfFiller doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at pdfFiller?** This integration exposes pdfFiller to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/pdffiller. Site index: https://flowrunner.ai/llms.txt