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

# Zapier Integration

> Connect Woes to Zapier with a scoped API key for no-code support workflows.

# Zapier Integration

<img src="https://mintcdn.com/woes/SjmqB9Aiw359c6aC/images/integrations/zapier-logo.svg?fit=max&auto=format&n=SjmqB9Aiw359c6aC&q=85&s=221d69a045a2f681d1e3ef0ee1086400" alt="Zapier logo" width="56" height="56" data-path="images/integrations/zapier-logo.svg" />

Zapier gives teams a no-code way to connect Woes support data to the other
tools they already use. Use it when an external workflow should read or create
Woes records without building directly against the REST API.

## At A Glance

| Use Zapier for                                                                                             | Where it appears                                  |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------- |
| No-code workflows that read or create Woes conversations, issues, clients, tags, statuses, and priorities. | Integrations > Zapier and the Woes app in Zapier. |

## What It Does

The Zapier integration creates a workspace API key with the scopes needed for
supported Zapier actions.

| Capability          | What you can do                                                                                     |
| ------------------- | --------------------------------------------------------------------------------------------------- |
| Create a Zapier key | Generate a scoped Woes API key for Zapier.                                                          |
| Copy once           | Copy the key when it is created. Woes does not show the full key again.                             |
| Use Woes actions    | Let Zapier work with supported Woes conversations, issues, clients, tags, statuses, and priorities. |
| Review access       | See the key prefix, last-used state, and granted scopes in Woes.                                    |
| Disconnect          | Revoke the Zapier connection from Woes when the workflow should stop.                               |

## Setup

<Steps>
  <Step title="Open Integrations">
    In Woes, go to **Workspace Settings -> Integrations**.
  </Step>

  <Step title="Create the Zapier key">
    Open **Zapier** and click **Connect** or **Create Zapier key**.
  </Step>

  <Step title="Copy the key">
    Copy the generated key immediately and paste it into Zapier when connecting
    the Woes app.
  </Step>

  <Step title="Build the Zap">
    Choose the Woes trigger, search, or action you need.
  </Step>

  <Step title="Test the workflow">
    Run the Zapier test and confirm the expected record appears in Woes.
  </Step>
</Steps>

## Good Use Cases

* Add high-priority Woes issues to an operations spreadsheet.
* Create a CRM task after a low CSAT response.
* Create a Woes issue from another support or product workflow.
* Add a conversation message from an approved external workflow.
* Search Woes records before deciding what an automation should do next.

## Supported Zapier Operations

| Type             | Operations                                                                                    |
| ---------------- | --------------------------------------------------------------------------------------------- |
| Polling triggers | New conversation, new issue, updated issue.                                                   |
| Searches         | Conversations, issues, clients, tags, statuses, and priorities.                               |
| Actions          | Create conversation, add conversation message, create issue, update issue, and create client. |

The Zapier key grants the scopes needed for those operations:
`clients:read`, `clients:write`, `conversations:read`,
`conversations:write`, `definitions:read`, `issues:read`, and
`issues:write`.

## Data And Privacy

Zapier uses a Woes API key, so treat it like any other server-side credential.
Do not paste the key into browser code, public documentation, customer replies,
or shared notes.

The key is scoped to the workspace and can be revoked by disconnecting Zapier in
Woes. Disconnecting stops new Zapier API calls but does not delete records that
Zapier already created.

## Current Boundaries

* Zapier is a workflow integration, not a customer conversation channel.
* The full API key is shown only once when it is created.
* Zapier actions follow the same workspace permissions and API limits as other
  Woes API-key integrations.
* Webhook-style instant triggers are separate from this key-based Zapier
  connection and should be documented only when they are available.

## Troubleshooting

| Issue                          | What to check                                                                                   |
| ------------------------------ | ----------------------------------------------------------------------------------------------- |
| Zapier says the key is invalid | Create a new Zapier key in Woes and update the Zapier connection.                               |
| A Zap can read but not write   | Confirm the Woes action is supported by the Zapier app and that the key has the required scope. |
| The key was copied incorrectly | Disconnect Zapier in Woes, create a new key, and paste the new value into Zapier.               |
| A workflow should stop         | Disconnect Zapier from the Woes integration card to revoke the key.                             |

## Related Docs

* [Public REST API](/api/overview)
* [API Keys](/api/keys)
* [Issues API](/api/issues)
* [Conversations API](/api/conversations)