Pipedream supports webhooks as a way to deliver events to an endpoint you own. Webhooks are managed at an account-level, and you send data to these webhooks using subscriptions. For example, you can run a Twitter event source that listens for new tweets. If you subscribe the webhook to this source, Pipedream will deliver those tweets directly to your webhook’s URL without running a workflow.Documentation Index
Fetch the complete documentation index at: https://pipedream.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Send events from an existing event source to a webhook
Event sources source data from a service / API, emitting events that can trigger Pipedream workflows. For example, you can run a GitHub event source that emits an event anytime someone stars your repo, triggering a workflow on each new star. You can also send the events emitted by an event source to a webhook.
Step 1 - retrieve the source’s ID
First, you’ll need the ID of your source. You can visit https://pipedream.com/sources, select a source, and copy its ID from the URL. It’s the string that starts withdc_:

pd list sources using the CLI.
Step 2 - Create a webhook
You can create a webhook using thePOST /webhooks endpoint. The endpoint accepts 3 params:
url: the endpoint to which you’d like to deliver eventsname: a name to assign to the webhook, for your own referencedescription: a longer description
cURL:
data.id — the string that starts with wh_ — which you’ll use in Step 3:
Step 3 - Create a subscription
Subscriptions allow you to deliver events from one Pipedream resource to another. In the language of subscriptions, the webhook will listen for events emitted by the event source. You can make a request to thePOST /subscriptions endpoint to create this subscription. This endpoint requires two params:
emitter_id: the source ID from Step 1listener_id: the webhook ID from Step 2
cURL:
200 OK with metadata on the subscription.