# Incoming endpoints and outgoing webhooks

> Two things point in opposite directions, and knowing which one you need saves a lot of guessing.

Source: https://infranest.io/docs/incoming-endpoints
Last updated: 2026-09-19

---

Not sure whether you need something that lets another tool trigger InfraNest, or something that lets InfraNest notify another tool? This article helps you pick the right one and points you to where each is set up. It's for anyone connecting InfraNest to other tools they use.

## Overview

- An **incoming endpoint** lets another tool start an automation in InfraNest.
- An **outgoing webhook** lets InfraNest tell another tool that something happened.
- The short version: incoming is a doorbell somebody else presses. Outgoing is us ringing theirs.

## Which one do you want?

|  | Incoming endpoint | Outgoing webhook |
|---|---|---|
| Direction | another tool → InfraNest | InfraNest → another tool |
| You give out | a URL InfraNest generates | a URL the other tool gives you |
| Use it to | let something else start an automation | tell something else that an event happened |
| Set up in | the integration, or your automation | the integration, under Where events go |

## Set up an incoming endpoint

1. Go to **Integrations** and open the tool you want to connect, or open the relevant rule in **Automations**.
2. Create an incoming endpoint — InfraNest generates a private URL for you.
3. Give the endpoint a clear name so you can tell at a glance which tool it belongs to.
4. Copy the URL and paste it into the other system's settings, wherever it asks where to send its requests.
5. When that system sends a request to the URL, your automation runs, using whatever information it sent.

<!-- docs-screenshots:start -->

![Incoming endpoints and outgoing webhooks (1)](/media/053ef784-f558-4785-bac4-b7072e4cb9f3)

![Incoming endpoints and outgoing webhooks (2)](/media/5eeac513-10ca-44b6-ac44-c63906654983)

<!-- docs-screenshots:end -->

You can turn any single endpoint off without affecting the others.

> [!WARNING]
> The URL is the credential. Anyone who has it can trigger that automation, so treat it like a password — and if it leaks, regenerate it.

## Set up an outgoing webhook

1. Go to **Integrations** and choose **Custom webhook** (or Zapier, Make or n8n).
2. Open **Where events go** and add the URL the other tool gave you.
3. Build or edit an automation to decide which events get sent to that destination.
4. Save your changes — from then on, matching events (a monitor going down, a domain renewing, a watched domain becoming available) are sent to that URL automatically.

Every delivery is signed and logged, so you can check what was sent and whether it arrived. See **Connect a custom webhook** for the full walkthrough.

## Still not sure?

Ask which side starts the conversation:

- "When X happens in my other tool, do something in InfraNest" → set up an **incoming endpoint**.
- "When X happens in InfraNest, tell my other tool" → set up an **outgoing webhook**.
- "Both" → you need one of each; they're independent of one another.

## Tips

> [!TIP]
> If you're building a two-way integration, set up the incoming endpoint and the outgoing webhook separately — they don't share configuration, so each needs its own setup and its own name.