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

# Zapier

> Connect Wiredesk to thousands of apps with Zapier: send finished conversations and leads where your team works, and add contacts, knowledge and messages from other apps.

> [!NOTE]
>
> The Wiredesk integration for Zapier is waiting for Zapier's review and isn't in the Zapier App Directory yet. This page describes what you'll get once it's published. Until then, you can connect any app to the [REST API](https://wiredesk.ai/docs/developers/api.md) or [webhooks](https://wiredesk.ai/docs/developers/webhooks.md) with Zapier's **Webhooks by Zapier** steps. If you'd like early access, [contact us](https://wiredesk.ai/contact).

The Wiredesk integration for Zapier connects your workspace to the other apps your team uses. For example, it can send every finished conversation to your CRM or Slack, or add new contacts from a sign-up form so the agent knows their name. It works through the [REST API](https://wiredesk.ai/docs/developers/api.md), so a Zap can do anything an API key can, and nothing more. Once it's in the Zapier App Directory, Wiredesk also works with Zapier's AI tools: Zapier MCP and AI Actions.

## Connect your workspace

**1. Make an API key**

In Wiredesk, go to **Developers → API keys** and make a key named Zapier. Only owners and admins see the Developers section. Choose **Full access**: instant triggers add a webhook endpoint when you turn a Zap on, and actions add contacts, knowledge or messages. A **Read only** key only works for New Conversation, New Contact and Find Contact.

**2. Connect in Zapier**

Pick Wiredesk in a Zap, choose **Sign in**, and paste the key. Zapier checks it by reading your agents. The connection is named after the key, like `Wiredesk (wd_3f9a…c41e)`, the same way the API keys list shows it.

The connection follows the same rules as any key: it stops working if the key is revoked, or if the person who made it is no longer an owner or admin. Changes a Zap makes show in the activity log under that person, with the key's name. See [Authentication](https://wiredesk.ai/docs/api-reference/authentication.md).

## Triggers

Four triggers are instant: Wiredesk sends the event to Zapier the moment it happens. Two check Wiredesk for new items every few minutes instead, because Wiredesk sends no event for them. How often depends on your Zapier plan.

| Trigger | Runs when | Filters | Arrives |
| - | - | - | - |
| **Conversation Ended** | A conversation has closed and been summarised. It includes the summary, outcome, topic and sentiment. Calls are summarised when they end. Chats and emails close after 30 quiet minutes and are summarised within the next 15. | Agent, channel | Instant |
| **New Lead** | An agent saves a lead with a **Capture leads** action. It includes the name, email, phone and the other fields the action collects. | Agent | Instant |
| **Handover Requested** | An agent asks for a person to take over, with its reason. Once per request: a customer asking again while they wait doesn't run it again. | Agent, channel | Instant |
| **New Message** | A customer, the agent or someone on your team writes in a chat or email conversation. Phone and browser-voice lines aren't sent one by one. | Agent, channel, from | Instant |
| **New Conversation** | A conversation starts on any channel. | Agent, channel | Every few minutes |
| **New Contact** | Someone talks to your agents for the first time, or a contact is added. | Kind | Every few minutes |

A Conversation Ended Zap gets the conversation, not its transcript. To get the transcript, add a **Webhooks by Zapier** step that calls [`GET /conversations/{id}/messages`](https://wiredesk.ai/docs/api-reference/conversations/list-messages).

### How instant triggers work

* Turning on a Zap with an instant trigger adds a [webhook endpoint](https://wiredesk.ai/docs/developers/webhooks.md) to your workspace, pointing at Zapier. You'll see it under **Developers → Webhooks**, described as `Zapier: <trigger>`. Turning the Zap off, or deleting it, removes the endpoint.
* Adding the endpoint takes a **Full access** key. With a **Read only** key, the Zap won't turn on.
* A workspace can have up to 10 webhook endpoints, and each Zap with an instant trigger that's on uses one. If you've reached 10, turn off a Zap you no longer need or remove an endpoint you don't use.
* Each event is signed, and the Zap checks the signature before it runs, so a request that didn't come from Wiredesk doesn't run it.
* While you set up a Zap, Zapier shows recent items from Wiredesk as samples. They're read from the API, so New Message and Handover Requested samples may have some fields empty.
* If you remove the endpoint in the dashboard, the Zap stops getting events. Turn it off and on again to add a new one.

## Actions

| Action | What it does |
| - | - |
| **Send Message to Agent** | Sends a customer's message to an agent and returns its reply. The agent uses the same instructions, knowledge, actions and handoff as in the chat widget, and the reply is billed as a chat reply. Pass the **Conversation ID** from an earlier step to continue that conversation. If someone on your team has taken the conversation over, the reply is empty and the handover state is `active`. |
| **Add Knowledge Source** | Teaches an agent from **Text**, up to 200,000 characters, or a **Website**. Text is ready straight away. A website is crawled in the background and starts out `pending`. |
| **Create or Update Contact** | Adds a contact by phone number (international format, like `+14155550123`) or email, with the name the agents should use. If that number or address already has a contact, the step updates the name instead of failing. |
| **Update Contact** | Changes a contact's name. |

## Searches

| Search | What it does |
| - | - |
| **Find Contact** | Finds a contact by phone number or email, among all your contacts. Phone numbers match however they're written, so `+1 (415) 555-0123` finds `+14155550123`, and email addresses match whatever their case. |
| **Find or Create Contact** | Finds the contact, or creates one if there isn't one. |

## Example Zaps

* **Conversation Ended → Slack:** post the summary and outcome of every phone call that was handed over.
* **Conversation Ended → HubSpot or Salesforce:** log each finished conversation on the customer's record.
* **New Lead → your CRM:** create a lead or deal with the fields the agent collected.
* **Handover Requested → Slack or SMS:** tell whoever is on shift the moment a customer needs a person, with the agent's reason.
* **Form submission → Create or Update Contact:** the agent greets new sign-ups by name when they call or email.
* **New document in Google Drive or Notion → Add Knowledge Source:** keep the agent's answers up to date.
* **New helpdesk ticket → Send Message to Agent:** draft a first answer from the agent's knowledge.

## Limits

* Zaps count against the workspace's API rate limit, together with your other keys.
* Files can't be added as knowledge yet. Upload them on the agent's **Knowledge** page.
* Each Zap with an instant trigger that's on uses one of the workspace's 10 [webhook endpoints](https://wiredesk.ai/docs/developers/webhooks.md).
* New Conversation and New Contact aren't instant, because Wiredesk sends no event for them.

## Related

* [REST API](https://wiredesk.ai/docs/developers/api.md)
* [Webhooks](https://wiredesk.ai/docs/developers/webhooks.md)
* [MCP server](https://wiredesk.ai/docs/developers/mcp.md)
* [Integrations](https://wiredesk.ai/docs/integrations/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.