Skip to main content

What Is a Webhook?

A webhook is a URL your software exposes so another system can push data to you when an event happens — usually an HTTP POST with a JSON or CSV body. You do not poll for updates; the sender calls you.

On MCPBundles, Webhook data capture stores those payloads so your AI can read them through MCP tools. That is separate from Webhook triggers, which start an A2A agent run, and from CSV upload, where you download a file and upload it yourself.

How it differs from a normal API call​

You call their APIThey call your webhook
Who starts the requestYour script or appTheir server when an event fires
Typical use"Fetch today's orders now""Tell me when an order is placed"
You need to beRunning code on a schedule or on demandReachable at a stable HTTPS URL

Many products offer both: a dashboard export (download a file) and a webhook or "HTTP notification" setting for the same data on a schedule.

What gets sent​

Payload shape depends on the sender. Common patterns:

  • JSON — form submissions, payment events, monitoring alerts
  • CSV or plain text — scheduled report drops from BI or partner portals
  • Signed body — some senders add an HMAC header so you can verify the POST really came from them

Treat the ingest URL like a password: anyone who has it can POST data to your connection until you rotate it.

Webhooks on MCPBundles​

If your tool can POST to a URL but there is no MCP server for that product yet, connect Webhook Ingest:

  1. Connect the server and save a source name.
  2. Copy the ingest URL from the connection panel.
  3. Paste it into the upstream app's webhook or scheduled-export setting.
  4. Connect your AI and ask questions about what arrived.

Each delivery is stored with a timestamp. Your agent can list recent payloads, read the latest one, or compare reports over time — without you downloading files by hand.

For the step-by-step product flow, see Webhook data capture for MCP servers and the walkthrough Webhook ingest for AI workflows.