Tables in Zendesk

The zendesk plugin includes 8 tables:

Name	Description	Queries
zendesk_brand	Brands are your customer-facing identities. They might represent multiple products or services, or they might literally be multiple brands owned and represented by your company.	1
zendesk_group	When support requests arrive in Zendesk Support, they can be assigned to a Group. Groups serve as the core element of ticket workflow; support agents are organized into Groups and tickets can be assigned to a Group only, or to an assigned agent within a Group. A ticket can never be assigned to an agent without also being assigned to a Group.	1
zendesk_organization	Just as agents can be segmented into groups in Zendesk Support, your customers (end-users) can be segmented into organizations. You can manually assign customers to an organization or automatically assign them to an organization by their email address domain. Organizations can be used in business rules to route tickets to groups of agents or to send email notifications.	4
zendesk_search	Search results for the given query.	4
zendesk_ticket	Tickets are the means through which your end users (customers) communicate with agents in Zendesk Support. Tickets can originate from a number of channels, including email, Help Center, chat, phone call, Twitter, Facebook, or the API. All tickets have a core set of properties.	5
zendesk_ticket_audit	Audits are a read-only history of all updates to a ticket. When a ticket is updated in Zendesk Support, an audit is stored. Each audit represents a single update to the ticket. An update can consist of one or more events.	4
zendesk_trigger	A trigger consists of one or more actions performed when a ticket is created or updated. The actions are performed only if certain conditions are met. For example, a trigger can notify the customer when an agent changes the status of a ticket to Solved.	3
zendesk_user	Zendesk Support has three types of users: end users (your customers), agents, and administrators.	4