What the dry run checks
The add-on checks required fields, email format, supported dropdown values, custom-field types and matching ambiguity using the connected Zendesk account. The preview distinguishes proposed creates and updates and shows blocked rows, errors and warnings. These checks reduce avoidable errors; they cannot guarantee that a later API request will succeed.
Use the generated template and current lists
Generate a template for Users, Organizations or Tickets rather than guessing the column names. Refresh live Zendesk lists before validating. A template copied from another account can contain organization IDs, ticket forms or custom-field options that are not valid in this account.
Review both the row notes and the summary
A clean summary is only useful if it matches the change you intended. Inspect cell notes and confirm the number of new records versus updates. Resolve ambiguous matches, duplicates and unexpected field values. Begin with a small, reviewed batch in your own test environment before applying a large production import.
Understand the boundary between validation and writing
Validate rows is the dry run. Push valid rows sends the reviewed records to Zendesk. Account permissions, rate limits, configuration changes and provider errors can still affect that write. Check the result of each row and use the Activity Log to reconcile what actually happened.
Keep a recovery record
Save the original values and a source identifier before updating existing records. This product records results; it does not promise a one-click rollback of every Zendesk change. For jobs that remain processing, check their existing status before sending the same batch again.
Try the workflow in your sheet
See installation, pricing and requirements. For the next step, read How to bulk update Zendesk users from Google Sheets.