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

# Zapier Integration

> Connect Cyberdesk to 6,000+ apps with Zapier

## Overview

Cyberdesk has a native Zapier connector. When enabled, you can trigger Zapier automations whenever a run completes — connecting your desktop automation to thousands of apps like Google Sheets, Notion, Airtable, email, and more.

Since Zapier Webhooks support arbitrary payloads, **no transformation code is required**. The full run data is sent directly to Zapier, where you can map fields to any action.

## Setup

<Note>
  **Prerequisite:** You must first enable webhooks for your organization. See the [Webhooks Quickstart](/webhooks/quickstart) to get started.
</Note>

<Steps>
  <Step title="Open the Webhooks tab">
    Go to the **Webhooks** tab in the Cyberdesk dashboard.
  </Step>

  <Step title="Add a new endpoint">
    Click **"+ Add Endpoint"** to create a new webhook endpoint.
  </Step>

  <Step title="Select Zapier as the destination">
    In the "New Endpoint" page, click the **"Webhook"** dropdown (with a down chevron) and select **"Zapier"**.
  </Step>

  <Step title="Get your Zapier webhook URL">
    You'll see instructions for getting a Zapier webhook URL:

    1. Go to [Zapier](https://zapier.com) and create a new Zap
    2. Choose **"Webhooks by Zapier"** as your trigger
    3. Select **"Catch Hook"** as the trigger event
    4. Copy the webhook URL Zapier provides
    5. Paste it into the Cyberdesk endpoint configuration

    <Tip>
      After pasting the URL and creating the endpoint, trigger a test run in Cyberdesk. Then click "Test trigger" in Zapier to see the payload structure and set up your action.
    </Tip>
  </Step>

  <Step title="Create the integration">
    Click **"Create"** to complete the configuration.
  </Step>
</Steps>

## You're done!

Your Zapier Zap will now trigger whenever a run completes. The webhook payload includes run data — status, timestamps, `input_values`, `output_data`, errors, and more — which you can map to any Zapier action. `run_message_history` is omitted to keep deliveries small and reliable.

## Example use cases

* **Log runs to Google Sheets** — Append a row for each completed run with status, duration, and outputs
* **Send email notifications** — Email yourself or your team when runs fail
* **Update Notion databases** — Track automation results in your project management system
* **Post to Discord/Teams** — Notify a channel when important workflows complete
* **Trigger follow-up workflows** — Chain Cyberdesk runs with other automation tools

<Tip>
  Use Zapier's **Filter** step to only continue the Zap for specific statuses (e.g., only on `error`) or when certain output values are present.
</Tip>