Zendesk
Half of vendor risk arrives as a support ticket — a customer asking who processes their data, or a colleague asking whether a tool is approved. Urengi turns those into intake requests instead of letting them die in a queue.
- Category
- Ticketing & work
- Auth method
- OAuth 2.0 or API token
- Direction
- Two-way
- Sync frequency
- Real time
- Scopes requested
- 4
- Available on
- Growth and Enterprise
- Maintained by
- Urengi
What the Zendesk integration does
Three jobs that stop a support queue from being a shadow intake form.
Tagged tickets become intake
A ticket tagged vendor-review opens an Urengi intake with the requester and the tool already filled in. The agent does not retype anything.
Answers come from the review
"Is this vendor approved, and at what tier?" is answered from the live review, as an internal note. Agents stop guessing on behalf of security.
The ticket closes when the review does
Sign-off posts back as a public reply and resolves the ticket, so the person who asked finds out without chasing.
Exactly what Urengi can see
Four scopes limited to the tags and views you name. Urengi does not read your whole queue.
Urengi reads
- Tickets carrying the tags you selected
- Requester display names and emails
- Ticket status and tag names
- Tickets Urengi itself created
Urengi writes
- Internal notes carrying review status
- Public replies on sign-off
- Tags and status on the tickets it touches
Urengi never touches
- Tickets outside the selected tags or views
- Attachments or their contents
- End-user records or organisation data
- Anything after you revoke the token
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Zendesk from this page and approve the scopes listed above — OAuth in a browser tab, or a scoped API key you paste. An admin approves them once.
02
Choose what syncs
Pick the projects, spaces or accounts Urengi should watch. Narrow is fine to start with; widening it later does not re-authorise anything.
03
Map your fields
Match owners, cost centres and tiers to what Urengi already tracks. Defaults arrive pre-filled from the first sync, so most teams change nothing.
04
Run a test sync
Pull one record and check it landed on the right review. The audit entry confirms the mapping before a real vendor is touched.
Your token, your rules.
Urengi stores the Zendesk token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Zendesk and every Urengi write stops within seconds — the audit log keeps the history, the connection simply ends.
Read the security statement- SOC 2 Type II
- audited annually
- Per-tenant keys
- no shared secrets
- Revocable in Zendesk
- one click, no ticket
- EU or US residency
- chosen at signup