· 4 min · TextMeFlow Team

Send WhatsApp Notifications from ClickUp with Webhooks

ClickUp has no built-in WhatsApp integration, but it does have its own webhook API that can fire an HTTP request on almost every action on a task: a status change, a new task, an updated deadline or an assigned team member. Combine that with the TextMeFlow API and within minutes you're sending a WhatsApp message to a customer or colleague as soon as something changes in a task.

This article shows the shortest route: ClickUp → your own webhook receiver → the TextMeFlow API. No Zapier or Make needed, although you can use those tools if you'd rather not maintain your own endpoint.

Creating a ClickUp webhook

ClickUp has no button in the UI to register a webhook — you have to do it through the API itself. You send a POST to https://api.clickup.com/api/v2/team/{team_id}/webhook with your ClickUp API token, the URL of your receiver and the events you want to react to:

curl -X POST "https://api.clickup.com/api/v2/team/123456/webhook" \
  -H "Authorization: $CLICKUP_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "endpoint": "https://jouw-domein.be/webhooks/clickup",
    "events": ["taskStatusUpdated", "taskCreated", "taskDueDateUpdated"]
  }'

ClickUp responds with a webhook_id and a secret. Keep that secret — every incoming webhook call contains an X-Signature header, an HMAC-SHA256 of the payload with that secret as the key. Verify that signature before you process the payload, otherwise anyone who knows the URL can submit fake status changes.

// routes/api.php (Laravel)
Route::post('/webhooks/clickup', function (Illuminate\Http\Request $request) {
    $expected = hash_hmac('sha256', $request->getContent(), config('services.clickup.secret'));

    if (!hash_equals($expected, $request->header('X-Signature', ''))) {
        abort(401);
    }

    $event = $request->input('event');
    $taskId = $request->input('task_id');
    // ... verwerk de wijziging, zie onder

    return response()->json(['ok' => true]);
});

From ClickUp event to WhatsApp message

Every webhook call contains the event type and a task_id, but not always the full task data. For the new status or due date you usually make a separate GET /task/{task_id} call, or you use the history_items field that some events already include. Link the phone number to the task via a custom field or your own mapping table, and pass it on to the TextMeFlow API:

$phone = Task::where('clickup_task_id', $taskId)->value('whatsapp_number');

if ($phone && $event === 'taskStatusUpdated') {
    $task = Http::withToken(config('services.clickup.token'))
        ->get("https://api.clickup.com/api/v2/task/{$taskId}")
        ->json();

    Http::withToken(config('services.textmeflow.api_key'))
        ->post('https://textmeflow.eu/api/v1/messages', [
            'to' => $phone,
            'type' => 'text',
            'text' => "Status update: \"{$task['name']}\" is now \"{$task['status']['status']}\".",
        ]);
}

If you'd rather not maintain your own backend, you can build the same two steps (signature check + forward) in n8n or Make as well — see our guide on sending WhatsApp messages from n8n, Make.com or Zapier for how to set up such a flow.

Which events are worth it

ClickUp sends dozens of event types; only a few matter for WhatsApp notifications:

  • taskStatusUpdated — inform a customer or team member as soon as a task moves to "In review" or "Completed".
  • taskCreated — escalate internally when a new urgent task comes in (filter by list or tag, otherwise you get a message for every task).
  • taskDueDateUpdated — send a deadline reminder when a due date shifts, combined with a scheduled cron job that checks daily which tasks are due tomorrow.

Subscribe only to the events you actually process — every extra event type increases the number of calls to your endpoint for no benefit.

Secure and limit the flow

Besides ClickUp's own HMAC verification, the same rule applies on the TextMeFlow side of your integration: every status notification TextMeFlow sends back (for example "delivered" or "failed") comes with its own HMAC signature in the header, which you must verify before processing it. The full explanation is in Verifying WhatsApp webhook signatures and in the webhooks documentation.

Also keep the anti-spam rules on the sending side in mind: rate limits, a risk score per number and automatic STOP handling make sure your WhatsApp number doesn't get overloaded, even if a ClickUp list suddenly forwards ten status changes per minute.

Getting started

All you need to build this integration is a TextMeFlow API key. The free plan gives you 50 messages a month to test the integration before you move to a paid plan.

Start testing for free

Want to send WhatsApp messages via API yourself?

Free forever up to 50 messages/month. Scan a QR and send your first message within 5 minutes.

Free forever