Fill PDF forms in Zapier workflows
Connect Emboss to Zapier and fill PDFs from the apps you already use: turn flat forms fillable, fill them from context documents, and send the finished PDF anywhere. Available in the Zapier app directory.
Up and running in five steps.
- 01
Find Emboss in Zapier
In the Zap editor, search for Emboss in the app picker. It's in the public app directory, so it's there for everyone: no invite needed.
- 02
Connect Emboss with your API key
Create an Emboss account, copy an API key from the dashboard, and paste it when Zapier asks you to connect. One connection covers all your Zaps.
- 03
Choose an action in your Zap
Add an Emboss step and pick Create Fillable Form, Fill From PDF + Context, or Fill Existing Form, whichever your Zap needs.
- 04
Map the file from your trigger
Point the File field at the actual file from your trigger (the file URL, not the filename), plus any context documents Emboss should read values from.
- 05
Send the filled PDF anywhere
The step returns the finished PDF as a file, ready for the rest of your Zap: attach it to an email, drop it in Drive, send it to your CRM.
Three actions, one connection.
| Action | What it does | What you get back |
|---|---|---|
| Create Fillable Form | Detects the fields in a flat PDF and places real form fields on it | The fillable PDF as a file, plus the form's id for later fills |
| Fill From PDF + Context | Takes a flat PDF and your context documents, detects the fields, and fills them in one pass | The filled PDF as a file |
| Fill Existing Form | Fills a form you've already created with new context documents | The filled PDF as a file |
Zapier specifics.
In the public directory
Emboss is listed in the Zapier app directory, so anyone can connect it from the Zap editor with no invite. It runs against the same production Emboss API as the n8n, Make, and Pipedream integrations.
Map the file, not the filename
When you map your trigger's output into the File field, pick the file itself (the file URL) rather than the filename text. It's the most common setup mistake: Zapier shows both, and only the file works.
Questions, answered.
How do I get started?
Search for Emboss in the Zap editor's app picker, connect it with an API key from your Emboss dashboard, and add an Emboss action to your Zap. One connection covers all your Zaps.
Which apps can I connect it to?
Any of Zapier's apps. A common pattern is a trigger that supplies a PDF or the data to fill one: a new file in Drive or Dropbox, an email attachment, a form response, then an Emboss action, then a step that stores or sends the finished PDF.
How is it priced?
Per operation, with no subscription. Creating a fillable form and filling one are billed separately, in cents, and every account gets a free monthly allowance on jobs of 5 pages or fewer (the form and its documents together), enough to build and test a workflow without paying anything. Current rates are on the pricing page.
How long does processing take?
It scales with page count and how much context Emboss has to read: usually within two minutes for a short form; a long form can take up to half an hour. The integration polls for you and resumes when the PDF is ready, so you never write timing logic.
What are the file limits?
The form must be a PDF up to 10 MB and 100 pages. You can add up to 5 context files (PDF, Word (DOCX), Excel (XLSX), CSV, JSON, plain text or Markdown, or an image (PNG, JPG, TIFF or BMP)), each up to 10 MB, with 30 MB for the form and its documents together.
Fill your first form in five minutes.
Free to start on forms of 5 pages or fewer, counting your documents. No card, no subscription. Pay per call when you're ready to scale.