DevRev resolved tickets
The works export for tickets closed in the period: each ticket's id, close date and stage. Never a title, never a conversation, never a customer.
Access
- Kind
- A read-only key you paste
- What to give
- Personal access token
- Why that one
- A DevRev personal access token with ticket read. This source writes no spend: it reports what the spend produced.
What it attributes on its own
- From the source
- tickets resolved per day, at the moment each was closed · tickets reopened since, counted apart
- Needs a rule or a trace
- which tickets DevRev's own agents resolved — the public reference exposes no such field, so cost per resolved ticket is a floor on the cost per assisted one · the workflow, which you tell us · how hard a ticket was: a password reset and an escalation both count as one
The addresses it calls
- https://api.devrev.ai/works.export
Only these. A call anywhere else is refused before it leaves, and every call is logged.
Connecting it
- Create a personal access token. Settings → Account → Personal access token → New token. Name it so you recognise it later; it is shown once. Open ↗
- Name the workflow, paste the token, click Test and connect. Valistry reads the last seven days of closed tickets, reports how many, then fills thirty.
DevRev's AI cost arrives on its invoice, not through an API; upload the invoice and it joins these tickets by workflow.