Skip to content
Build a Doc
Home Documentation Support
This documentation is currently in preview, therefore subject to change.

Integrate with SharePoint

Build a Doc integrates seamlessly with SharePoint through Power Automate, enabling automated document generation workflows.

SharePoint Integration

This is an overview of integrating Build a Doc with SharePoint.

Storing Templates in SharePoint

Store your document templates in a SharePoint document library:

  1. Create a dedicated folder for templates (e.g., /Templates/)
  2. Upload your Word, Excel, or HTML templates
  3. Reference templates using “Get file content” action

Benefits:

  • Version control through SharePoint
  • Centralised template management
  • Easy template updates without modifying flows

Triggering from SharePoint

Use SharePoint triggers to start document generation:

TriggerUse Case
When an item is createdNew record processing
When an item is modifiedStatus change handling
When a file is createdFile-based workflows

Saving Output to SharePoint

Save generated documents back to SharePoint:

  1. Add SharePoint: Create file action
  2. Configure:
    • Site Address: Your SharePoint site
    • Folder Path: Destination folder
    • File Name: Dynamic name with extension
    • File Content: Build a Doc output

Updating SharePoint List Items

After generating a document, update the source item:

  1. Add SharePoint: Update item action
  2. Set fields like:
    • Document Generated: Yes
    • Document Link: Link to the created file
    • Generated Date: Current timestamp

Example: SharePoint-Triggered Invoice Generation

Trigger: When an item is created (Orders list)
│
├── Get file content (Invoice template from SharePoint)
│
├── Build a Doc: Convert Word Document
│   - Document: Template content
│   - Data source: SharePoint item data
│   - Output Format: PDF
│
├── Create file in SharePoint (Invoices folder)
│
├── Update item (Set DocumentGenerated = Yes)
│
└── Post message in Teams (Notify sales channel)

Example: Job Application Scenario

Based on the SharePoint recruitment scenario:

  1. HR updates applicant status in SharePoint list
  2. Flow triggers on modification
  3. Based on status, select appropriate template (offer/rejection)
  4. Generate personalised letter with applicant data
  5. Save to SharePoint
  6. Email to applicant

Best Practices

Template Management

  • Use a dedicated template library
  • Implement version naming (Template_v1.docx)
  • Test templates before production use

File Organisation

  • Create logical folder structures
  • Use dynamic subfolder paths (by year/month)
  • Include dates in filenames for uniqueness

Performance

  • Consider file size limits
  • Use site-relative paths where possible
  • Handle large volumes with batching