Skip to main content
The Nitro PDF Services connector is published in the Power Automate connector gallery, so there is nothing to install. This guide takes you from a blank environment to a working flow that compresses every PDF added to a SharePoint library.

Before you start

1

Nitro PDF Services credentials

A Client ID and Client Secret for an API application. See Credentials for how to create one in the Nitro Developer portal, 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.

1. Create a connection

You can create the connection ahead of time, or let the designer prompt you the first time you add a Nitro action. Either way the dialog is the same.
1

Open Connections

In Power Automate, go to Connections in the left navigation and click New connection.
2

Find Nitro PDF Services

Search for Nitro and click + on Nitro PDF Services (publisher Nitro PDF).
3

Enter your credentials

Fill in Nitro Client ID and Nitro Client Secret, optionally give the connection a display name, and click Create.
Connect to Nitro PDF Services dialog with Display name, Nitro Client ID and Nitro Client Secret fields

The connection dialog. Only the Client ID and Client Secret are required.

There is no interactive sign-in. The connector exchanges your credentials for an access token behind the scenes and refreshes it automatically — see Authentication.
Nitro connections are not shareable. If you share a flow or app, the other person is prompted to create their own connection with their own credentials.

2. Build your first flow

The flow below watches a SharePoint document library, compresses each new PDF with Nitro, and writes the result to another folder. It uses four steps and no expressions.
Flow with four steps: When a file is created (properties only), Get file content, Compress PDF Document, Create file

The finished flow.

1

Create an automated cloud flow

On the Create page choose Automated cloud flow, name it, and pick the SharePoint trigger When a file is created (properties only). Set Site Address and Library Name to the library you want to watch.
2

Add SharePoint — Get file content

Click + under the trigger, search for Get file content and pick the SharePoint action. Set Site Address to the same site and File Identifier to the trigger’s Identifier output.
The properties only trigger does not include the file’s bytes. This step is what actually loads the PDF; without it the Nitro action has nothing to work on.
3

Add Nitro — Compress PDF Document

Click + again, search for Nitro PDF Services and click See more to list every action. Pick Compress PDF Document.
Add an action panel listing every Nitro PDF Services action

All 33 Nitro actions in the action picker.

If you have not created a connection yet, the designer asks you to do so now.
4

Point the Nitro action at the file

Click into the PDF File input, then click the lightning-bolt icon to open the dynamic content picker. Under Get file content, choose File Content.
Compress PDF Document action with the dynamic content picker open, showing File Content from Get file content

Drop the SharePoint File Content token into PDF File.

Leave PDF File (file name) empty for now, and leave Accept (Output format) under Advanced parameters at its default, application/octet-stream, so the action returns the compressed PDF itself.
5

Add SharePoint — Create file

Click +, search for Create file and pick the SharePoint action. Set Site Address and Folder Path to where the compressed copy should go — use a different folder or library from the one the trigger watches, otherwise the flow triggers itself.Then open the dynamic content picker for File Content. The Compress PDF Document step exposes three file tokens: File Name, File Content Type, and File Content.
Create file action with the dynamic content picker showing the Compress PDF Document tokens File Name, File Content Type and File Content

Every Nitro action that returns a file exposes File Name, File Content Type and File Content.

Drop File Content into File Content, and File Name into File Name.
Create file action with File Name and File Content both set to Compress PDF Document tokens

Create file wired to the Nitro output.

6

Save and test

Click Save, then Test → Manually and drop a PDF into the watched library. The run history shows each step’s inputs and outputs, including the size of the file Nitro returned.
Nitro’s File Name output is a generic name such as result.pdf, so every run of the flow above writes the same file name. To keep the original name, set File Name on Create file to the trigger’s File name with extension token instead — see File names.

What just happened

  • SharePoint handed the PDF’s bytes to the Nitro action as File Content.
  • The connector uploaded the bytes to Nitro, waited for the result, and returned the compressed PDF as a File Content token that any later step can use.
  • Nothing about tokens, base64, or the REST API surfaced in the designer. When you do want to know how files move between steps, read Working with files.

Next steps

Working with files

Chaining Nitro actions, output modes, and the JSON each action expects.

Actions

Every action, with its inputs and outputs.

Limits and errors

File size, page count, throttling, and error codes.