Integration
Formfeed for Pipedream
Pipedream workflows mix code and prebuilt steps, and documents are where a prebuilt step saves the most code. The Formfeed actions render a template with its fields as props and put the file in the File Stash for the next step.
Built; waiting for Pipedream to add the app to its registry, and the components cannot be used in Pipedream before that. Until then, a Node.js step makes the same call.
Free plan with 100 units a month, no credit card
Actions and sources
- Create Document. A template with one prop per field of its schema, saved to
/tmpfor the next step. - Create Document From HTML and From URL. Markup built earlier in the workflow, or a public page.
- Convert Document to PDF. A Word, Excel, PowerPoint, OpenDocument or RTF file by URL or
/tmppath, or the render of a Word or PowerPoint template, turned into a PDF. Starter plan and above. - Get Render and Upload File. A render with a fresh download URL; a logo or PDF into the file library, where templates use it by name.
- New Render Completed, New Render Failed, New Batch Finished. Instant sources that register a webhook endpoint and check every delivery’s signature.
Until the app is listed
A Node.js step with @formfeed/sdk or a plain fetch does the same today; the API key goes into an environment variable. The documentation has the step.