Fill PDF forms in Make scenarios
Connect Emboss to Make and fill PDFs inside your scenarios: turn flat forms fillable, fill them from context documents, and pass the finished PDF to the next module. Early access, by invite link.
Up and running in five steps.
- 01
Add the Emboss app
In Make, add the Emboss app and create a connection with an API key from your Emboss dashboard. One connection covers every module.
- 02
Pick a module
Add an Emboss module: Create Fillable Form, Fill From PDF + Context, or Fill Existing Form. For existing forms, a built-in picker lists the forms on your account.
- 03
Map the PDF and context
Point the module at a PDF from an earlier step — a Drive download, an email attachment, an HTTP response — and add any context as text or a file for Emboss to read values from.
- 04
Get the filled PDF back
The module submits the job, waits for it to finish, and returns the finished PDF in the same step: no webhooks, no callback URLs, no second scenario. Map it straight into the next module.
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 binary file, plus the form's id for later fills |
| Fill From PDF + Context | Takes a flat PDF and your context, detects the fields, and fills them in one pass | The filled PDF as a binary file |
| Fill Existing Form | Fills a form you've already created, picked from the built-in form list, using new context | The filled PDF as a binary file |
Make specifics.
One module, no webhooks
Each Emboss module runs in a single step: it submits the job, waits for Emboss to finish, and returns the result in the same execution. There is nothing to configure, with no callback URLs and no second scenario.
Context as text or a file
Provide context as typed text or as a document, whichever you have. If you supply both, the file is used.
A universal module too
Alongside the three actions, a universal “Make an API Call” module lets you call any Emboss endpoint when you need something the actions don't cover.
Questions, answered.
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, 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, from seconds for a short form to a few minutes for a long, context-heavy one. 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 attach up to 5 context files — PDF, DOCX, XLSX, images, or plain text — with 30 MB total across them.
Do I need a paid Make plan?
Adding the Emboss app is free. Running a custom app inside a scenario requires a qualifying Make plan, the same as any custom app on Make.
Where does the filled PDF go?
It comes back as a binary file on the module's output, so any downstream Make module that accepts a file — Drive upload, email attachment, HTTP request — can use it directly.
Fill your first form in five minutes.
Free to start. No card, no subscription — pay per call when you're ready to scale.