PDF documents from Power Automate

Add a plain HTTP action (the built-in one, not a connector) with these settings:

Method  : POST
URI     : https://morfee.furo.solutions/api/render?format=url
Headers : {
            "X-Api-Key": "mrf_your_key_here",
            "Content-Type": "application/json"
          }
Body    : {
            "templateId": "quote-a3f9c1",
            "data": @{outputs('Compose_the_data')}
          }

Make the key on API keys once your account exists; a key belongs to one organization and reaches nothing outside it. Put the template id in a variable at the top of the flow rather than typing it into every action that needs it: when you copy a template to make a new version, the id changes, and then there is exactly one place to update.

?format=url is the setting that matters most in Power Automate. Without it, the response body is the raw PDF bytes, and dragging binary content through a flow is where most Power Automate PDF attempts go wrong: every action after it has to know it is carrying bytes and not JSON, and the run history becomes unreadable. With it, the response is a small JSON object and the bytes stay out of your flow entirely until the one action that actually needs them.

With ?format=url the HTTP action's body is:

{
  "url": "https://morfee.furo.solutions/api/download/1f9b2c4a-...",
  "filename": "quote-a3f9c1.pdf",
  "bytes": 48213
}

That link is valid for an hour and needs no key, which is exactly what an email attachment or a "Create file" action wants. Two ways to use it:

• Attach it to an email. Add a second HTTP action, method GET, URI @{body('HTTP')?['url']}. Its output is the file content; use that as the attachment content on Send an email (V2), with @{body('HTTP')?['filename']} as the name.
• Save it to SharePoint or OneDrive. Same second HTTP action, then Create file with the file content set to that action's body and the file name to filename from the first response.

Skip ?format=url only when you already know the flow will not touch the bytes more than once, for example a single "Create file" straight after the render. Then the first HTTP action's raw body is the file content and the second call is not needed.

Power Automate retries a failed HTTP action on its own, with the default retry policy or one you set. A render that succeeded but whose response got lost on the way back would otherwise be repeated, which means a second document and a second one counted against your plan. Send an Idempotency-Key header with a value that is unique to this run and stable across its retries, for example the flow run id combined with the action name:

Headers : {
            "X-Api-Key": "mrf_your_key_here",
            "Content-Type": "application/json",
            "Idempotency-Key": "@{workflow().run.name}-render-quote"
          }

Send the same key again for the same request and Morfee hands back the same answer instead of rendering twice. Send it again for a request that is not the same, and you get back idempotency_key_reused instead of a silently wrong document, which is the failure you want: loud, not quiet.