Skip to main content
This guide takes you from nothing to a working Zap that compresses every PDF added to a Dropbox folder.

​
Before you start

You need a Client ID and Client Secret for a Nitro API application. See Credentials for how to create one, or request API access if you do not have an account yet.

​
1. Connect your Nitro account

1

Add a Nitro step to a Zap

In the Zap editor, add an action step and search for Nitro PDF Services.
2

Sign in to Nitro PDF Services

Click Sign in. Zapier asks for:
  • Client ID — your Nitro application’s Client ID
  • Client Secret — the matching secret
  • Connection Name (optional) — a label such as Nitro Prod or Marketing Team
3

Let Zapier test the connection

Zapier verifies the credentials against Nitro straight away. The connection appears in the account picker under the name you gave it, or as Nitro app …1234 (the last four characters of the Client ID) if you left the name blank.
Connections are reusable — connect once and pick the same account in every Zap.

​
2. Build your first Zap

1

Trigger — Dropbox: New File in Folder

Point it at the folder you want to watch.
2

Filter (optional)

Add a Filter by Zapier step: only continue if the file name ends with .pdf.
3

Action — Nitro PDF Services: Compress PDF

  • PDF File → the trigger’s file field. Zapier passes a file URL or the file itself; the Nitro app handles both.
  • Output Type → Download file.
There are no other options: Compress always targets the smallest file. If you want to choose the size/quality trade-off, use Optimize PDF and its profile instead.
4

Action — Dropbox: Upload File

  • File → the Nitro step’s Compressed PDF File output.
  • Folder → a different folder from the trigger’s, or the Zap will re-trigger on its own output.
5

Test and publish

Run a test with a real PDF, confirm the uploaded file is smaller, then publish.
Writing the output back into the folder the trigger watches creates a loop. Use a separate folder, or add a filter that skips names the Zap itself produces.

​
3. Choosing an output type

Actions that return a file have an Output Type field with two choices: Extraction actions have no Output Type — they always return structured fields.
Download URLs are valid for about 15 minutes, after which Nitro deletes the output file. Use the URL within the same Zap run rather than storing it.

​
Next steps

Actions

Everything the app can do, with inputs and outputs.

Working with files

Files in, files out, and chaining actions.

Limits and errors

File size, page count, throttling, and what each error means.