Exportloop support and user guide

Contact: support@studiowebworks.com. We answer within two working days (Central European Time).

Getting started

A Zendesk administrator installs Exportloop from the Zendesk Marketplace.
Open Exportloop from the left navigation bar of the Agent Workspace.
Choose a view, or type a search; pick the columns, the comments option and the format; press Export. The file downloads when it is ready.

Agents see the views and tickets their own Zendesk role allows. Exportloop uses the signed-in agent's permissions and nothing more.

Views and searches

View: every ticket in the view, in the view's order.
Search: Zendesk search syntax, for example status<solved created>2026-01-01 tags:billing. Exportloop uses Zendesk's search export, so there is no 1,000-result limit. You do not need to add type:ticket.

Columns

Standard fields (ID, link, subject, description, status, priority, type, requester and email, submitter, assignee, group, organization, tags, channel, dates, satisfaction, external ID) and every active custom field. Dropdown fields show their labels, not their tags. Created, updated and due dates are real Excel dates in your computer's local time; custom date fields are exported as text (YYYY-MM-DD). Your choices are remembered in this browser for next time.

Comments

All comments in one column: each ticket's conversation in one cell, oldest first, marked internal where it applies.
One row per comment, on a second sheet: ticket ID, subject, date, author, author email, public or internal, and the text. Easy to filter and pivot.
Both, and optionally public replies only.

Comments need one request per ticket. Exportloop makes at most about 100 requests a minute, half of the smallest Zendesk plan's API limit, so other apps and integrations keep working. Expect about 10 minutes per 1,000 tickets with comments. On a Team plan, avoid running several large exports at the same time. Keep the page open until the file downloads; Cancel stops at once.

Limits

Excel holds 32,767 characters per cell; longer text is cut there and ends with "… [truncated]" (in CSV too, so the file opens the same in Excel).
Excel holds 1,048,576 rows per sheet; more comments continue on "Comments 2", "Comments 3" and so on.
CSV files contain the ticket sheet only (with comments in one column if chosen). Cells that start with =, +, - or @ are prefixed with an apostrophe so spreadsheet programs do not run them as formulas.
Very large exports (tens of thousands of tickets) are built in the browser's memory. Split them by date with a search if the browser runs short of memory.

Troubleshooting

"Zendesk asked us to slow down": your account hit its API limit, often because of another integration. Exportloop waits and carries on by itself.
"Zendesk refused access": your role cannot see that view or run that search.
"Zendesk could not run that search": check the search text in Zendesk's own search first.
"Too much data for one file in the browser": split the export, for example with searches by date (created>2026-01-01 created<2026-04-01).
No download appeared: use the Download … again link under the status line, or allow downloads for your Zendesk address in the browser.

Still stuck? Write to support@studiowebworks.com with what you exported and the message you saw. Please do not send ticket data.