We are setting up Retently NPS survey triggers based on ticket closure events in Zendesk, and I need the exact webhook payload structure.
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
We are setting up Retently NPS survey triggers based on ticket closure events in Zendesk, and I need the exact webhook payload structure.
3 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 3 queries…
Searches and sources
ChatGPT3 real searches · gpt-6
Retently Zendesk ticket closed webhook payload NPS survey trigger documentation Google ↗
site:help.retently.com Zendesk webhook ticket solved closed event payload Google ↗
Retently API create NPS response trigger webhook Zendesk Google ↗
- Retently CSAT Surveys & Agent Scorecards via Zendesk Integration · retently.com
- Retently CSAT Surveys & Agent Scorecards via Zendesk Integration · retently.com
- Retently API Documentation · retently.com
- About Zendesk triggers and how they work · support.zendesk.com
Queries
3 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Retently Zendesk ticket closed webhook payload NPS survey trigger documentation OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
site:help.retently.com Zendesk webhook ticket solved closed event payload OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Retently API create NPS response trigger webhook Zendesk OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |