Webhook Event Triggers

Pipedream allows users to use a webhook as a trigger to begin the execution of a workflow. When you create a new Webhook source, we create a URL endpoint specific to your pipeline.

While we call the source "Webhook", it's technically a general HTTP source. You can send any HTTP requests to this endpoint, from anywhere on the web. You can configure the endpoint as the destination URL for a webhook or send HTTP traffic from your application - we'll accept any valid HTTP request.

Capabilities

Pipedream allows you to execute a function and/or call a URL whenever your workflow receives a webhook.

Quickstart

• Fork this pipeline or click the "FORK" button above
• This will generate a new workflow in your account with a Webhook source (and a URL endpoint specific to your workflow)
• Click SEND TEST EVENT which will trigger the scripts in your workflow
• Select the event in the inspector and you will see observability at each step in the workflow

Usage Tips

• All pipeline code on Pipedream is public, all event data is private.
• Pipeline code is run for every event sent to your source.
• Send data to S3, HTTP out using destinations.
• The event data sent to your source is accessible in the $event object — you can add, update, or delete any properties of this object in your code.
• Most of NPM’s 400,000 packages are available for use — just require() them.
• Using API keys or other sensitive data in your code? Create an environment variable and access it in code using process.env.KEY_NAME.
• Need to reject certain events sent to your pipeline, or end a pipeline early? Use $end().
• You need to await the execution of async code with Promises, using async / await — learn more here