Integration
Formfeed for Zapier
A form submission, a new row, a closed deal: whatever starts the Zap, the Formfeed action turns it into a document. Fields come from your template schema, so you map named fields instead of pasting JSON.
Listed in Zapier’s app directory, with ready-made Zap templates for six apps: search for Formfeed when you add a step to a Zap.
Free plan with 100 units a month, no credit card
Actions and trigger
- Create Document. Pick a template, map its fields, and get the download URL, page count and units back. The list shows the workspace’s templates, up to 100, unpublished ones included; only a published template renders. PDF, an image template’s PNG, JPG or WebP, or DOCX, PPTX or PDF from a Word or PowerPoint template.
- Create Document From HTML. Send HTML from an earlier step when you have no stored template, in Jinja2, Liquid or Handlebars.
- Create Document From URL. Capture a public web page as a PDF or a screenshot.
- Upload File. Put a logo or PDF from an earlier step into the file library, where templates use it by name.
- Convert Document to PDF. Turn a Word, Excel, PowerPoint, OpenDocument or RTF file from an earlier step (up to 20 MB, not kept), or the render of a Word or PowerPoint template, into a PDF. Starter plan and above.
- Create E-Invoice. A ZUGFeRD / Factur-X invoice from the fields of the invoice, its lines as line items, printed by your template and validated before the Zap receives it. Live e-invoices from the Starter plan; a test key makes up to 20 a day on the Free plan, each with the test mark. Create Document with a template that declares an e-invoice works too, with the block in Data (JSON).
- Render Completed. A trigger for finished or failed renders and batches and for quota warnings, from Zaps, the app and the API alike, of live and test keys.
Example Zaps
Most of these are published Zap templates: start one from Zapier’s directory or from the Integrations page in the app, connect the two accounts, pick your template. No app in them is a premium app; Zapier’s free plan runs Zaps of one trigger and one action, so the brand-asset and alert Zaps run on it, and the three with a third step need a paid Zapier plan. The step-by-step setup, with every field, is in the documentation.
- Certificates. Google Forms or Typeform response → Formfeed Create Document → Gmail sends the PDF as an attachment.
- Invoices. New row in Google Sheets → Formfeed Create Document with the line items as JSON → Google Drive stores the PDF.
- Reports. Weekly schedule → Formfeed Create Document From HTML → the PDF link goes out by email.
- Brand assets. New file in a Drive folder → Formfeed Upload File → every template shows the new logo.
- Alerts. Formfeed Render Completed on failed renders → Slack posts the error.
Keys and quota
The connection takes an API key bound to one workspace. The default scopes of a new key cover the connection test, the template list and every action that renders; tick file:write for Upload File and webhook:manage for the trigger. Use a test key while building the Zap: its renders are not metered (on the Free plan they carry a small watermark). Switch to a live key when it goes on.