ClickUp's Call webhook Automation cannot trigger surveys through a Retently generic inbound webhook. The trigger itself fires correctly, but the task data never arrives in a form Retently can read. To automate surveys from ClickUp, use Zapier or Make as a connector.
Why it looks like it should work
ClickUp has an Automations feature, and one of the actions you can pick is Call webhook. On paper that is exactly what a Retently generic inbound webhook needs: an external service firing a request when something happens, for example a task status changing to Closed.
Setting up the ClickUp side also looks right. You paste the Retently webhook URL, and ClickUp offers a Content-type header already set to application/json.
Why it does not work
When you build the webhook in ClickUp, the task properties you want to pass along (Task ID, Task Name, Task Description, Creator Email, Date Closed, and the rest) are inserted into the Url field itself. ClickUp appends them to the end of the address as URL parameters. There is no field in the dialog where you compose a request body, and nothing you select ends up inside one.
The result looks like this, with the contact's email address and the task details sitting in the address rather than inside the request:
https://<your-retently-generic-webhook-url>?email=jane@example.com&taskId=86abc123&dateClosed=1757548800000
Retently's generic inbound webhook reads a JSON payload. That is how it finds the email address, matches your custom properties, and decides who to survey. See Contact data mapping via the generic inbound webhook for the format it expects.
Retently cannot parse values out of the webhook URL. Because ClickUp sends everything there instead of in a payload, Retently receives the request with no contact data attached, has no email address to survey, and nothing to map to your properties.
The application/json header in the ClickUp dialog does not change this. The header describes the request, but the task properties you selected are still in the address.
What to use instead
Put an automation platform between ClickUp and Retently. Both Zapier and Make list ClickUp as a trigger app and Retently as an action app, so the connector reads the ClickUp event and then sends Retently a properly formed request with your fields mapped.
Platform | ClickUp side | Retently side |
Zapier | Task Changes trigger, filtered to the status you care about | Retently action to create or update a contact, or send a transactional survey |
Make | ClickUp trigger module watching your tasks | Retently module to create or update a contact, or send a transactional survey |
Step-by-step setup for the Retently side:
Everything you configure inside the campaign still applies no matter which connector fires it. The delay before a survey goes out after the event, and the throttle that skips contacts surveyed recently, are both handled on the Retently side.
Related