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

# Traffic and webhooks

> Which way calls and webhooks flow between your apps and outside services.

Select an item and dots move along its lines that carry traffic, the way it flows. Its details list the same thing in words.

![An item's details with its traffic, and dots moving along its lines](https://mintcdn.com/xerg/Xfd-lD2nNpiXaLb6/images/details-light.webp?fit=max\&auto=format\&n=Xfd-lD2nNpiXaLb6\&q=85\&s=cab26911e21f425a1184b04e32d6b5b1)

## Calls

**App to service**: the app calls it, or stores data in it. Found from the app's packages, env variable names and source.

## Webhooks

**Service to app**: the service calls in, the other way round. Xerg finds a webhook from:

* the env variable name of its secret, like `STRIPE_WEBHOOK_SECRET`, `SLACK_SIGNING_SECRET` or `QSTASH_CURRENT_SIGNING_KEY`
* a route file with a webhook folder or file next to a service's name, like `app/api/webhooks/stripe/route.ts`, from the repo's file list without reading it

A connected Stripe account's webhook endpoints confirm them.

When both happen, dots move both ways.

## What the dots don't say

Every line moves at the same speed: dots show direction, not how much traffic there is. Lines like **contains** or **deploys to** are structure, not traffic, so they have none.

## In Ask and MCP

`impact` follows the same lines: an app that receives a service's webhooks depends on that service. See the [tool reference](https://xerg.ai/docs/coding-agents/tools.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.