Use Case

Power Automate PDF Conversion

Extract structured data from PDFs in Microsoft Power Automate - no code required. Use the HTTP connector to convert PDFs from SharePoint, Outlook, and Teams into JSON, text, CSV, or Markdown.

Why use PDFPipe with Power Automate?

Power Automate is great at connecting Microsoft services and triggering workflows. But it has no built-in way to extract structured data from PDFs. The AI Builder PDF model requires a premium license and only works with predefined templates. Custom connectors for PDF parsing are complex to build and maintain.

PDFPipe works with Power Automate's standard HTTP connector - available in every plan. When a PDF arrives in SharePoint, hits your Outlook inbox, or gets shared in Teams, your flow calls PDFPipe and gets back structured data you can route anywhere: Excel, Dataverse, SQL Server, or another API.

No premium connectors. No AI Builder credits. No custom code. Just an HTTP action that converts any PDF URL into the format you need.

How it works

Add an HTTP action to your flow. PDFPipe handles the PDF conversion.

1. Configure the HTTP action

HTTP action configuration
{
  "method": "POST",
  "uri": "https://api.pdfpipe.dev/v1/convert",
  "headers": {
    "Authorization": "Bearer pk_live_...",
    "Content-Type": "application/json"
  },
  "body": {
    "url": "@{triggerOutputs()?['body/{Link}']}",
    "format": "json",
    "returnMethod": "inline"
  }
}

2. Get the response

JSON response
{
  "requestId": "req_01J9X7K2M...",
  "status": "complete",
  "format": "json",
  "pagesProcessed": 3,
  "creditsUsed": 1,
  "contentType": "application/json",
  "content": "{\"pages\":[{\"page\":1,\"text\":\"...\"}]}"
}

Complete flow example

Here is a typical Power Automate flow that processes invoices uploaded to SharePoint. The flow triggers on new files, sends the PDF to PDFPipe, and routes the extracted data wherever you need it.

  • SharePoint, Outlook, and Teams triggers
  • Standard HTTP connector - no premium license
  • JSON, text, CSV, or Markdown output
  • Route data to Excel, Dataverse, or SQL Server
  • Works with any PDF URL - including protected files
Power Automate flow steps
Step 1: Trigger
  "When a new file is created in SharePoint"
  - Site: your-company.sharepoint.com
  - Library: Invoices
  - Folder: /Incoming

Step 2: HTTP Action
  Method: POST
  URI: https://api.pdfpipe.dev/v1/convert
  Headers:
    Authorization: Bearer pk_live_...
    Content-Type: application/json
  Body: {
    "url": "@{triggerOutputs()?['body/{Link}']}",
    "format": "json",
    "returnMethod": "inline"
  }

Step 3: Parse JSON
  Content: @{body('HTTP')}
  Schema: (use "Generate from sample" with the response)

Step 4: Parse inner JSON (when returnMethod is inline and status is complete)
  Content: @{body('Parse_JSON')?['content']}
  Schema: (your PDFPipe JSON document shape)

Step 5: Use the data
  - Save to Excel, update a database, send via Teams
  (If you omit returnMethod or get returnMethodFallback, use a second HTTP GET to resultUrl instead.)
Outlook attachment trigger
{
  "method": "POST",
  "uri": "https://api.pdfpipe.dev/v1/convert",
  "headers": {
    "Authorization": "Bearer pk_live_...",
    "Content-Type": "application/json"
  },
  "body": {
    "url": "@{items('Apply_to_each')?['ContentBytes']}",
    "format": "json",
    "returnMethod": "inline"
  }
}

Works with any Microsoft trigger

PDFPipe integrates with any Power Automate trigger that produces a PDF URL or file content. Process invoices from SharePoint, extract data from email attachments in Outlook, or handle documents shared in Teams channels.

SharePointOutlookTeamsOneDriveFormsDataverseExcel Online

Start converting PDFs in Power Automate today

Free tier includes 10 requests per month. No credit card required.