Webhook Destination Setup

Webhook destinations send Prevenue signal payloads to your systems. Use them when a custom application, data pipeline, operations tool, or internal workflow should receive structured signal output.

Open Settings > Integrations > Webhook to configure endpoint URLs. A workspace can keep up to 10 active webhook endpoints.

Requirements

Your receiver should:

• Use HTTPS.
• Accept JSON payloads.
• Verify Prevenue signatures with the current signing secret.
• Return a successful HTTP response quickly.
• Store idempotency keys or delivery identifiers.
• Treat webhook delivery as at-least-once.
• Avoid creating duplicate downstream work on retry.

Setup steps

1. Open Settings > Integrations > Webhook.
2. Select Add endpoint.
3. Enter a display name.
4. Enter the HTTPS destination URL.
5. Save the endpoint.
6. Open the setup guide and copy the relevant endpoint metadata.
7. Send a test payload to the endpoint.
8. Confirm the receiver verifies the signature and stores the idempotency key.
9. Review the endpoint row for latest delivery status.
10. Repeat for any other endpoint that should receive signal payloads.

When a Funnel uses the Webhook delivery channel, select 1-5 active endpoints for that Funnel. Removing the Webhook channel clears the selected endpoints.

Signature verification

Webhook destinations use HMAC signing. Each endpoint has its own signing secret. Your receiver should compute the expected signature with the current endpoint signing secret and compare it to the request signature using a timing-safe comparison.

Rotate an endpoint signing secret if it may have been exposed. After rotation, update that receiver before relying on delivery.

Payload review

Payload previews are visible from signal detail pages. A payload can include:

• Signal ID, type, category, priority, status, reason, and recommended action.
• Account display name, external ID, domain, plan, MRR, status, billing customer ID, and safe identity values when known.
• Evidence summary and references.
• Account intelligence context when available.
• Compatibility rule context such as the internal rule name, rule key, routing key, selected route channels, and route kind.
• Safe route metadata such as prevenue.route.destination_id and prevenue.route.destination_name.
• Event KPI rows, prediction readiness, sentiment distributions, semantic/category counts, source counts, matched evidence count, and total events scored when available.
• Delivery provider, route kind, attempt time, and idempotency key.
• Workspace ID.

Use payload preview to align the receiver before enabling a workflow.

Test and operate

Send a setup test after every endpoint or signing-secret change. Then validate one real signal route before treating the integration as production-ready.

Monitor:

• Endpoint count and selected endpoint count per Funnel.
• Last test time per endpoint.
• Last response per endpoint.
• Host and path summary per endpoint.
• Whether signing is enabled.
• Recent failed delivery activity.
• Disabled state.

Related articles

• Destinations
• API and Webhooks
• Signals
• Data Safety and Security Boundaries