<commit_before># Webhook Integrations

There are a number of third party services you can use with Buildkite webhooks. Some services (such as RequestBin and Zapier) are designed specifically with webhooks in mind, and others (such as AWS Lambda, Google Cloud Functions, IronWorker and Webtask) are general purpose programming platforms which can be triggered with webhook HTTP requests.

<%= toc %>

## RequestBin

[RequestBin](http://requestb.in) is free service by [Runscope](https://www.runscope.com/) which creates private URLs you can use to inspect and debug webhook requests. It's a great starting place for understanding how Buildkite webhooks work.

To get started go to [http://requestb.in](http://requestb.in) and create a new bin:

<%= image "request-bin.png", size: '297x143', alt: 'Screenshot of Create a RequestBin request' %>

Copy the bin’s URL and add it in a new Buildkite webhook notification. Once you've saved the notification settings we’ll send it a [Ping](/docs/webhooks/ping-events) event. Simply reload your RequestBin page to inspect the `ping` webhook request.

## AWS Lambda

[AWS Lambda](https://aws.amazon.com/lambda/) is an Amazon service for hosted Javascript execution, and supports exposing functions via URLs. You can follow their [GitHub webhook guide](https://aws.amazon.com/blogs/compute/dynamic-github-actions-with-aws-lambda/) for an example of how to publish Buildkite webhook events as SNS topics and then process them using AWS Lambda.

## Google Cloud Functions

[Google Cloud Functions](https://cloud.google.com/functions) are a Google Cloud service for hosted Javascript execution, and also supports exposing functions via URLs. See the [Calling Cloud Functions documentation](https://cloud.google.com/functions/calling) for how to expose them, and their [Hello World walkthrough](https://cloud.google.com/functions/walkthroughs) for getting started.

## IronWorker

[Iron.io’s IronWorker](http://www.iron.io/worker/) is a service for hosted code execution using Docker containers. You can follow their [webhook worker documentation and sample code](http://dev.iron.io/worker/webhooks/) for an example of how to create an endpoint to use with Buildkite webhooks.

## Zapier

[Zapier](https://zapier.com/) is a system for connecting APIs together, and has built in support for hundreds of services. For example, you could use Zapier to send an email when a build has finished, save a build artifact into a Dropbox folder, or post to a Slack room substituting values such as the build URL and number into the message body.

To use Buildkite webhooks with Zapier create a new Zap and select Webhook.

## Webtask

[Webtask](https://webtask.io/) makes it easy to write Node.js powered backend code without having to run a server, and it supports cron (scheduled runs) and secure token storage (for things like API keys). You can use our LIFX webtask example to get started with processing webhooks using Webtask:

<a class="Docs__example-repo" href="https://github.com/buildkite/lifx-buildkite-build-light-webtask">:node: Webtask.io webhook example application <span class="repo">github.com/buildkite/lifx-buildkite-build-light-webtask</span></a><commit_msg>Remove RequestBin in documentation<commit_after># Webhook Integrations

There are a number of third party services you can use with Buildkite webhooks. Some services (such as RequestBin and Zapier) are designed specifically with webhooks in mind, and others (such as AWS Lambda, Google Cloud Functions, IronWorker and Webtask) are general purpose programming platforms which can be triggered with webhook HTTP requests.

<%= toc %>

## AWS Lambda

[AWS Lambda](https://aws.amazon.com/lambda/) is an Amazon service for hosted Javascript execution, and supports exposing functions via URLs. You can follow their [GitHub webhook guide](https://aws.amazon.com/blogs/compute/dynamic-github-actions-with-aws-lambda/) for an example of how to publish Buildkite webhook events as SNS topics and then process them using AWS Lambda.

## Google Cloud Functions

[Google Cloud Functions](https://cloud.google.com/functions) are a Google Cloud service for hosted Javascript execution, and also supports exposing functions via URLs. See the [Calling Cloud Functions documentation](https://cloud.google.com/functions/calling) for how to expose them, and their [Hello World walkthrough](https://cloud.google.com/functions/walkthroughs) for getting started.

## IronWorker

[Iron.io’s IronWorker](http://www.iron.io/worker/) is a service for hosted code execution using Docker containers. You can follow their [webhook worker documentation and sample code](http://dev.iron.io/worker/webhooks/) for an example of how to create an endpoint to use with Buildkite webhooks.

## Zapier

[Zapier](https://zapier.com/) is a system for connecting APIs together, and has built in support for hundreds of services. For example, you could use Zapier to send an email when a build has finished, save a build artifact into a Dropbox folder, or post to a Slack room substituting values such as the build URL and number into the message body.

To use Buildkite webhooks with Zapier create a new Zap and select Webhook.

## Webtask

[Webtask](https://webtask.io/) makes it easy to write Node.js powered backend code without having to run a server, and it supports cron (scheduled runs) and secure token storage (for things like API keys). You can use our LIFX webtask example to get started with processing webhooks using Webtask:

<a class="Docs__example-repo" href="https://github.com/buildkite/lifx-buildkite-build-light-webtask">:node: Webtask.io webhook example application <span class="repo">github.com/buildkite/lifx-buildkite-build-light-webtask</span></a>
{'fraction_non_alphanumeric': 0.08042568039078855, 'fraction_numerical': 0.00104675505931612, 'mean_word_length': 4.934782608695652, 'pattern_counts': {'":': 0, '<': 14, '<?xml version=': 0, '>': 14, 'https://': 17, 'lorem ipsum': 0, 'www.': 3, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3609900', 'n_tokens_mistral': 1556, 'n_tokens_neox': 1514, 'n_words': 709}