Manage support tickets with Zendesk

Databases
See all your support tickets and messages.
Overview

The Jet Admin Zendesk integration lets your app create, read, update and search Zendesk tickets, users and organizations, driven by the same tables, forms and record actions you already build in Jet. Whether a customer submits a support request, an agent needs to triage a queue, or a ticket needs escalating to another team, the whole workflow runs inside Jet, and every action is scoped by role and written to the audit log.

That covers what teams build on Zendesk first: support consoles that show a ticket next to the account and order it belongs to, triage queues with owners and next actions, and reporting dashboards tracking volume and response time. Because Jet reads your own database alongside Zendesk, every screen shows the ticket next to the customer, the subscription or the order it relates to, and nobody needs a Zendesk seat to work with it.

What you can do
Create ticket
Open a new Zendesk ticket from a Jet form or workflow, so a signup issue, a bug report or an inbound request becomes a ticket without anyone opening Zendesk.
Get ticket
Look up one ticket by ID and show its status, priority and history on the record page your support team already works in.
List tickets
Pull tickets into a Jet table with search, filters and pagination, for example everyone open in the last 24 hours or every ticket without an assignee.
Update ticket
Change status, priority, assignee or tags on a ticket from your app, so triage happens without a tab switch.
Add comment to ticket
Post a public or internal comment on a ticket from a Jet workflow, keeping the thread in Zendesk even when the reply started elsewhere.
Delete ticket
Remove a ticket when it was opened by mistake or merged elsewhere. Put it behind an approval step so it cannot happen on a single click.
Create user
Create a Zendesk end user or agent from a Jet form, so a new customer record and their support profile stay in sync.
Get user
Look up a requester or agent by ID and show their ticket history next to the account record.
List users
Pull Zendesk users into a Jet table filtered by role, organization or tag.
Update user
Write name, email or custom field changes back to Zendesk from your own database.
Create organization
Create a Zendesk organization from a Jet form when a new company account signs up.
List organizations
Show Zendesk organizations with their domain and tags, so an account view can group tickets by company.
List ticket comments
Read the full comment history on a ticket, public and internal, for a support console that doesn't require opening Zendesk.
Search tickets
Query tickets by any field with Zendesk's search syntax, for a filtered support queue built to match your workflow.
Use Cases
Scenario
What it looks like
Support console
Give agents one screen with the ticket, the requester's account and your own order or subscription data, so they can resolve issues without switching between Zendesk and your product's admin tools.
Ticket triage queue
Route new tickets by tag, priority or customer tier into a queue with owners and next actions, so nothing sits unassigned.
Customer 360 view
Show every open and past ticket next to the account, plan and billing status, combining Zendesk with your own database on one screen.
Internal escalation workflow
Let non-support teams like engineering or billing open and track tickets on a shared record without giving them a full Zendesk seat.
Self-service status page
Let a customer log in and see the status of their own tickets, with your branding, instead of checking their email for updates.
Support metrics dashboard
Track ticket volume, response time and backlog by team or tag, next to product usage or revenue data.

Key benefits

  • Support without extra seats. Let non-support teams view and act on tickets from your app, without paying for a Zendesk agent seat.
  • Tickets joined to your own data. Zendesk sits next to the Postgres, MySQL or Mongo you already use, so a ticket appears beside the account, order or subscription it belongs to.
  • Actions with limits and a record. Ticket updates, deletions and organization changes run inside your app, scoped by role, held for approval where you need it, and written to the audit log.
  • Custom triage and routing. Build a queue and routing logic that matches how your team actually works, instead of Zendesk's default views.
  • Complete workflows. Tie a new ticket to everything that follows it: notify the team, update a record, and escalate automatically.
  • Live support data on the screen. Show ticket status, comments and history as they stand right now, in both internal dashboards and customer-facing views.

How to connect Jet Admin with Zendesk

  1. In Zendesk, open Admin Center → Apps and integrations → APIs → Zendesk API and generate an API token.
  2. In Jet Admin, open your project and add a new resource, or pick Zendesk while creating a project.
  3. Choose Zendesk and enter your subdomain, email and API token.
  4. Jet loads your Zendesk objects: Tickets, Users, Organizations and Groups.
  5. Add the data sources you want to join with them, for example your own accounts or orders table.
  6. Generate the screens you need, then set role permissions on the records and fields each team can see.
  7. Add actions and workflows on top: ticket comments, status changes, and Slack or email alerts on new tickets.