Zapier
For the tool that is not on this page and never will be, there is Zapier. Review events become triggers and intake becomes an action, so you can wire Urengi into whatever your team actually runs without waiting for us to build it.
- Category
- Automation
- Auth method
- OAuth 2.0
- Direction
- Two-way
- Sync frequency
- Real time
- Scopes requested
- 4
- Available on
- Growth and Enterprise
- Maintained by
- Urengi
What the Zapier integration does
Three building blocks, and whatever you assemble from them.
Review events as triggers
A review opening, a tier changing or evidence arriving each fire a Zap, so the tool you care about hears about it without an integration existing.
Intake as an action
Any Zap can open a vendor review, which is how a form, a spreadsheet row or a purchase approval becomes the front door.
Scoped like any other connection
The Zapier connection carries the same scopes as a direct one, so a Zap cannot reach data a direct integration could not.
Exactly what Urengi can see
Four scopes, identical to a direct connection. A Zap inherits them and cannot widen them.
Urengi reads
- Review status, tier and vendor name
- Evidence item names and dates
- Reviewer display names and emails
- Records the connection itself created
Urengi writes
- New vendor intakes
- Evidence items on an existing review
- Comments recording an external action
Urengi never touches
- Evidence file contents
- Audit log entries or their history
- Account, billing or seat data
- Anything after you disconnect the app
Connect it in four steps
One authorisation, one field mapping, and a test sync you run yourself.
01
Authorise the connection
Open Zapier 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 Zapier token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Zapier 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 Zapier
- one click, no ticket
- EU or US residency
- chosen at signup