Zendesk · Support
ZENDESK_CREATE_TICKET
Create a Zendesk ticket. Use only after explicit user approval. Returns the created ticket { id, subject, status, priority }.
- Provider
- Zendesk
- Access
- Write
- Category
- Support
- Version
- v1
Input schema
{
"type": "object",
"properties": {
"subject": {
"type": "string",
"description": "Ticket subject line."
},
"body": {
"type": "string",
"description": "First comment / description body."
},
"priority": {
"type": "string",
"enum": [
"urgent",
"high",
"normal",
"low"
],
"description": "Optional priority."
}
},
"required": [
"subject",
"body"
],
"additionalProperties": false
}How to call it
Expose this tool to any MCP-capable agent (Claude, GPT, or your own) through CybrLink's MCP server. The agent calls zendesk_create_ticket with arguments matching the schema above.
CybrLink validates the input, injects the connected Zendesk credentials server-side, and runs a single scoped provider API call through the shared proxy — the same guarded path as the generic call_api tool. The raw secret never reaches the model, and the response is trimmed to just the fields the agent needs.
Write action — gate behind explicit user approval and write scope.
Frequently asked
- How do I let an AI agent zendesk create ticket?
- Connect Zendesk to CybrLink, then expose the `zendesk_create_ticket` tool to any MCP-capable agent (Claude, GPT, or a custom framework). The agent calls it with typed arguments; CybrLink injects the Zendesk credential server-side and runs one scoped API call. Create a Zendesk ticket. Use only after explicit user approval. Returns the created ticket { id, subject, status, priority }.
- Does the AI model see my Zendesk credentials when using ZENDESK_CREATE_TICKET?
- No. CybrLink stores the credential in a token vault and injects it on the server for each call, so the model can take this action in Zendesk without the OAuth token or API key ever entering its context.