Integration
Formfeed for Make
Make scenarios are where documents usually get stuck. The Formfeed modules take a template and mapped fields and hand back a URL, a file for the next module, or a batch that ends in a zip.
Built and in Make’s review: until Make approves it, the app is not in Make’s list of apps. Until then, the HTTP module makes the same call. The changelog says when the app is listed.
Free plan with 100 units a month, no credit card
Modules
- Create a document. Pick a template and its fields appear, line items included; returns the download URL, page count and units.
- Create a document from HTML or a URL. For scenarios that build markup earlier in the flow, or capture a public page.
- Create a batch. An Array aggregator turns rows from an earlier module into up to 1,000 documents and one zip.
- Convert a document to PDF. A Word, Excel, PowerPoint, OpenDocument or RTF file from an earlier module (up to 20 MB, not kept), or the render of a Word or PowerPoint template, as a PDF. Starter plan and above.
- Watch events. Fires when a render or a batch finishes or fails, or when the workspace nears or reaches its quota.
- And the rest. Get a render, Get a batch, Upload a file, List files and Delete a file, plus Make an API call for any other endpoint, such as merging PDFs.
Files, not just links
The render module can hand the document to the next module as a file, so uploading to Dropbox or attaching it to an email needs no extra HTTP step.
Until the app is listed
The HTTP module works today: one POST to https://api.formfeed.dev/v1/renders with the header Authorization: Bearer <key> and a JSON body with template and data. The response contains download_url, which a second HTTP module (Get a file) turns into a file. The documentation has the steps and every module.