Supported Integration Patterns

Overview

Build a Doc can be integrated into various enterprise workflow patterns through Microsoft Power Platform. The connector architecture and end-to-end flow are outlined in Power Platform Connector Architecture.

Common Patterns

Event-Driven Document Generation

Trigger document generation in response to business events:

SharePoint item created/modified
Dataverse record updated
Teams channel message trigger (flow kicked off from a post)

Scheduled Report Generation

Generate reports on a schedule:

Daily sales summaries
Weekly status reports
Monthly invoices

See the daily recurrence example in Week-to-date Sales Digest where a Recurrence trigger runs every morning to regenerate the digest.

User-Initiated Generation

Allow users to trigger generation manually:

Manual trigger in Power Automate
Power Apps button

For examples, see the starter flows in Build a Power Automate Flow and the Canvas app flow in Power Apps Getting Started.

Batch Processing

Process multiple documents in sequence:

Apply to each loop

The sales digest scenario uses Apply to each to aggregate Dataverse rows before generating documents; see Week-to-date Sales Digest.

Data Source Patterns

Source	Use Case
SharePoint Lists	Structured business data
Dataverse	CRM and business applications
HTTP/API	External services
Excel Online	User-managed data

Data sources are passed to actions as named inputs; see Templates and Data Binding and the examples in the Power Automate and Power Apps quickstarts.

Output Patterns

Destination	Use Case
SharePoint	Document management, collaboration
OneDrive	Personal storage
Email Attachment	Direct delivery
Teams	Collaboration notification

SharePoint/OneDrive outputs are demonstrated in Build a Power Automate Flow and Week-to-date Sales Digest.
Teams notification is demonstrated in Integrate with Microsoft Teams.
Email delivery with HTML and embedded chart is demonstrated in Week-to-date Sales Digest.