Zendesk triggers
Zendesk Solved Ticket Review Requests
Zendesk already knows when a ticket is solved, and its triggers can notify any webhook. From Pro, a StoryProof automation has an inbound URL for exactly that. This page wires the two together; when to ask and what to say after support are covered elsewhere.
- A Zendesk webhook connected by Trigger or Automation
- A Notify webhook action with a small JSON body
- Leaving room for the ticket to reopen before asking
Admin Center checklist
Zendesk webhook to StoryProof, in Admin Center order
Every Zendesk item follows Zendesk’s help article on webhooks. You need admin rights, or a custom role allowed to create webhooks.
This checklist runs in your browser and saves nothing.
The problem, solved
From solved ticket to request without an agent
- Problem 1
Agents copy emails into another tool
Manual hand offs happen on quiet days and vanish on busy ones.
How StoryProof solves it
From Pro, each automation has a secure URL. A Zendesk trigger notifies it on solve, so no agent is involved.
- Problem 2
The customer replies and the ticket reopens
Zendesk reopens a solved ticket when the customer replies, so a fast ask can land on a problem that is not over.
How StoryProof solves it
A wait of days between the webhook and the request gives reopen time to pass.
- Problem 3
Heavy users raise a ticket a week
Your most active customers would be asked constantly.
How StoryProof solves it
The review request action skips anyone who already reviewed or was asked recently.
- Problem 4
A low rating comes back from support
Some solved tickets still leave the customer unhappy, and they say so.
How StoryProof solves it
A separate automation can alert your team and send a personal apology when a review of 2 stars or fewer arrives.
- Problem 5
We do not know which message works after support
Support customers respond differently from buyers.
How StoryProof solves it
A percentage split sends people down two paths so you can test two follow-ups against each other.
A small Notify webhook body
Illustrative sample. Insert Zendesk’s own placeholders from its placeholder list; check the keys against what your automation shows.
Keep the body to the two things the automation needs: the requester’s email and their name. Zendesk inserts ticket data through placeholders written in double curly brackets.
Leave out ticket comments. They can contain personal or account details that StoryProof does not need, and the body is capped at 16,000 characters.
- requester email placeholder
- name
- requester name placeholder
- source
- zendesk (a fixed value, so you can tell runs apart)
In StoryProof
The order that avoids rework
Step 1 of 4
Build the automation and copy the URL
Inbound webhook trigger, a wait, the review request.
Step 2 of 4
Create the Zendesk webhook
Trigger or Automation connection, the automation URL, JSON, and authentication if needed.
Step 3 of 4
Write the trigger
Status changed to Solved, your exclusions, and a Notify webhook action with a short JSON body. Then Finish setup.
Step 4 of 4
Solve your own ticket
The run is real. Confirm it in the automation log, then publish.
Before you start
What the integration does not do
No Zendesk app
StoryProof does not appear in Zendesk or read tickets. It only receives what your trigger sends.
No satisfaction filter from StoryProof
StoryProof cannot see the ticket’s outcome. Any condition about which tickets qualify belongs in the Zendesk trigger.
Placeholders are Zendesk’s
This page does not list placeholder names. Use Zendesk’s placeholder reference, then check the fields the automation shows from your sample.
One request per address
The skip rule works per contact, so tickets raised from a shared inbox count as one person.
Docs, not a live instance
Zendesk steps follow its help center as of 2026-11-18 and were not clicked through in a live account.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should the trigger fire on Solved or Closed?
Build on Solved. Zendesk’s default automation closes a solved ticket four days later, and after that a customer reply opens a follow up ticket rather than reopening it. Let the StoryProof wait cover that window.
Can I use Zapier instead of a Zendesk webhook?
Yes, if you prefer to keep the logic in a Zap. The Zendesk webhook route avoids a second paid tool.
How do I test without a customer?
Zendesk’s Test webhook option sends a request you write by hand. Use your own email in it, because StoryProof will act on it for real.
Will customers think the support agent sent it?
The request comes from StoryProof with your collection link. Mentioning the support case in the wording makes the link clear.
Still have a question? Ask the StoryProof team or book a demo.
Let solved tickets ask for you
Create the automation, then point a Zendesk trigger at it.
Sources
- Creating webhooks to interact with third-party systems, Zendesk Help. Checked 2026-11-18.
- Using placeholders, Zendesk Help. Checked 2026-11-18.
- What is the difference between a solved ticket and a closed ticket?, Zendesk Help. Checked 2026-11-18.
Last updated 2026-11-18.