Custom webhook and Talon
Point Talon at your own HTTPS endpoint, with optional HMAC signing. You can register your own endpoint in Talon, choose the events you want, and send a signed test event. Talon does not send finding events to webhooks yet. If you need findings in another system today, the MCP server lets your own tools read them.
What works today
Available now
- Your endpointAny HTTPS URL that accepts a JSON POST.
- HMAC-SHA256 signingAdd a secret and every request carries an X-Webhook-Signature header you can verify.
- Event choices savedPick new finding, finding status change, scan completed and new asset.
- Test eventSend a test event to check your receiver and your signature check.
Good to know
- Finding events are not sent yet. The event choices are saved for when they are.
- Failed deliveries are logged, not retried.
- To pull findings into your own tools today, use the MCP server.
Set it up in a few minutes
You need a Talon workspace and permission to create a token or webhook in Custom webhook.
- 01
Prepare a receiver
Stand up an HTTPS endpoint that accepts a JSON POST and returns a 2xx status.
- 02
Open the Marketplace in Talon
Go to Workspace > Marketplace and choose Configure Webhook.
- 03
Enter your details
Add the URL, an optional secret for signing, and the events you want.
- 04
Test and save
Send a test event, check the signature on your side, then save.
What is sent today
| Field | What you get |
|---|---|
| Test event | A JSON POST with event, data, timestamp and source fields |
| Signature | X-Webhook-Signature: sha256=<HMAC of the body> when a secret is set |
| Finding events | Not sent yet |