ClickUp task per testimonial
Turn New Testimonials Into ClickUp Tasks
A testimonial is work waiting to happen: someone has to read it, approve it, thank the customer and decide where it goes. If your content team plans that work in ClickUp, each new testimonial should appear there as a task. StoryProof sends every new review to your own tools by webhook, and Zapier or a small endpoint can turn each delivery into a task through ClickUp’s create task API.
- One task in a chosen List per new review
- ClickUp’s create task call, from its API docs
- A tracker with statuses the team already uses
ClickUp checklist
Create a task for every new review
Two routes: Zapier’s Catch Hook with a ClickUp task step, or your own endpoint calling ClickUp’s API. API details are from ClickUp’s developer reference and Zapier’s help, read on 2026-11-17.
Ticks stay in your browser. Do not type API tokens here.
The problem, solved
Turning testimonials into planned work
- Problem 1
Nobody is assigned to new testimonials
Without an owner, reviewing and reusing a testimonial is everyone’s job, which means nobody’s.
How StoryProof solves it
From Pro, webhooks send every new review to your own tools as it arrives, so each one can become an assignable ClickUp task.
- Problem 2
The task says approved, StoryProof does not
A ClickUp status does not publish anything. A team can mark a task done while the testimonial is still waiting.
How StoryProof solves it
Approval happens in StoryProof, where nothing goes public until approved. Move the task to approved only after that click.
- Problem 3
Thanking the customer falls through
The thank you is the first thing forgotten once the quote is on the site.
How StoryProof solves it
From Pro, the customer can get a thank-you email two hours after approval. Use the thanked status for a personal note on top, or skip it if the automation is on.
- Problem 4
Approved quotes never get used
Good testimonials get approved and then sit in a list, never reaching a page or a post.
How StoryProof solves it
You choose which approved testimonials appear in each widget, and the social image designer can turn one into a post image. The in use status records where.
- Problem 5
Two systems describe it differently
ClickUp tags and StoryProof tags drift apart, and searches stop matching.
How StoryProof solves it
Use the same names for tags in both places, so a testimonial tagged pricing in StoryProof is tagged pricing on its task too.
In StoryProof
Set it up
Step 1 of 4
Make the testimonial List
Create the List and statuses in ClickUp and note its list id.
Step 2 of 4
Catch the webhook
Create the Catch Hook or endpoint, add its URL where StoryProof lists webhooks, and send a test review.
Step 3 of 4
Create a task per delivery
Map values from the real test delivery into the task name and description, and set the tag.
Step 4 of 4
Close the loop in StoryProof
When a task reaches approved or not for use, make the same decision in StoryProof so the two agree.
Before you start
Limits to know
No native ClickUp integration
StoryProof is not claimed to connect to ClickUp. The webhook, plus Zapier or your endpoint, is the only link.
ClickUp’s webhook automations point outward
Search summaries of ClickUp’s help describe its webhook automations as sending task events to other apps, not receiving them. That is why a middle step is needed.
Payload not documented here
Field names, event names, retries and signatures are not described. Map only what a test delivery shows you.
One way only
Moving a task in ClickUp changes nothing in StoryProof, and approving in StoryProof does not move the task.
Vendor steps as of 2026-11-17
ClickUp and Zapier details follow their docs as read on 2026-11-17 and have not been run on a live account by us.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can ClickUp receive the webhook without Zapier?
Not as far as we found: ClickUp’s webhook automations, as summarised in search results, send data out. Use a small endpoint that calls ClickUp’s create task API, or a middleware tool.
Should low ratings become tasks too?
Probably not in a content List. Route those to support instead, and keep this List for testimonials you might reuse.
Can we set a due date?
ClickUp’s create task call accepts a due date. A common choice is a few days after arrival, so nothing waits too long for review.
What about Asana, Trello or monday?
The same pattern works: catch the webhook, create an item. Follow that tool’s own docs for the create step.
Still have a question? Ask the StoryProof team or book a demo.
Give every testimonial a next step
Collect testimonials in StoryProof and send each new one to the ClickUp List your team already works from.
Sources
- API reference: Create Task, ClickUp developer docs. Checked 2026-11-17.
- Trigger Zaps from webhooks, Zapier. Checked 2026-11-17.
- Create a task webhook Automation, ClickUp Help Center. Checked 2026-11-17.
Last updated 2026-11-17.