Skip to main content
The Nitro connectors bring Nitro Automate’s document processing and eSignature capabilities into Power Automate, so you can add them to the processes you already run across Microsoft 365 without writing code. Pick a file from SharePoint, OneDrive, Outlook, or Dataverse, run it through Nitro, and write the result back — no HTTP requests, no token handling.
This section documents the Nitro PDF Services connector (Preview), a premium connector published in the Microsoft connector gallery. There is nothing to import — search for it in the action picker. It is available in Power Automate, Power Apps, Azure Logic Apps and Copilot Studio in all regions except US Government (GCC, GCC High, DoD) and China (21Vianet).eSignature actions come from the separate Nitro Sign connector.

What you can do

Conversions

Convert between PDF and Office formats (Word, Excel, PowerPoint) in either direction, plus images and HTML to PDF and PDF to PDF/A for archiving.

Data extraction

Extract text, tables, invoice data, form fields and metadata from documents and pass them to downstream systems.

Document generation

Fill PDF forms with data from your flow or from a CSV, JSON, XFDF or FDF file, or turn a flat PDF into a fillable form automatically.

Document manipulation

Merge, split, compress, optimize, OCR, rotate, flatten and watermark PDFs as a step in any flow.

End-to-end eSignatures

Create envelopes, add documents and participants, place signature fields, set signing order, send requests and retrieve completed documents with full audit trails — with the Nitro Sign connector.

Security and compliance

Password-protect documents, manage permissions and redact sensitive data to keep your flows compliant.

Keep documents moving

Start document processing automatically from events like a new file in SharePoint, an email in a shared mailbox, or a Microsoft Forms submission.

Typical flows people build with it

  • A new invoice lands in a SharePoint library → Extract Invoice Data from PDF → create a row in Dataverse.
  • A contract arrives in a shared mailbox → Extract PII from PDF → Redact PDF Pages → store the redacted copy.
  • A Word report is approved → Word to PDF → Password Protect PDF Document → email it to the client.
  • A folder of scans builds up → OCR PDF Document → Merge PDF Documents → Compress PDF Document → archive the result.
  • A Microsoft Forms response comes in → Fill PDF Form → save the completed form to OneDrive.
  • A deal is marked closed-won → Create Envelope → Send Envelope for Signing → save the sealed copy to SharePoint.

How it works

Connecting to Nitro

The first time you add a Nitro action to a flow, Power Automate asks you to create a connection. Enter the Client ID and Client Secret from your API application. The connection is stored in your Power Platform environment and can be reused across your flows; the connector obtains and refreshes access tokens for you.
Nitro actions take file content directly from earlier steps — SharePoint, OneDrive, Outlook attachments, Dataverse — and return the processed file as File Content you can pass to the next step, including another Nitro action. Files up to 100 MB and 500 pages are supported.
Every action completes within its step and returns the result in the same run — most in a few seconds, larger OCR or conversion jobs in under a minute. An asynchronous mode is available for advanced scenarios; see Output modes.

Before you start

You need both of the following:
1

Nitro PDF Services credentials

A Client ID and Client Secret from the Nitro Developer portal. See Credentials for how to create an API application, or request API access if you do not have an account yet.
2

A plan that includes premium connectors

Nitro PDF Services is a premium connector. You need a Power Automate, Power Apps, Logic Apps, or Copilot Studio plan that includes premium connectors.

Where to go next

Get started

Create a connection and build your first flow.

Authentication

How the connector exchanges your Client ID and Secret for an access token.

Actions

Every action the connector exposes, with its inputs and outputs.

Working with files

How files move between steps, chaining actions, and the JSON each action takes.