FillFaster

FillFaster turns a PDF into a fillable, signable web form. Agents create prefilled links per recipient, track what happens to them, fetch the signed PDF, fill a PDF outright with no signing step, and react to form events.

1 trigger 13 actions API key available

FillFaster website Platform Documentation Capability data verified 2026-08-13

The renewal window opens for a cohort of accounts

Agent reads each account's terms, dates and figures out of the CRM

Get Form Fields returns the field names on the renewal form, so the prefill map is built against the real template rather than an assumed one

Generate PDF fills one account's form on the server and returns the document, with no link created and nobody emailed

Agent posts that filled sample to the renewals owner next to the source record it came from

The owner confirms the mapping is right, and only then does Create Submissions In Bulk issue the personalized links

What This Integration Enables

FillFaster's premise is narrow and useful: take a PDF you already use, make it a fillable and signable web form, then hand each recipient a link with their details already in it. There is no document library to manage and no signing ceremony to configure. You build the form once and the API's job is producing links, one per person, with the right values in the right boxes.

That narrowness is what makes it an unusually clean target for an agent. FlowRunner agents read a form's field names before they build a prefill map, create a single link or up to twenty in one call, set an expiry and an access code on a link that would otherwise stay open indefinitely, watch whether a recipient has opened it, pull the signed PDF back into file storage, and, when nothing needs signing at all, fill the PDF server side and return the file. That last operation matters more than it looks, because it is the only way to see what a recipient would see without creating anything a recipient can open. FlowRunner's human-in-the-loop design uses it as the proof step, so the person approving a batch is looking at a real rendered document rather than at a field map.

Without FlowRunner

Every agreement retyped Someone copies names, dates and figures from a record into a PDF, one account at a time

Mapping errors found by the customer A misaligned field is discovered when a client asks why their agreement shows someone else's number

Links live forever by default A signing link with no expiry set stays open long after the deal it belonged to closed

With FlowRunner

Prefill comes from the record Values are pulled from the system that already holds them, keyed to the form's actual field names

Mapping proved before it ships One filled document is rendered and read by a person before any link reaches a recipient

Links carry deliberate limits Expiry, note and access code are set on the submission rather than left at whatever the default was

Use Case Scenarios

A renewal season issued as one reviewed batch

Renewal dates come due for a cohort of accounts in HubSpot. The agent calls Get Form Fields on the renewal form so it maps to the names the form actually defines, assembles one entry per account, and calls Generate PDF for a single representative account. That document is filled and returned with no link created and nobody contacted. The renewals owner reads it, confirms the term dates and the pricing landed in the right boxes, and approves. Create Submissions In Bulk then issues up to twenty personalized links in one call, and because a whole call can succeed while individual entries fail, the agent checks each result and reports the ones that did not go out.
Fill and return, with nobody signing anything

An internal request needs a completed form rather than a signature: a benefits summary, a service record, a certificate. The agent reads the source row, calls Generate PDF, and files the returned document into Google Drive against the record it belongs to. No link exists, so there is nothing to expire and nothing for anybody to open. This is the shape most teams reach for once they realize how much of their signing traffic never actually needed a signature.
Chasing what stalled, not everything

A daily sweep calls List Submissions and Get Submission Status to separate the links nobody has opened from the ones opened and abandoned mid form. Those are two different problems and they get two different responses: the unopened ones get a resend through the channel the customer actually uses, the abandoned ones get a person. The agent posts the short list into Slack for the account owner, and where a link is close to lapsing it calls Update Submission to extend the expiry rather than starting the whole agreement over.

Human-in-Loop Highlight

Create Submission and Create Submissions In Bulk are the operations with no undo here, and the reason is in the parameter list rather than the verb. Supplying a recipient email address emails that person the link immediately. In the bulk call, every entry that carries an email address goes out to that person, and the call can report overall success while individual entries failed, so a batch is never uniformly delivered or uniformly held. There is no recall. What lands in twenty inboxes is an agreement carrying figures the agent mapped from a database, and a prefill map that is wrong is wrong quietly: each recipient sees a well formed, professional document with the wrong number in it.

So the gate sits one step earlier, and it uses an operation the connector already provides for exactly this. Generate PDF fills the form server side and returns the document with no link and no email. The agent renders one, posts it, and asks: "This is the renewal agreement as account Meridian Logistics would receive it. Term dates 01 Oct to 30 Sep, annual value shown as 48,000, contact shown as their AP address. Correct to issue the other 19 on this mapping?" A person reads the document, not the mapping. Then the batch goes. The agent did the reading, the mapping, the rendering and the chasing. Sending a contract to twenty customers stayed a decision.

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

13 actions

Forms

List Forms Lists the form templates on the account, 25 to a page. Used to resolve a form by name before anything is built against it.
Get Form Fields Reads the fields on a form so a flow knows which names it can prefill. Called before building a prefill map rather than after a mismatch shows up.
Get Form Settings Reads a form's settings, including the webhook URLs currently subscribed to it.
Update Form Settings Changes a form's settings, touching only the fields supplied. Webhook subscriptions are deliberately left alone here, so those are changed through Subscribe To Form Events instead.

Submissions and Links

Create Submission Creates a signing link for one recipient, optionally with fields already filled in. Supplying a recipient email address emails them the link straight away, which is why this operation sits behind the gate on this page.
Create Submissions In Bulk Creates up to 20 signing links in one call. Each entry carrying a recipient email is sent to that person, and the call can succeed overall while individual entries fail, so a flow checks every result rather than trusting the status.
List Submissions Lists the submissions on a form, 25 to a page. The read behind reporting and chase sweeps.
Get Submission Status Reads where a submission has reached: not opened yet, opened, or submitted. The distinction between the first two is what separates a delivery problem from an attention problem.
Update Submission Changes a submission's expiry, note or access code, touching only what is supplied. Used to put a deliberate limit on a link, or to extend one rather than reissue the agreement.

Documents

Generate PDF Fills a form on the server and returns the PDF straight away, with no signing step and no link for anyone to open. The proof step behind this page's human gate, and the whole workflow when nothing actually needs signing.
Download Submission PDF Downloads the signed PDF for a completed submission into FlowRunner file storage, so it can be filed against the record it belongs to.

Event Subscriptions

Subscribe To Form Events Registers a URL to be called when something happens on a form. FillFaster refuses a URL already subscribed to that form.
Unsubscribe From Form Events Removes a webhook URL from a form. Flows should leave alone any subscription FlowRunner registered while its trigger is enabled.

Triggers

1 triggers

Event Triggers

On Form Event Fires when someone opens, saves or submits a form. It watches one form template, so a workspace covering several forms adds a trigger for each one it cares about. The submitted event is what starts the file-and-record half of most flows here, since that is the moment a signed PDF exists to download.

Frequently Asked Questions

What can FlowRunner do with FillFaster?

FlowRunner agents can run List Forms, Get Form Fields, and Get Form Settings in FillFaster, plus 10 more actions.

Does connecting FillFaster to FlowRunner require OAuth?

No. FillFaster connects to FlowRunner with an API key, no OAuth flow required.

Can FillFaster trigger a FlowRunner workflow automatically?

Yes. FillFaster supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with FillFaster

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us