Jeffrey Labrecque | 2026-05-15
We have made an update on our webhook feature. Small update, but helpfull. You can fire a sample high-intent, target-account, or lead-capture payload to any URL straight from webhook settings. Optional signing keeps your receiver’s HMAC verification in sync with real deliveries.
Configuring Zapier, Make, or a custom HTTPS endpoint shouldn’t guesswork. Starting now, webhook testing sends a full sample POST to whichever URL you provide—matching production JSON plus the same headers you rely on day to day.
What you’ll notice
Open your workspace webhook settings and run a test. You choose the event type (high intent, target accounts, or lead capture) so your automation sees realistic fields. Paste the exact URL you’ll use when live; nothing is routed through a saved webhook list for tests.
Optional signature check
If you verify webhooks with a shared secret, you can attach it on the test call. We’ll generate the DigitalPilot signature the same way as real deliveries, so you can confirm your receiver rejects bad payloads and trusts good ones.
Use this anytime you migrate endpoints, tighten security, or wire a new stack. Fewer surprises in production—and faster confidence that your integrations will fire when campaigns do.