> ## Documentation Index
> Fetch the complete documentation index at: https://developers.gonitro.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Get started with Zapier

> Connect the Nitro PDF Services app to Zapier and build your first Zap.

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](/docs/authentication/credentials) for how to create one, or
[request API access](https://sso.gonitro.com/platform-trial-signup) if you do not have an account
yet.

## 1. Connect your Nitro account

<Steps>
  <Step title="Add a Nitro step to a Zap">
    In the Zap editor, add an action step and search for **Nitro PDF Services**.
  </Step>

  <Step title="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*
  </Step>

  <Step title="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.
  </Step>
</Steps>

Connections are reusable — connect once and pick the same account in every Zap.

## 2. Build your first Zap

<Steps>
  <Step title="Trigger — Dropbox: New File in Folder">
    Point it at the folder you want to watch.
  </Step>

  <Step title="Filter (optional)">
    Add a **Filter by Zapier** step: only continue if the file name **ends with** `.pdf`.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Test and publish">
    Run a test with a real PDF, confirm the uploaded file is smaller, then publish.
  </Step>
</Steps>

<Warning>
  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.
</Warning>

## 3. Choosing an output type

Actions that return a file have an **Output Type** field with two choices:

| Choice | What you get | Use it when |
| - | - | - |
| **Download file** | A file object Zapier can hand to any file-accepting field | You are storing or emailing the result |
| **Download URL** | A URL plus metadata (content type, size, page count) | You want the metadata, or the target app takes a URL |

Extraction actions have no **Output Type** — they always return structured fields.

<Note>
  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.
</Note>

## Next steps

<Columns cols={3}>
  <Card title="Actions" icon="list-check" href="/docs/integrations/zapier/actions">
    Everything the app can do, with inputs and outputs.
  </Card>

  <Card title="Working with files" icon="folder-open" href="/docs/integrations/zapier/working-with-files">
    Files in, files out, and chaining actions.
  </Card>

  <Card title="Limits and errors" icon="triangle-exclamation" href="/docs/integrations/zapier/limits-and-errors">
    File size, page count, throttling, and what each error means.
  </Card>
</Columns>