The Scenario
A Zendesk consultant handed you a project brief on Monday morning: document the complete ticket schema for a client's Zendesk account before the implementation review on Thursday. That means every custom ticket field — API name, display label, field type, and all dropdown options for picklist fields. The client has 35 custom fields. The consultant has none of them documented.
The bad version:
- Open Zendesk Admin, navigate to Ticket Fields.
- Click field 1. Note the API name. Note the display name. Note the type. If it's a dropdown, open the options list and copy each one.
- Go back. Click field 2.
- At field 18, realize that two of the dropdown fields have hundreds of options and you've been copying them one by one.
Schema documentation is foundational — every downstream integration, automation, and report depends on it being correct. Doing it manually through the admin UI is how you end up with documentation that covers 28 of the 35 fields and gets shelved before it's finished.
The Easy Way: One Prompt in SheetXAI
SheetXAI is an AI agent inside your Google Sheet. It uses the Zendesk integration to pull every custom field definition in one operation.
Open the SheetXAI sidebar in your schema documentation sheet and paste:
List all Zendesk ticket fields and write them into this sheet with field ID, API name, title, type, required status, and picklist options
What You Get
- One row per custom ticket field.
- Field ID, API name, display title, field type, and required status in columns A through E.
- All dropdown options for picklist fields written as a comma-separated list in column F.
35 fields documented, including every dropdown option, without clicking through a single field page.
What If the Data Is Not Quite Ready
You want dropdown options on separate rows for easier filtering
List all Zendesk ticket fields and write field ID, API name, title, and type to this sheet. For each dropdown or multi-select field, write each option on its own row with the field ID repeated in column A
One row per option for fields that need it, repeated field ID for easy grouping.
You only need custom fields, not system fields
List all custom Zendesk ticket fields — excluding system fields like status, priority, and assignee — and write field ID, API name, title, type, and options to this sheet
System fields filtered out of the documentation sheet.
You need to separate required vs. optional fields for the implementation review
List all Zendesk ticket fields and write field ID, API name, title, type, and options to this sheet. Put required fields in the 'Required Fields' tab and optional fields in the 'Optional Fields' tab
Two-tab split that matches how the implementation review team wants to think about the schema.
Full schema documentation package
List all Zendesk ticket fields and write to the 'All Fields' tab — field ID, API name, title, type, required status, and all options. On the 'Summary' tab, write counts of fields by type (text, dropdown, checkbox, etc.) and the total count of required vs. optional fields
Complete field inventory plus type-distribution summary — one prompt, implementation review ready by Wednesday.
Try It
Get the 7-day free trial of SheetXAI and open your schema documentation sheet, then export the full field list. Related: export triggers to document the automation layer that uses these fields, or return to the Zendesk integration guide.