Overview
Pipedream allows users to trigger a workflow via an HTTP request.
When you create a new HTTP / Webhook trigger, we create a URL endpoint specific to your workflow.
While we call the trigger "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.
Quickstart
- Fork this workflow or click the "FORK" button above
- This will generate a new workflow in your account with a Webhook trigger (and a URL endpoint specific to your workflow)
- Send an HTTP request to your endpoint which will trigger the execution of your workflow
- Click on the event to see the observability at each code step
Example Workflows
Usage Tips
- All pipeline code on Pipedream is public and run on every event. All event data is private.
- Send data to Airtable, S3, Snowflake or HTTP out using code actions.
- Use $end() to stop your workflow or $respond to return a response to the client.
- Most of NPM’s 400,000 packages are available for use — just require() them.
- Store API keys or secrets as environment variables and access via
process.env.KEY_NAME.
await the execution of async code with Promises, using async / await. - You need to await the execution of async code with Promises, using async / await — learn more here