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

# Zapier

> Connect Scanova to thousands of apps via Zapier.

Zapier lets you wire Scanova into thousands of other apps — Google Sheets, Slack, HubSpot, and more — without writing code. On the Scanova side, connecting Zapier is a single step: generate a Management API token scoped to the `zapier` environment, then paste it into the Scanova app inside your Zapier account. From there, Zaps are built and managed entirely in Zapier.

<Note>
  This integration is a **token handshake**, not a visual trigger/action builder inside Scanova itself. Everything you'd recognize as "Zapier setup" — choosing triggers, actions, and field mappings — happens on Zapier's platform, using its published Scanova app. Scanova's side only issues and revokes the token that app authenticates with.
</Note>

## Prerequisites

* A Zapier account.
* A Scanova plan that includes the Zapier integration quota (`INTEGRATION_ZAPIER`). If your token is rejected with a quota error, contact [support@scanova.io](mailto:support@scanova.io).

## Setting up the connection

<Steps>
  <Step title="Open the Zapier integration">
    From **Integrations**, select **Add Integration**, then find the **Zapier** card and select **Setup**. This opens a setup panel — Zapier doesn't need a multi-step wizard, since there's nothing to configure on Scanova's side beyond the token itself.
  </Step>

  <Step title="Generate a token">
    Select **Generate token**. Scanova creates a Management API key with `environment=zapier`, named `zapier_<your-account-email>`. The token is shown once — copy it immediately using the copy icon next to the masked value. There's no way to reveal it again later; if you lose it, revoke it and generate a new one.
  </Step>

  <Step title="Connect the Scanova app in Zapier">
    Open the **Scanova** app inside your Zapier account and paste the token when prompted to authenticate.
  </Step>

  <Step title="Build a Zap">
    Create a Zap with a Scanova trigger — for example, a new scan or a new lead — then connect the destination app (Sheets, Slack, HubSpot, or anything else Zapier supports).
  </Step>

  <Step title="Turn the Zap on">
    Once the Zap is on, Scanova events start flowing to your chosen destination automatically.
  </Step>
</Steps>

<Warning>
  Revoking the token (**Revoke token** in the setup panel) immediately disables every trigger and action configured against it in Zapier — any live Zaps built on this connection stop working.
</Warning>

## How the token actually works

The Zapier integration is built entirely on the Management API — there's no bespoke Zapier-specific backend. For the underlying request/auth mechanics (host, header format, and how the `environment=zapier` quota check and its required `User-Agent: zapier` header interact), see:

<Card title="Management API overview" icon="key" href="/api-reference/management-api/overview">
  How Management API tokens authenticate, including the `zapier` environment's quota and User-Agent requirements.
</Card>

## What data flows where

Once a Zap is live, Scanova pushes trigger events (such as new scans or new leads) to Zapier, which hands them to whatever action you've configured in the destination app. Zaps that call back into Scanova (for example, creating a QR code from another app's event) use the same token against the regular Management API data endpoints.

## Related

* [Management API overview](/api-reference/management-api/overview) — the two-host auth architecture the `zapier` environment token authenticates against.
* [Create an API token](/api-reference/management-api/tokens/create) — how the `environment=zapier` key handed to Zapier is generated.
* [MCP overview](/mcp/overview) — another integration built on a Management API key with its own dedicated environment.