Zendesk OAuth

Live

OAUTH 2.0

CUSTOMER SUPPORT

Customer Support

Connect to Zendesk OAuth to manage tickets, users, organizations, and support workflows from your AI agent pipelines using Zendesk's customer service platform.

  • Acts as the user: Every tool call runs as the authorizing user. Access and audit trail stay intact.
  • Credentials stay vaulted: AES-256 encrypted, resolved at request time, never stored in LLM context.
  • Scoped before every call: Per-user permissions enforced automatically. 90-day audit trail included.
Zendesk OAuth
agent · Acme Q3
Run
Groups List in Zendesk (OAUTH)
S
zendeskoauth_groups_list
85ms
Zendesk (OAUTH) agent
List all groups in zendesk. groups are used to organize agents and route tickets..
Sources: Zendesk (OAUTH)
zendeskoauthmcp
1 tool call
18:29
Message Claude...

Zendesk OAuth tools for AI agents

CALL ANY TOOL
12 tools covering create, get, list.
zendeskoauth_search_tickets
Search tickets
Search Zendesk tickets using a query string. Supports Zendesk's search syntax (e.g., 'type:ticket status:open'). Zendesk limits search results to 1,000 total : the maximum valid page is floor(1000 / per_page) (e.g., per_page=100 → max page 10, per_page=25 → max page 40). Stop paginating when next_page is null or you reach the max page; requesting beyond the limit returns a 400 error.
Parameters
Name
Type
Required
Description
query
string
Required
Search query string using Zendesk search syntax (e.g., 'type:ticket status:open assignee:me')
include
string
Optional
Comma-separated list of additional data to sideload with results. Supported values: users, groups, organizations, tickets.
page
number
Optional
Page number for pagination. Max valid page = floor(1000 / per_page). Do not exceed this : Zendesk returns a 400 error beyond the 1,000 result limit.
per_page
number
Optional
Number of results per page (max 100). Determines the max page ceiling: floor(1000 / per_page). Higher values mean fewer pages but a lower max page number.
sort_by
string
Optional
Field to sort results by (updated_at, created_at, priority, status, ticket_type)
sort_order
string
Optional
Sort direction: asc or desc (default: desc)
zendeskoauth_user_get
User get
zendeskoauth_tags_list
Tags list
zendeskoauth_view_get
View get
zendeskoauth_users_list
Users list
zendeskoauth_brand_get
Brand get
zendeskoauth_views_list
Views list
zendeskoauth_group_get
Group get
zendeskoauth_brands_list
Brands list
zendeskoauth_macro_get
Macro get
zendeskoauth_groups_list
Groups list
zendeskoauth_ticket_get
Ticket get
zendeskoauth_macro_apply
Macro apply
zendeskoauth_macros_list
Macros list
zendeskoauth_request_get
Request get
zendeskoauth_user_create
User create
zendeskoauth_trigger_get
Trigger get
zendeskoauth_user_delete
User delete
zendeskoauth_user_update
User update
zendeskoauth_view_create
View create
zendeskoauth_view_delete
View delete
zendeskoauth_view_update
View update
zendeskoauth_webhook_get
Webhook get
zendeskoauth_group_create
Group create
zendeskoauth_group_delete
Group delete
zendeskoauth_group_update
Group update
zendeskoauth_guide_search
Guide search
zendeskoauth_macro_create
Macro create
zendeskoauth_macro_delete
Macro delete
zendeskoauth_macro_update
Macro update
Build your Agent
Same auth pattern across every framework.
Python · LlamaIndex
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="zendeskoauth")

mcp = MultiServerMCPClient({
"zendeskoauth": {
"url": "https://mcp.scalekit.com/zendeskoauth",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "zendeskoauth" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/zendeskoauth
// Pass: Authorization: Bearer + token
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "zendeskoauth" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/zendeskoauth
// Pass: Authorization: Bearer + token
from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="zendeskoauth")
# Connect to MCP at https://mcp.scalekit.com/zendeskoauth
# Pass: Authorization: Bearer + token
Try these prompts
Paste any prompt into your agent to get started.
Get started
Copy the prompt
Copied
Create a section under a Help Center category?
Copy the prompt
Copied
Retrieve details of a specific Zendesk ticket by ID?
Advanced
Copy the prompt
Copied
List all groups in Zendesk?
Copy the prompt
Copied
Update article-level metadata: promoted status, position, comments setting, labels, and content tags?
SEE HOW AUTH WORKS
User authorises once. Every agent call after uses their token with scope enforcement.
1
Authorize
Your user connects
Zendesk OAuth
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Zendesk OAuth
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Zendesk OAuth
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Zendesk OAuth
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern across other connectors.
Support and Ops Teams
Support triage agent
Fetches new Zendesk tickets, classifies them by type and urgency, searches the Notion knowledge base for an answer, and routes what it cannot resolve to Slack. Every call runs on the support agent's own delegated OAuth.
Support and Ops Teams
Support ticket automation agent
Fetches new Zendesk tickets, drafts a reply from Notion knowledge base articles, digests what it cannot answer to Slack, and archives the rest, acting as the support agent rather than a shared API key.
Support and Ops Teams
Freshdesk CSAT agent
Watches Freshdesk for resolved tickets, emails each requester a CSAT survey from Gmail, and writes the score and the verbatim back onto the ticket, every call on the support rep's own delegated OAuth.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Test other agents
See the same per-user auth pattern across other connectors.
SUPPORT
Support triage agent
Classify new Zendesk tickets, search the Notion knowledge base for an answer, and route what it cannot resolve to Slack.
SUPPORT
Support ticket automation (Google ADK)
Fetch, annotate, and archive Zendesk tickets with Notion context, digesting anything it cannot answer to Slack.
SUPPORT
Freshdesk CSAT follow-up agent
Spot resolved Freshdesk tickets, email the CSAT survey from Gmail, and write the score back onto the ticket.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.
// shared token
audit → bot_service_account

// scalekit
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
One connector today. Ten tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions

Does the agent access Zendesk OAuth as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Zendesk OAuth OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Zendesk OAuth?
Yes. Pass a tool name filter to listScopedTools so the support agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Zendesk OAuth.

What happens when a user revokes Zendesk OAuth access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent publish or archive Help Center articles?
Only if the authorizing user has Guide admin rights. Article create, comment, and archive tools run with the user's Zendesk role, so Help Center changes always trace to a real editor.

Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""zendeskoauth"": {
""url"": ""https://mcp.scalekit.com/zendeskoauth"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.zendeskoauth]
url = ""https://mcp.scalekit.com/zendeskoauth""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""zendeskoauth"": {
""url"": ""https://mcp.scalekit.com/zendeskoauth"",
""type"": ""http""
}
}
}