Integration
Formfeed for Power Automate
A new row in a SharePoint list, an approved request, a closed opportunity in Dynamics: the Formfeed connector turns it into an invoice, a certificate or a report, and the next action attaches the file to an Outlook mail or saves it to OneDrive.
Certified by Microsoft and available since October 2026 as a premium connector, marked Preview like every newly certified one: search for Formfeed when you add an action. Where it is not offered, the HTTP action makes the same call.
Free plan with 100 units a month, no credit card
Actions and trigger
- Create a document. Pick a template and its fields appear in the designer, from its data schema or its sample data. Returns the download link, page count and units.
- Create a document file. The same render, returning the file itself: File Content goes straight into an email attachment or a Create file action.
- Create a document from HTML or a web page. For flows that build their own markup, or capture a public page as a PDF or an image.
- Convert a document to PDF. Word, Excel, PowerPoint, OpenDocument or RTF files of up to 20 MB from SharePoint or an email attachment, turned into a PDF and not kept. Starter plan and above.
- Get a render and Get a batch. A render with a fresh download link, or the progress of a batch with its documents and zip.
- When a render or batch finishes. A trigger that starts a flow when a render succeeds or fails, or a batch finishes.
The key stays in the connection
The connection takes a workspace API key once; the connector sends it as a bearer token on every call. The default scopes of a new key cover every action; the trigger also needs webhook:manage, which you tick when you create the key. Use a ff_test_ key while building the flow: its renders are not metered (on the Free plan they carry a small watermark).
Without the connector
Where the connector is not offered, in a region Microsoft has not reached yet or an environment whose data policy blocks it, the HTTP action (a premium action, like the connector itself) makes the same call: POST to https://api.formfeed.dev/v1/renders?output=binary with the header Authorization: Bearer <key> and a JSON body with template and data, and the response body is the file. The documentation has the steps.