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

# Zapier

> Connect Introw to thousands of apps with no code, so partner events trigger actions across your stack and external systems can push data into Introw.

> Wire Introw into the rest of your stack without engineering. Zapier connects partner events to thousands of apps, both ways, so your program automates end to end.

## What it does

The Zapier integration exposes Introw as triggers and actions in Zapier. When something happens in your program, like a new partner, a registered deal, or a submitted form, Zapier can fan that event out to the tools you already run: spreadsheets, messaging, marketing automation, ticketing, and more. It works the other way too, so external systems can create or update records in Introw.

Because it is no-code, partner operations can build and change these automations themselves, without waiting on a developer or the public API.

## The problem it solves

* **Partner events stay trapped in one tool** → Zapier pushes them anywhere your team already works, with no glue code.
* **Connecting niche apps needs engineering** → Partner ops build the connection themselves in Zapier.
* **Manual copying between systems** → Events sync automatically, cutting the busywork.
* **The public API is overkill for a simple sync** → Zapier covers common integrations without a build.

## From problem to solution

Instead of filing an engineering ticket for every integration, partner operations connect Introw to the rest of the stack themselves. A new partner can kick off an onboarding sequence; a closed-won partner deal can post to a finance sheet; an external signup can create a partner. The program becomes automated without adding headcount.

```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
  event["Partner event"] --> zap["Zap"]
  zap --> action["Action across your stack"]
```

## Use cases

<CardGroup cols={2}>
  <Card title="Automate onboarding" icon="circle-check">
    A new partner triggers a sequence in your other tools.
  </Card>

  <Card title="Sync to finance or ops sheets" icon="circle-check">
    Push deal and payout events to spreadsheets.
  </Card>

  <Card title="Notify any channel" icon="circle-check">
    Send partner events to chat, email, or ticketing.
  </Card>

  <Card title="Create records from outside" icon="circle-check">
    Let external systems create partners or deals in Introw.
  </Card>
</CardGroup>

## Impact

* **Composability** - Introw becomes a building block in a wider automated stack.
* **Low total cost of ownership** - partner ops build integrations with no code.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Operations" icon="user">
    Automates the program across tools without engineering.
  </Card>

  <Card title="Revenue Operations" icon="user">
    Keeps partner data flowing into the wider stack.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="API Keys & REST API" icon="code" href="/features/developer/api">
    Runs on the public API.
  </Card>

  <Card title="Partner Notifications" icon="users" href="/features/partners/notifications">
    Fan partner events out to any tool.
  </Card>
</CardGroup>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Endpoints and code.
  </Card>
</CardGroup>