Skip to main content
The Wiredesk nodes for n8n come in one community package, n8n-nodes-wiredesk: the Wiredesk node and the Wiredesk Trigger. Each of the Wiredesk node’s operations is one endpoint of the REST API, so it can do what the API does, with an API key from your workspace. n8n’s AI Agent can also use it as a tool.

Install the node

1

Install it in n8n

In n8n, go to Settings → Community nodes → Install and enter n8n-nodes-wiredesk. Self-hosted n8n needs community nodes enabled. See n8n’s installation guide.
2

Make an API key

In Wiredesk, go to Developers → API keys and make a key for n8n. Only owners and admins see the Developers section. Choose Read only if the workflows only read. The Wiredesk Trigger needs Full access, because it adds a webhook endpoint. See Authentication.
3

Connect your workspace

Add a Wiredesk node to a workflow. Under Credential, choose Create new, and paste the key. n8n checks it by listing your agents.

What it does

  • Agent fields list your workspace’s agents by name. You can also paste an ID or use an expression.
  • Get Many returns 50 items by default. Return All follows the API’s pages to the end.
  • Simplify, on by default, trims conversations, inbox items and knowledge sources to their ten most used fields, with the contact flattened into contact_name and contact_value. Turn it off to get everything the API returns.
  • Every Delete outputs one item, { "deleted": true }. Nodes added before version 0.1.2 of the package keep their earlier output, with no Simplify.
  • Send Message works as described in Talk to an agent. Pass back the conversation_id from the first reply to continue the conversation. Set User ID to your own ID for the person, so their conversations share one contact. It’s billed as a chat reply.
  • Knowledge Source → Create with a website returns the source pending while the site is crawled. Get Many shows when it’s ready.
  • Conversation → Export returns up to 25 conversations a page, each with its transcript. Return All follows the pages to the end.
  • Agent → Delete can be undone: an owner can restore the agent from the dashboard for 30 days.

Start a workflow from a Wiredesk event

The Wiredesk Trigger node starts a workflow the moment something happens in Wiredesk. It doesn’t check on a schedule.
1

Add the trigger

Add Wiredesk Trigger to a workflow and choose a credential with a Full access key. Pick the events: Conversation Ended, Handover Requested, Lead Captured or Message Created.
2

Activate the workflow

Activating it adds a webhook endpoint in Wiredesk for the workflow’s URL. You’ll see it under Developers → Webhooks, described as n8n: <node name>. Deactivating the workflow, or deleting it, removes the endpoint. Listen for test event in the editor adds a second endpoint for the test URL while it listens, and leaves the production one alone. If the endpoint was switched off in Wiredesk, for example after days of failed deliveries, the next activation replaces it.
3

Use the event

Each run gets the event’s type, its timestamp, its data with the same objects the API returns, and delivery_id. Webhooks lists what data holds for each event.
  • Wiredesk sends events only to https URLs on a public host, so an n8n on localhost needs a tunnel or a public URL (WEBHOOK_URL).
  • Every delivery is signed. The trigger checks the signature with the endpoint’s secret, which it keeps in the workflow, and refuses one that doesn’t match. A delivery more than five minutes old is refused too.
  • A workspace can have up to 10 webhook endpoints, and each active Wiredesk Trigger uses one. If you’ve reached 10, deactivate a workflow you no longer need or remove an endpoint you don’t use.
  • A message from the dashboard’s Send test event is answered but doesn’t start the workflow.
  • Phone and browser-voice transcripts aren’t sent line by line. Use Conversation Ended, then Conversation → Get Messages, to read them.

Errors

The node shows the API’s message, what to do about it, and the API’s error code, for example (Wiredesk code: read_only_key). The ones you’re most likely to see: Every request the node makes is in Developers → Logs, under the key’s name. See Request logs.