> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/other-integrations/zapier.md).

# Zapier

Start a Zap the moment a recording, an AI report, a comment, a video call or a booking happens in Screendesk. Works on every plan.

The [Screendesk app on Zapier](https://zapier.com/apps/screendesk/integrations) starts your Zaps the moment something happens in your workspace: a new recording, its AI report, a comment, a video call that ends, or a booking. Send them to a spreadsheet, an issue tracker, a chat tool or any of the apps Zapier supports.

{% embed url="<https://app.screendesk.io/recordings/339cf30a-de7a-4767-a42d-da2b8f07d5f0>" %}

Zapier works on every plan, with no API access needed. Only a workspace admin can connect it.

## 1. Choose Screendesk in a Zap

1. In Zapier, create a Zap, or click **Open Zapier** on the **Zapier** card in **Settings → Integrations**, under **Workflows**.
2. Choose **Screendesk** as the trigger app and pick a trigger event (see [Triggers](#triggers)). Every Screendesk trigger is **Instant**.
3. For **New Recording** and **New AI Report**, choose which **Recordings** start the Zap. **Sent by customers** is the default.

## 2. Connect your workspace

1. Under **Account**, click **Select** (or **Change**, then **+ Connect a new account**), and confirm with **Connect**. Zapier opens Screendesk.
2. Sign in to Screendesk if you aren't already, pick the workspace, and click **Allow**.

You're back in Zapier, connected, and the connection is named after your workspace. There's nothing to copy or paste.

If you're an admin of several workspaces, connect each one separately. A teammate who isn't an admin sees a message asking them to have an admin connect it.

## 3. Test the trigger and switch the Zap on

1. Click **Test trigger**. Zapier shows your latest matching items, or an example if there are none yet.
2. Add the action that should run and map the fields you need into it.
3. Publish the Zap.

From then on, each event reaches the Zap within seconds. In Screendesk, the card shows **Connected** and how many triggers are switched on.

## Triggers

| Trigger             | Starts a Zap when                                                                     |
| ------------------- | ------------------------------------------------------------------------------------- |
| New Recording       | A recording is ready to watch                                                         |
| New AI Report       | A recording's AI report is ready, with its summary, main issue and steps to reproduce |
| New Comment         | A teammate comments on a recording                                                    |
| Video Call Ended    | A video call ends, recorded or not                                                    |
| New Booking         | Someone books a time on one of your booking links                                     |
| Booking Rescheduled | A booking moves to another time                                                       |
| Booking Cancelled   | A booking is cancelled                                                                |

The two recording triggers take recordings **Sent by customers**, **Made by your team**, **Recorded video calls**, **Uploaded videos**, or **All recordings**. Screendesk only sends the Zap the ones you chose.

Each event carries its details, such as a recording's title, link, customer email, helpdesk and ticket, or an AI report's summary, issue and steps to reproduce. The full list of fields is in the [webhook events reference](https://docs.screendesk.io/api/webhooks/events): Zapier receives the same events.

Zapier gets links and details, never the video files, and can't change anything in Screendesk.

{% hint style="info" %}
To act on recordings without leaving Screendesk, such as posting them to a Slack channel or filing them in a folder, use an [automation](https://docs.screendesk.io/organization-and-workflows/workspace-automations.md) (Pro and Enterprise). On other plans, the **Automations** page offers Zapier instead.
{% endhint %}

## See and manage the connection

Click **Configure** on the **Zapier** card (admins only):

* **Connections** lists who connected the workspace and when, with **Disconnect**. Disconnecting stops that connection's Zaps at once and can't be undone.
* **Triggers switched on** lists each Zap's trigger, since when, and when it last sent an event. Zapier adds and removes them as Zaps are switched on and off.

A connection works as the admin who made it. If they leave the workspace, stop being an admin or can no longer sign in, it stops: the card shows **Action required** and the sheet says why. Another admin connects Screendesk again in Zapier and picks the new connection in each Zap.

## Troubleshooting

* **The Zap doesn't start.** Check that the Zap is on, that the Zapier card doesn't show **Action required**, and that the trigger's **Recordings** choice matches the recording: by default only recordings customers send you start it.
* **Zapier says it can't connect.** Only a workspace admin can click **Allow**. Ask an admin to connect it from their own Zapier account.
* **A trigger shows a warning in the sheet.** Screendesk stops sending to a Zap that keeps failing. Switch the Zap off and on in Zapier to restart it.
* **A Zap made before November 2026 still asks for an API key.** It uses the previous version of the Screendesk app. Edit the Zap, update the Screendesk step to the latest version and connect again: it then signs in the new way.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.screendesk.io/other-integrations/zapier.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
