Zendesk
Tickets, SLAs, and agent workflows on Zendesk
Zendesk's job is the ticket lifecycle, Tiny Command lets you wire that lifecycle into everywhere else without leaving the agent context behind. Six triggers cover the events that drive SLAs and team rituals: Ticket Created (new inbound), Ticket Updated (any field changes including status), Ticket Solved (resolution moment that triggers downstream reporting), Ticket Assigned (handoff to a specific agent or group), Ticket Commented (response or internal note), and User Created (new requester). Seventeen actions cover the operational surface: Create Ticket, Update Ticket, Delete Ticket, Add Comment to Ticket, Create User, Update User, Delete User, Create Organization, plus the read endpoints for tickets, users, organizations, and groups, and a Search Tickets / Search Users that supports Zendesk's full query syntax. The integration authorizes via Zendesk's OAuth and respects agent permissions. Common patterns: Ticket Solved triggers a CSAT survey via Typeform, a high-priority Ticket Created pings the on-call rotation in Slack, and Ticket Updated with a tag-change syncs the categorization to HubSpot for customer-success visibility.
Workflows start when Zendesk does.
6 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a ticket is assigned (or reassigned) to an agent in Zendesk. Use to ping the assignee, start an SLA clock, or audit workload balance.
Fires when a comment (public or internal) is added to a Zendesk ticket. Common use: notify Slack of customer replies, log activity, or mirror conversations into a CRM.
Fires when a new support ticket is created in Zendesk, across any channel (email, web form, chat, API, social). The standard inbound hook for AI triage and routing.
Fires when a ticket is marked solved in Zendesk. Common use: kick off CSAT surveys, log resolution to CRM, or run an AI quality-of-resolution check.
Fires whenever any field on a Zendesk ticket changes (status, priority, assignee, group, tags, custom fields). Combine with field filters to react only to the changes you care about.
Fires when a new user (end-user or agent) is created in Zendesk. Use to enrich the user, sync into your CRM, or auto-add to an organization.
Do anything Zendesk can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Add Comment to Ticket | Adds a public comment (customer-visible) or internal note to an existing Zendesk ticket. Used for AI summary notes, automated status broadcasts, or piping context from external systems. |
| Create Organization | Creates an organization (B2B account) in Zendesk with name, domains, tags, and custom fields. Used to mirror CRM accounts into Zendesk so end-users auto-link by email domain. |
| Create Ticket | Creates a new support ticket in Zendesk with requester, subject, comment body, priority, status, type, group, assignee, and tags. The entry point for converting external alerts or forms into trackable tickets. |
| Create User | Creates a new user (customer or agent) in Zendesk with name, email, role, organization, and tags. Used to provision users before ticket creation or to mirror your auth system. |
| Delete Ticket | Permanently deletes a Zendesk ticket by ID. Two-step: this marks it deleted; for PII purposes you may also need to "redact" comments separately. |
| Delete User | Deletes a user from Zendesk by ID. Two-step: soft-delete first; pass permanently=true (or use the dedicated permanently-delete endpoint) for GDPR right-to-delete. |
| Get Ticket | Retrieves a Zendesk ticket by ID with subject, requester, status, priority, group, assignee, and custom fields. The standard read after a trigger fires with an ID. |
| Get Ticket Comments | Returns all comments and replies on a Zendesk ticket in chronological order, with public/internal flag and author. Used to feed AI summaries or build transcript exports. |
| Get User | Retrieves a Zendesk user by ID with email, role, organization, tags, and user fields. Used to enrich trigger payloads or render user UI. |
| List Groups | Lists all agent groups in Zendesk. Used to populate a group picker for routing rules or for permissions reporting. |
| List Organizations | Lists organizations in Zendesk with their domains and tags. Used for B2B account-level reporting and CRM sync. |
| List Tickets | Retrieves a paginated list of Zendesk tickets. For complex filters or older tickets, use Search Tickets; this action returns the unfiltered queue with cursor pagination. |
| List Users | Lists users in Zendesk, optionally filtered by role (end-user, agent, admin). Used for directory exports or for sync into your auth/CRM system. |
| Search Tickets | Searches for tickets using Zendesk's search query syntax (status:, assignee:, type:, tags:, created>). Powers SLA dashboards, segment reports, and upsert lookups. |
| Search Users | Searches for users in Zendesk by email, name, phone, organization, or tags. The standard upsert lookup before deciding to create or update. |
| Update Ticket | Updates an existing Zendesk ticket: status, priority, assignee, group, tags, custom fields, or add a new comment. The standard hook to reflect downstream actions back into the helpdesk. |
| Update User | Updates an existing Zendesk user's name, email, role, organization, tags, or user fields. Only the fields you pass are changed. |
Pre-built Zendesk workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Zendesk once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Zendesk field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Zendesk integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Zendesk to Tiny Command?
What Zendesk triggers does Tiny Command support?
What Zendesk actions can I run from a workflow?
Is the Zendesk integration real-time?
Do I need to write code to use Zendesk with Tiny Command?
How much does the Zendesk integration cost?
More customer support apps people connect.
Same category as Zendesk, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Zendesk.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
