Before you connect Webhook
Owners and admins can create or change the Webhook integration. Make sure you have a securehttps:// endpoint ready before you start. If your receiver expects authentication, prepare the auth header value your team wants to use.
Each workspace supports one active Webhook integration. If you need to change destinations, update the existing Webhook instead of creating parallel ones.
Connect Webhook
- Open Integrations.
- Open Webhook.
- Add an integration name.
- Add a secure
https://endpoint. - Add an auth header if your receiver expects one.
- Enable the Qualified Lead Detected trigger.
- Decide whether you want auto-send on or off.
- If you turn on auto-send, set the ICP match threshold that should trigger delivery.
- Decide whether to enable Send repeat engagement from qualified leads.
- Open Payload & Help if you want to review the sample payload and signing guidance.
- Send a test payload before you rely on it.
Review the payload
The Webhook UI includes a payload browser and sample JSON. The payload includes event metadata plus lead, profile, company, contact, and engagement data. Use the payload samples in the app as the source of truth for your receiver. They cover first qualified lead delivery and repeat engagement delivery.Verify requests
Webhook requests are signed. Each request includesX-Traxy-Signature and X-Traxy-Timestamp so your receiver can verify that it came from traxy.
Choose manual or automatic delivery
Webhook can work in two ways:- Manual delivery from the leads table when you want to review each lead first
- Automatic delivery when you want traxy to send qualified lead events as soon as leads meet your threshold