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 or webhooks with Zapier’s Webhooks by Zapier steps. If you’d like early access, contact us.
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.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.
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.
How instant triggers work
- Turning on a Zap with an instant trigger adds a webhook endpoint 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
Searches
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.
- New Conversation and New Contact aren’t instant, because Wiredesk sends no event for them.