# Webhook

## What It Does

Sends the full visitor data payload as a JSON POST request to any URL you specify. Use this to connect Midbound to tools that are not directly supported, or to build custom integrations.

## Authentication

Webhook URL. When adding Webhook as a connection step in an automation, enter the URL where Midbound should send data.

## Data Sent

The webhook sends the complete visitor data object as raw JSON in the POST body with a `Content-Type: application/json` header. This includes:

* **Identity** — person ID, name, profile picture URL, LinkedIn URL, gender, age range, full address
* **Contact** — work emails, personal emails, work phones, personal phones
* **Employment** — job title, company name, company logo URL, company LinkedIn URL, company industry, revenue range, headcount
* **Visitor Stats** — total sessions, total pageviews, total time on site, last seen timestamp, visited pages
* **Attribution** — UTM source, medium, campaign, term, content, entry path, exit path
* **Audiences** — list of all active audience memberships

## Key Behaviors

* **Raw JSON** — Unlike the Slack integration which formats data into a rich message, the webhook sends the complete unmodified data object. This gives you full control over how to process it.
* **No deduplication** — Every workflow trigger sends a new request. If you need deduplication, handle it on the receiving end.
* **URL validation** — The webhook URL is validated during setup. It must be a properly formatted HTTP or HTTPS URL.
* **Works with automation platforms** — Use Zapier, Make, n8n, or any platform that accepts incoming webhooks.

## Using with Workflows

1. Set up your receiving endpoint (your own server, Zapier, Make, etc.)
2. Connect the Webhook integration and enter your URL
3. Build a workflow that triggers the webhook
4. Each matching visitor sends a full data payload to your endpoint

## Related

* [Integrations Overview](/docs/integrations/overview.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://midbound.ai/docs/integrations/webhook.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.