Skip to content

Webhooks

What Are Webhooks?

Webhooks are outbound HTTP endpoints that Zendesk can call when certain events occur. Triggers and automations can fire webhooks to send data to external systems -- for example, notifying a Slack channel, updating a CRM, or triggering a deployment pipeline.

What Configly Captures

For each webhook, Configly stores:

  • Webhook name
  • Endpoint URL -- the destination for outbound requests
  • HTTP method -- GET, POST, PUT, PATCH, or DELETE
  • Authentication configuration -- type and credentials (API key, bearer token, basic auth)
  • Request format -- JSON, XML, or form-encoded
  • Active status -- whether the webhook is currently enabled
  • Signing secret -- whether request signing is configured
  • Created and updated timestamps

Feature Support

Feature Supported
Sync ✅
Diff / History ✅
Dependencies ✅
What-If ✅

Common Dependencies

Webhooks are referenced by:

  • Triggers -- actions that fire a webhook when conditions are met
  • Automations -- time-based rules that call webhooks

Use dependency mapping to find which triggers reference each webhook. The health check flags orphaned webhooks (WEBHOOK-001) and non-HTTPS endpoints (WEBHOOK-002).

Tips for Admins

  • Always use HTTPS endpoints for security
  • Review orphaned webhooks regularly -- they may indicate removed integrations
  • Before deleting a webhook, check its reverse dependencies to find all triggers that use it
  • Triggers -- rules that fire webhooks
  • Automations -- time-based rules that fire webhooks
  • Targets -- legacy notification targets (predecessors to webhooks)