Taalk Help Center

Notification Webhooks and Slack

Campaign and workspace notifications can go to email, to your own system as a Webhook, or to a Slack channel as a Slack Channel message. This article covers the two non-email targets: how to set them up, which events they support and what Taalk sends.

Where to add them

Scope Go to Article
One campaign Open the campaign › Notifications tab › Add notification Campaign Alerts
Every campaign in the workspace Workspace menu › Manage workspaces › your workspace › Company Detail › Notifications Workspace Notifications

Workspace notifications apply to all campaigns, in addition to each campaign's own.

Add a webhook

  1. Click Add notification.
  2. Pick the Event.
  3. Set Type to Webhook.
  4. Pick the Method (POST by default).
  5. Enter the URL of your endpoint.
  6. Click Save changes.

Add a Slack channel

  1. In Slack, create an incoming webhook: go to api.slack.com/apps, pick or create an app, turn on Incoming Webhooks, click Add New Webhook to Workspace, pick a channel and copy the URL.
  2. In Taalk, click Add notification, pick the Event, and set Type to Slack Channel.
  3. Paste the URL into Slack Webhook URL (it starts with https://hooks.slack.com/services/).
  4. Click Save changes.

Slack messages show a title, a short summary and a View Campaign button.

Which events each target supports

Event Webhook Slack Channel
Metric Threshold Yes Yes
Hourly Report, Half Day Report, Daily Report Yes Yes
New Contact Yes No
Remove Contact Yes No
Agent Miss Call Yes No
Click Link Yes No
Fuse Melt (campaign notifications only) Yes No
Low Fresh Contacts, Contacts Exhausted, Campaign Stalled Yes (see below) No

If you pick Slack Channel for an event without Slack support, nothing is sent. Use Email or Webhook for those events.

The workspace-wide Daily Report (Company Detail › Notifications) is sent by email only. For a daily report by webhook or Slack, add a Daily Report notification on each campaign.

What Taalk sends to a webhook

Taalk sends a JSON body with the method you chose.

Event Body
Metric Threshold event: "metric_threshold", campaign, campaignId, metric, metricLabel, operator, threshold, value, formattedValue, formattedThreshold, window
Hourly / Half Day / Daily Report values (counts for the period) and cost (total, unit, unitVM)
New Contact contacts: the contacts that were added
Remove Contact phones and emails of the removed contacts
Agent Miss Call missing: the number of transfers picked up by an IVR in the time window
Click Link session, campaign, companyId, params, context, phone, email
Fuse Melt campaign (ID) and failureRate
Contact health event: "contact_health_alert", campaign, campaignId, severity, issues, stats (fresh, total, exhausted, bad, freshPct)

Contact health alerts (low fresh contacts, exhausted contacts, campaign stalled) go to every webhook on the campaign, whatever event it's set to, at most once every 24 hours. Admins also get an email.

[Confirm] Field names and the exact contents of values in report webhooks.

Delivery

  • Webhooks are sent once. There are no retries. If your endpoint is down or returns an error, that notification is lost.
  • There's no delivery log, test button, custom header or signing secret. Make your endpoint accept the request quickly and log what it receives.
  • To check that a request came from Taalk, put a long, hard-to-guess token in your URL (for example ?key=...) and rotate it if it leaks.

Notification webhooks vs. the post-call webhook

Notification webhook Post-call webhook
Set on Campaign or workspace AI agent (Post-call and automations › Webhook)
Fires on Campaign events and reports Each call or engagement
Best for Alerts, reports, new-contact feeds Sending call results to a CRM or automation tool

See Event Webhooks for the post-call webhook, and Connect Zapier, Make or HubSpot with Webhooks for recipes.

Related