Skip to main content
Glama
JurreBrandsenInfoSupport

Zendesk API MCP Server

delete_trigger

Remove a trigger from Zendesk Support by specifying its ID to streamline automation rules and ticket workflows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTrigger ID to delete

Implementation Reference

  • The handler function that executes the 'delete_trigger' tool logic. It calls the zendeskClient.deleteTrigger(id) and handles the response or error.
    handler: async ({ id }) => { try { await zendeskClient.deleteTrigger(id); return { content: [{ type: "text", text: `Trigger ${id} deleted successfully!` }] }; } catch (error) { return { content: [{ type: "text", text: `Error deleting trigger: ${error.message}` }], isError: true }; } }
  • Zod schema defining the input parameter 'id' for the delete_trigger tool.
    schema: { id: z.number().describe("Trigger ID to delete") },
  • src/server.js:31-52 (registration)
    Registration of all tools including 'delete_trigger' via the triggersTools array imported earlier. The forEach loop calls server.tool for each tool.
    const allTools = [ ...ticketsTools, ...usersTools, ...organizationsTools, ...groupsTools, ...macrosTools, ...viewsTools, ...triggersTools, ...automationsTools, ...searchTools, ...helpCenterTools, ...supportTools, ...talkTools, ...chatTools, ]; // Register each tool with the server allTools.forEach((tool) => { server.tool(tool.name, tool.schema, tool.handler, { description: tool.description, }); });
  • Supporting utility function in ZendeskClient that performs the actual DELETE request to the Zendesk Triggers API endpoint.
    async deleteTrigger(id) { return this.request("DELETE", `/triggers/${id}.json`); }

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/JurreBrandsenInfoSupport/zendesk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server