Zendesk
What Paperbeam reads from Zendesk, the read-only access it asks for and why, filters, and the beats it feeds.
Support
Read-only API key
Tickets solved, satisfaction ratings and customer comments from Zendesk.
What we read
- Support conversations and satisfaction ratings
Only the reporting window of each edition is read. Paperbeam stores derived facts and short excerpts, not copies of your Zendesk data, and keeps raw evidence only for your retention period.
Access we ask for, and why
| Scope | Why |
|---|---|
read | Read solved tickets, satisfaction ratings and organizations |
All access is read-only. You can revoke it from Zendesk at any time, or disconnect the source in Paperbeam.
Connect Zendesk
- Go to Sources and choose Zendesk.
- Create a api token. Admin Center → Apps and integrations → APIs → Zendesk API → enable token access, then Add API token. Open Zendesk settings.
- Fill in Subdomain, Email and API token, then click Test connection. Paperbeam makes one read-only call and shows the account it reached, or exactly what went wrong.
- Click Connect. The credential is encrypted before it is stored and never shown again. Use Sync now on the source’s page to see what it collects from the last 24 hours, and set filters there.
You need the admin or owner role in Paperbeam, and enough permission in Zendesk to grant read access to the data listed above.
Filters
Set on the source’s page at Sources›Zendesk. Filtered-out data is never collected.
| Filter | Effect |
|---|---|
| Satisfaction ratings | Attach CSAT ratings and comments to solved tickets. |
To keep specific people, channels or topics out of the paper across all sources, use exclusion rules and the never-mention list in House style.
Beats
Zendesk is a source for:
Stories land in whichever of your sections fits them best.