> ## Documentation Index
> Fetch the complete documentation index at: https://apidoc.cufinder.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Signals Webhooks

> Signals Webhooks push buying-signal events to your endpoint the moment they are detected. Instead of polling the Signals APIs, define a webhook in your dashboard, choose the filters, and receive matching events as they happen.

The **Signals Webhooks** turn CUFinder's buying-signal detection into a push feed. You define a webhook in your [dashboard](https://dashboard.cufinder.io/), pick the event type and filters, and CUFinder sends each matching event to your endpoint as an HTTP `POST` with a JSON body. No polling, no schedules, no missed windows.

## Webhook types

<CardGroup cols={2}>
  <Card title="Company Activity Webhook" icon="rss" href="/buying-signals/signals-webhooks/company-activity">
    News, funding, and activity on companies you track.
  </Card>

  <Card title="People Signals Webhook" icon="users" href="/buying-signals/signals-webhooks/people-signals">
    Buying-intent and behavior signals on contacts.
  </Card>

  <Card title="Company Signals Webhook" icon="building" href="/buying-signals/signals-webhooks/company-signals">
    Buying-intent and behavior signals on companies.
  </Card>

  <Card title="Job Changes Webhook" icon="arrows-exchange" href="/buying-signals/signals-webhooks/job-changes">
    Career moves for contacts you track.
  </Card>
</CardGroup>

## How it works

<Steps>
  <Step title="Create a webhook in the dashboard">
    Open your [dashboard](https://dashboard.cufinder.io/), go to the webhooks section, and click **New webhook**.
  </Step>

  <Step title="Choose a type and filters">
    Pick one of the four webhook types and set its filters, for example a signal name, time frame, and bucket. Only events matching your filters are delivered.
  </Step>

  <Step title="Point it at your endpoint">
    Enter the HTTPS URL that should receive events, for example `https://your-app.com/webhooks/cufinder`.
  </Step>

  <Step title="Activate and receive events">
    Leave **Start active** on to begin receiving events immediately, or pause it to save the webhook without sending anything yet.
  </Step>
</Steps>

## Fields shared by every webhook

| Field            | Required | Description                                                            |
| ---------------- | -------- | ---------------------------------------------------------------------- |
| Webhook name     | Yes      | A label for your own reference, for example `High-intent EU accounts`. |
| Webhook type     | Yes      | One of the four types above.                                           |
| Webhook endpoint | Yes      | The HTTPS URL that receives the events.                                |
| Start active     | No       | On by default. Turn it off to save the webhook in a paused state.      |

<Note>
  Webhooks complement the [Signals APIs](/buying-signals/signals-apis/introduction): use webhooks to react to events in real time, and the APIs to query signals on demand.
</Note>