Asana
Renewal work lands in the procurement project as a task with an owner and a due date, timed against the certificate that is about to expire. The review reopens itself, and the task is what makes that visible to the people who have to act on it.
- Category
- Ticketing & work
- Auth method
- OAuth 2.0
- Direction
- Two-way
- Sync frequency
- Hourly
- Scopes requested
- 4
- Available on
- All plans
- Maintained by
- Urengi
What the Asana integration does
Three jobs, all of them calendar work somebody currently keeps in their head.
Renewals as dated tasks
A SOC 2 report expiring in March produces a February task, assigned to the vendor owner. Nothing depends on anyone remembering the date.
The checklist travels with it
Each task carries the evidence still outstanding as subtasks, so the person picking it up can see what is actually missing.
Completing it closes the loop
Marking the task complete records who signed off and when, and the review reflects it without a second update.
Exactly what Urengi can see
Four scopes on the projects you name. Urengi cannot see a project you did not select.
Urengi reads
- Project and section names
- Task names Urengi itself created
- Member display names and emails
- Custom field names used for tiers
Urengi writes
- Renewal and review tasks in selected projects
- Assignees, due dates and subtasks on those tasks
- Comments carrying evidence updates
Urengi never touches
- Tasks in projects you did not select
- Attachments or their contents
- Portfolios, goals or workload 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 Asana 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 Asana token encrypted at rest under a per-tenant key and never replays it outside the scopes you approved. Revoke the app in Asana 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 Asana
- one click, no ticket
- EU or US residency
- chosen at signup