Table: zendesk_ticket_audit - Query Zendesk Ticket Audits using SQL
A Zendesk Ticket Audit is a record of all updates and changes made to a given ticket within the Zendesk Support Suite. Each audit contains detailed information about the changes, including the author of the change, the timestamp of the change, and the specific changes made to the ticket. Zendesk Ticket Audits provide a comprehensive history of a ticket's lifecycle, facilitating transparency and accountability in customer support processes.
Table Usage Guide
The zendesk_ticket_audit
table provides insights into the changes and updates made to tickets within the Zendesk Support Suite. As a customer support representative or manager, explore audit-specific details through this table, including the author, the timestamp, and the specific changes made to a ticket. Utilize it to track ticket history, monitor changes, and ensure accountability in your customer support processes.
Examples
List all ticket audit rows
Explore which ticket audits have been performed, enabling you to understand when and by whom each ticket was modified, as well as the number of events associated with each modification. This can be useful for tracking changes and maintaining accountability in customer support situations.
select ticket_id, id, created_at, author_id, jsonb_array_length(events)from zendesk_ticket_audit;
select ticket_id, id, created_at, author_id, json_array_length(events)from zendesk_ticket_audit;
List all events associated with ticket audits
Explore all changes related to ticket audits, including the type of change and the old and new values, to better understand the sequence of events and actions taken. This can be useful for troubleshooting, auditing, or understanding the history of a ticket.
select ta.ticket_id, ta.id, e ->> 'id' as event_id, e ->> 'type' as type, e ->> 'field_name' as field_name, e ->> 'previous_value' as previous_value, e ->> 'value' as valuefrom zendesk_ticket_audit as ta, lateral jsonb_array_elements(ta.events) as e;
select ta.ticket_id, ta.id, json_extract(e.value, '$.id') as event_id, json_extract(e.value, '$.type') as type, json_extract(e.value, '$.field_name') as field_name, json_extract(e.value, '$.previous_value') as previous_value, json_extract(e.value, '$.value') as valuefrom zendesk_ticket_audit as ta, json_each(ta.events) as e;
List all events that changed tags
This query provides a way to track the changes made to event tags. It is useful in monitoring and auditing purposes, allowing users to identify and analyze alterations made to specific event tags.
select ta.ticket_id, ta.id, e ->> 'id' as event_id, e ->> 'type' as type, e ->> 'field_name' as field_name, e ->> 'previous_value' as previous_value, e ->> 'value' as valuefrom zendesk_ticket_audit as ta, lateral jsonb_array_elements(ta.events) as ewhere e ->> 'type' = 'Change' and e ->> 'field_name' = 'tags';
select ta.ticket_id, ta.id, json_extract(e.value, '$.id') as event_id, json_extract(e.value, '$.type') as type, json_extract(e.value, '$.field_name') as field_name, json_extract(e.value, '$.previous_value') as previous_value, json_extract(e.value, '$.value') as valuefrom zendesk_ticket_audit as ta, json_each(ta.events) as ewhere json_extract(e.value, '$.type') = 'Change' and json_extract(e.value, '$.field_name') = 'tags';
List all satisfaction rating events
Identify instances where customer satisfaction ratings have been recorded. This is useful for monitoring customer feedback and improving service quality.
select ta.ticket_id, ta.id, e ->> 'id' as event_id, e ->> 'type' as type, e ->> 'score' as scorefrom zendesk_ticket_audit as ta, lateral jsonb_array_elements(ta.events) as ewhere e ->> 'type' = 'SatisfactionRating'
select ta.ticket_id, ta.id, json_extract(e.value, '$.id') as event_id, json_extract(e.value, '$.type') as type, json_extract(e.value, '$.score') as scorefrom zendesk_ticket_audit as ta, json_each(ta.events) as ewhere json_extract(e.value, '$.type') = 'SatisfactionRating'
Schema for zendesk_ticket_audit
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
author_id | bigint | The user who created the audit. | |
created_at | timestamp with time zone | The time the audit was created. | |
events | jsonb | An array of the events that happened in this audit. | |
id | bigint | = | Unique identifier for the ticket update. |
metadata | jsonb | Metadata for the audit, custom and system data. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
subdomain | text | =, !=, ~~, ~~*, !~~, !~~* | The organization subdomain name of the Zendesk instance. |
ticket_id | bigint | = | The ID of the associated ticket. |
via_channel | text | How the ticket or event was created. Examples: "web", "mobile", "rule", "system". | |
via_followup_source_id | text | The id of a closed ticket when creating a follow-up ticket. | |
via_source_from | jsonb | Source the ticket was sent to. | |
via_source_ref | text | Medium used to raise the ticket. | |
via_source_to | jsonb | Target that received the ticket. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- zendesk
You can pass the configuration to the command with the --config
argument:
steampipe_export_zendesk --config '<your_config>' zendesk_ticket_audit