---
title: "Webhook Integration"
canonical: https://trickest.com/glossary/webhook-integration
description: "A webhook integration sends an HTTP callback to another system the moment an event fires, letting workflows react in real time instead of polling for changes."
---

# Webhook Integration

A webhook integration is an event-driven HTTP callback. Instead of a system repeatedly asking "anything new yet?", the source service pushes a POST request to a URL you register the instant something happens: a scan finishes, a new asset appears, a finding crosses a severity threshold. The payload carries the event details, and the receiving system acts on them immediately.

The model wins on latency and efficiency. Polling wastes requests on quiet intervals and adds delay equal to the poll period; a webhook delivers within seconds of the event and costs nothing while idle. The tradeoff is reliability and security: the receiver has to be reachable, handle retries and duplicate deliveries, and verify the sender, usually through a signed secret in the request, so an attacker cannot forge events.

In security workflows webhooks are the glue that makes pipelines reactive. A new finding can fire a webhook that opens a ticket, posts to a chat channel, or kicks off enrichment, which is the connective tissue of [security automation](/glossary/security-automation) and [security orchestration](/glossary/security-orchestration).

In a Trickest workflow a webhook node both triggers a run from an external event and pushes results outward when the graph finishes, wiring [workflow orchestration](/glossary/workflow-orchestration) into the rest of your [data pipeline](/glossary/data-pipeline) without manual handoffs.

---
_Markdown source of https://trickest.com/glossary/webhook-integration._