Power Automate recipes

Each recipe below is one Power Automate cloud flow: a Microsoft trigger, the AutomaDoc steps that make the document, and a Microsoft step that delivers it. They assume the AutomaDoc connector is already added with a connection; if not, see Power Automate and Power Apps.

All three use the same two AutomaDoc actions:

Action	What you fill in	What it gives the next steps
Generate a document	Template (picked from a list), then one input per placeholder of that template, and Output Format (pdf, png or native; empty means the template’s setting)	Document ID, File Name, Status, Download URL, Warnings
Download document	Document ID ← Document ID from Generate a document	File Content

Generate a document waits until the document is ready, and fails with the reason when it cannot be made. File Name Pattern and Record ID are under its advanced parameters.

What counts against your allowance

Each Generate a document that completes is one automated document. On Pro there is no limit; otherwise it comes out of your Business seats’ automated documents (20,000 a year per seat), then the free monthly allowance, then your document packs. A document that fails is not counted, and nothing is counted for a run that never reaches the step. Inside an Apply to each, every pass is a document of its own.

When an approval completes

Ask someone to approve a request, and make the document only when they approve it: a purchase order, a leave certificate, a signed-off quotation.

Trigger. Whatever starts the request. For a request filed in a SharePoint list, use SharePoint → When an item is created; to start it by hand, use Manually trigger a flow with the inputs you need.

Steps.

1. Approvals → Start and wait for an approval.
   • Approval type: Approve/Reject - First to respond.
   • Title, Assigned to and Details: from the trigger, for example Title and the approver’s email address.
2. Control → Condition: Outcome (from Start and wait for an approval) is equal to Approve.
3. In the True branch, AutomaDoc → Generate a document:
   • Template: your purchase order template.
   • Map the template’s inputs from the trigger’s dynamic content (Title, Amount, Supplier and so on), and the approval’s from Start and wait for an approval: Outcome, Response summary, Completion date.
   • Output Format: pdf.
4. AutomaDoc → Download document with Document ID ← Document ID.
5. Deliver it, either or both:
   • Office 365 Outlook → Send an email (V2): To the requester; under Attachments, Attachments Name ← File Name and Attachments Content ← File Content.
   • SharePoint → Create file: Site Address and Folder Path of your library, File Name ← File Name, File Content ← File Content.

Dynamic content to map.

Template input	Dynamic content
Request	Title (trigger)
Amount, Supplier	the request’s own columns (trigger)
Decision	Outcome
Approval_note	Response summary
Approved_on	Completion date

Responses Approver name and Responses Comments come from a list with one entry per approver, so Power Automate puts the step inside an Apply to each when you use them, which makes one document per approver. To keep one document per request, use Response summary instead.

What counts. One document per approved request. A rejected request ends in the False branch and costs nothing.

When a Microsoft Forms response arrives

Turn each form response into a document and send it back to the person who answered: a registration confirmation, a quote request, an inspection report.

Trigger. Microsoft Forms → When a new response is submitted, with your form in Form Id.

Steps.

1. Microsoft Forms → Get response details: the same Form Id, and Response Id ← Response Id from the trigger.
2. AutomaDoc → Generate a document:
   • Template: your confirmation template.
   • Map each input from Get response details: every question appears as dynamic content under its own title.
   • Output Format: pdf.
3. AutomaDoc → Download document with Document ID ← Document ID.
4. Office 365 Outlook → Send an email (V2): To ← Responders' Email; Attachments Name ← File Name, Attachments Content ← File Content.

Dynamic content to map.

Template input	Dynamic content (Get response details)
Name, Company, Date	the questions of the same name
Email	Responders' Email
Submitted	Submission time

• Responders' Email is filled only when the form records who answered (a form for people in your organization). For a form anyone can answer, add a question that asks for an email address and send to that answer instead.
• A question that allows several answers gives them as one text in brackets, such as ["Red","Blue"], and the template prints it that way. To print Red, Blue instead, fill the input with the expression join(json(<the answer>), ', ').
• A file uploaded through the form is stored in OneDrive or SharePoint behind a sign-in, so it cannot fill a picture placeholder: picture inputs must be public web addresses (https://, or http://).

What counts. One document per response.

When a SharePoint item is created

Make a document from a new list item’s columns, then keep it next to the item: in a document library, or as an attachment of the item itself.

Trigger. SharePoint → When an item is created, with your Site Address and List Name.

Steps.

1. AutomaDoc → Generate a document:
   • Template: your template.
   • Map each input from the trigger’s columns.
   • Output Format: pdf.
2. AutomaDoc → Download document with Document ID ← Document ID.
3. Keep the file, one of:
   • SharePoint → Create file: Site Address, Folder Path (for example /Shared Documents/Contracts), File Name ← File Name, File Content ← File Content.
   • SharePoint → Add attachment: the same Site Address and List Name as the trigger, Id ← ID from the trigger, File Name ← File Name, File Content ← File Content.

Dynamic content to map.

Column type	Dynamic content to use
Text, number, date	the column itself
Choice	Column Value
Person	Column DisplayName (or Email)
Lookup	Column Value

Map the trigger’s ID to Record ID, under the advanced parameters of Generate a document, so {Record_ID} prints the item’s number.

• Use When an item is created, not When an item is created or modified: adding the attachment modifies the item, which would start the flow again.
• Importing many items at once starts one flow per item. Over 60 requests a minute for one template, the step answers 429 and Power Automate’s retry policy tries again.
• To make one document from many items (a statement, a list, labels), see One document from many rows.

What counts. One document per new item.