QueueDeskDocs
Main website Go to dashboard
Documentation

Getting Started

  • Quickstart Guide
  • Workspace Setup
  • Inviting your Team
  • Export and Import

Ticketing & ITIL

  • Incidents vs Service Requests
  • Categories, Custom Fields & Ticket Numbering
  • SLA Rules & Priorities
  • Ticket Stages, On Hold & SLA Pause
  • Assignment Rules & Groups
  • Ticket List View & Canned Replies
  • Closure Rules, Approvals & CSAT Surveys
  • Merging Duplicates & Linking Major Incidents
  • Attachments & Screenshots
  • Agent Ticket Visibility

Service Catalog & Knowledge Base

  • Service Catalog
  • Knowledge Base
  • Writing Articles from Tickets

QueAssist (AI Copilot)

  • AI Triage & Categorization
  • Agentic Auto-Resolution
  • QueAssist Settings & Usage Quota
  • AI Agent Access — Connect Claude, Cursor & ChatGPT
  • No-Code Playbooks
  • Identity Scoping & Safety
  • How QueAssist Answers Each Department
  • Skills
  • Approve QueAssist Actions

Channels & Email

  • Email Forwarding Setup
  • Portal Mode — Forms vs AI Chat
  • Department Mailboxes
  • Departments on the Employee Portal

People & Identity

  • External Users
  • Single Sign-On & SCIM Directory Sync

Integrations

  • Connecting Integrations & Custom MCP Servers
  • Connect n8n, Zapier or Make Workflows

Billing & Plans

  • Billing & Plans
DocsIntegrationsConnect n8n, Zapier or Make Workflows

Connect n8n, Zapier or Make Workflows

Already automate things in n8n, Zapier or Make? QueAssist can run those workflows from a ticket. Each of these tools can publish a workflow as an MCP server, and QueueDesk connects to MCP servers as a custom MCP connection. You keep building the automation where you already do; QueueDesk decides when it runs and who approves it.

1. Publish the workflow as an MCP server

n8n:

1. Add an MCP Server Trigger node to a workflow.

2. Connect the nodes you want QueAssist to be able to call, for example Create mailbox or Order laptop. Each becomes a tool.

3. Under Authentication, choose Bearer auth and set a long random token.

4. Activate the workflow and copy the Production URL.

Zapier and Make: both offer an MCP server for your account. Create it, pick the actions to expose, and copy its URL and token.

The URL must be public HTTPS. QueueDesk refuses private and local addresses and does not follow redirects.

2. Add it to QueueDesk

1. Go to Settings → Integrations and click Add custom MCP server.

2. Give it a label (e.g. n8n — IT workflows), paste the URL, and paste the token as the secret.

3. Click Test connection. QueueDesk lists the tools the server reports.

3. Choose who acts on whom

For each tool:

  • •Identity field — which input holds the employee's email. QueueDesk fills it with the ticket's subject, so a workflow can never be pointed at someone else. Choose No identity needed only for tools that don't act on a person.
  • •Mode — set it to Needs approval to start. See Approve QueAssist Actions.

4. Use it

  • •On a ticket: QueAssist can ask to run the workflow when it fits, or an agent can click Plan with QueAssist.
  • •In a playbook: add a Run an integration tool step and pick the workflow. If it's set to Needs approval, the playbook pauses until an agent approves.

Every run appears in the ticket's activity timeline with its inputs and result.

Troubleshooting

  • •No tools listed — the workflow isn't active, or the MCP Server Trigger has no connected nodes.
  • •401 or 403 on test — the token in QueueDesk doesn't match the one in the trigger.
  • •Tool can't be switched on — choose its identity field first.