# Webhooks: send new mentions to your tools (https://snitchfeed.com/docs/integrations/webhooks)





A webhook sends each new mention to a web address you choose, the moment it arrives in a feed. Use it to push mentions into an automation tool (such as Zapier, Make or n8n), a CRM or your own app without copying anything by hand.

<Callout type="info" title="Pro plan">
  Webhooks need the Pro plan. On other plans, **Integrations → Webhooks** is
  locked. See [Plans & billing](/docs/workspace/plans-and-billing).
</Callout>

## When to use a webhook [#when-to-use-a-webhook]

* You want mentions in a tool SnitchFeed does not connect to directly.
* You want a lead or task created automatically for each strong mention.
* A developer on your team wants mention data in your own system.

For alerts in Slack, Discord or email, use [notifications](/docs/notifications) instead. They need no setup on the other side.

## How it works [#how-it-works]

You set up a webhook in two places:

1. **The endpoint.** This is the web address that receives mentions. Your automation tool or developer gives you this address.
2. **The feed.** You pick which feeds send to that endpoint. Only mentions that pass the feed's filters are sent.

One endpoint can be used by several feeds.

## Add a webhook endpoint [#add-a-webhook-endpoint]

<Steps>
  <Step>
    ### Open the Webhooks page [#open-the-webhooks-page]

    Go to **Integrations → Webhooks** ([app.snitchfeed.com/integrations/webhooks](https://app.snitchfeed.com/integrations/webhooks)).
  </Step>

  <Step>
    ### Start a new webhook [#start-a-new-webhook]

    Click **Create Webhook**.
  </Step>

  <Step>
    ### Paste the address [#paste-the-address]

    Paste the address into **Webhook URL**. It must start with `https://`.
  </Step>

  <Step>
    ### Name it [#name-it]

    Enter a **Name** you will recognize later, for example "CRM pipeline".
  </Step>

  <Step>
    ### Save and test [#save-and-test]

    Click **Save**. Then click **Test** to send a sample mention and check that it arrives.
  </Step>
</Steps>

Use the **Status** toggle to pause or resume an endpoint without deleting it.

## Choose which feeds send to it [#choose-which-feeds-send-to-it]

<Steps>
  <Step>
    ### Open the feed [#open-the-feed]

    Open a saved [feed](/docs/feeds) and click **Notifications** in the top bar.
  </Step>

  <Step>
    ### Pick endpoints [#pick-endpoints]

    In the **Webhooks** tab, select the endpoints that should receive this feed's mentions.
  </Step>

  <Step>
    ### Turn it on [#turn-it-on]

    Turn on **Enable notifications**, then click **Save changes**.
  </Step>
</Steps>

To send fewer mentions, tighten the feed's filters, for example its **Fit score** filter. See [Notifications](/docs/notifications#turn-on-alerts-for-a-feed).

You can also send a single existing mention to an endpoint from the app with **Send to webhook**.

## Check that mentions are delivered [#check-that-mentions-are-delivered]

The **Webhooks** page has two tabs: **Endpoints** and **Log**. The **Log** tab shows one row for each mention sent to each endpoint.

| Column          | What it shows                                      |
| --------------- | -------------------------------------------------- |
| **Date & time** | When SnitchFeed last tried to send it              |
| **Endpoint**    | Which endpoint it went to                          |
| **Mention**     | A link to open the mention                         |
| **Attempts**    | How many times SnitchFeed tried, including retries |
| **Code**        | The reply code the other tool sent back            |
| **Status**      | `pending`, `success`, `failed` or `retrying`       |

Click a row to see the full reply. Filter by **Status**, **Endpoint** and **Date range**.

If a delivery fails, SnitchFeed tries again up to 10 times. If the address no longer exists, the endpoint is switched off.

## Slow down deliveries [#slow-down-deliveries]

Some tools can only accept a few mentions at a time. Open **Advanced: delivery limits** in the webhook dialog to pace them.

| Setting                     | Default | Maximum |
| --------------------------- | ------: | ------: |
| **Max concurrent requests** |       1 |      20 |
| **Max requests per minute** |      10 |     120 |

Keep these at or below what the receiving tool supports.

## Next steps [#next-steps]

* [Webhook events, retries and delivery limits](/docs/api/webhooks): the technical reference for developers, including what each mention contains.
* [Workflows](/docs/features/workflows): add conditions and approvals before a webhook fires.
* [Feeds](/docs/feeds): build the filters that decide what is sent.