Cloudflare Docs
Edit this page on GitHub
Set theme to dark (⇧+D)

GitHub SMS notifications using Twilio

​​ Before you start

All of the tutorials assume you have already completed the Get started guide, which gets you set up with a Cloudflare Workers account, C3, and Wrangler.

​​ Overview

In this tutorial, you will learn to build an SMS notification system on Workers to receive updates on a GitHub repository. Your Worker will send you a text update using Twilio when there is new activity on your repository.

You will learn how to:

  • Build webhooks using Workers.
  • Integrate Workers with GitHub and Twilio.
  • Use Worker secrets with Wrangler.

Animated gif of receiving a text message on your phone after pushing changes to a repository

​​ Create a Worker project

Start by using npm create cloudflare@latest to create a Worker project in the command line:

Create a project
$ npm create cloudflare@latest

For setup, select the following options:

  • Where do you want to create your application?: Input github-twilio-notifications.
  • What type of application do you want to create?: Select "Hello World" Worker.
  • Do you want to use TypeScript?: Select No.
  • Do you want to deploy your application?: Select Yes.

Make note of the URL that your application was deployed to. You will be using it when you configure your GitHub webhook.

$ cd github-twilio-notifications

Inside of your new github-sms-notifications directory, src/index.js represents the entry point to your Cloudflare Workers application. You will configure this file for most of the tutorial.

You will also need a GitHub account and a repository for this tutorial. If you do not have either setup, create a new GitHub account and create a new repository to continue with this tutorial.

First, create a webhook for your repository to post updates to your Worker. Inside of your Worker, you will then parse the updates. Finally, you will send a POST request to Twilio to send a text message to you.

You can reference the finished code at this GitHub repository.

​​ Configure GitHub

To start, configure a GitHub webhook to post to your Worker when there is an update to the repository:

  1. Go to your GitHub repository’s Settings > Webhooks > Add webhook.

  2. Set the Payload URL to the /webhook path on the Worker URL that you made note of when your application was first deployed.

  3. In the Content type dropdown, select application/json.

  4. In the Secret field, input a secret key of your choice.

  5. In Which events would you like to trigger this webhook?, select Let me select individual events. Select the events you want to get notifications for (such as Pull requests, Pushes, and Branch or tag creation).

  6. Select Add webhook to finish configuration.

Following instructions to set up your webhook in the GitHub webhooks settings dahsboard

​​ Parsing the response

With your local environment set up, parse the repository update with your Worker.

Initially, your generated index.js should look like this:

export default {
async fetch(request, env, ctx) {
return new Response('Hello World!');

Use the request.method property of Request to check if the request coming to your application is a POST request, and send an error response if the request is not a POST request.

export default {
async fetch(request, env, ctx) {
if(request.method !== 'POST') {
return new Response('Please send a POST request!');

Next, validate that the request is sent with the right secret key. GitHub attaches a hash signature for each payload using the secret key. Use a helper function called checkSignature on the request to ensure the hash is correct. Then, you can access data from the webhook by parsing the request as JSON.

index.js - fetch()
async fetch(request, env, ctx) {
if(request.method !== 'POST') {
return new Response('Please send a POST request!');
try {
const rawBody = await request.text();
if (!checkSignature(rawBody, request.headers, env.GITHUB_SECRET_TOKEN)) {
return new Response("Wrong password, try again", {status: 403});
} catch (e) {
return new Response(`Error: ${e}`);

The checkSignature function will use the Node.js crypto library to hash the received payload with your known secret key to ensure it matches the request hash. GitHub uses an HMAC hexdigest to compute the hash in the SHA-256 format. You will place this function at the top of your index.js file, before your export.

index.js - checkSignature()
import { createHmac, timingSafeEqual } from 'node:crypto';
import { Buffer } from 'node:buffer';
function checkSignature(text, headers, githubSecretToken) {
const hmac = createHmac('sha256', githubSecretToken);
const expectedSignature = hmac.digest('hex');
const actualSignature = headers.get('x-hub-signature-256');
const trusted = Buffer.from(`sha256=${expectedSignature}`, 'ascii');
const untrusted = Buffer.from(actualSignature, 'ascii');
return trusted.byteLength == untrusted.byteLength
&& timingSafeEqual(trusted, untrusted);

To make this work, you need to use wrangler secret put to set your GITHUB_SECRET_TOKEN. This token is the secret you picked earlier when configuring you GitHub webhook:

$ npx wrangler secret put GITHUB_SECRET_TOKEN

Add the nodejs_compat flag to your wrangler.toml file:

compatibility_flags = ["nodejs_compat"]

​​ Sending a text with Twilio

You will send a text message to you about your repository activity using Twilio. You need a Twilio account and a phone number that can receive text messages. Refer to the Twilio guide to get set up. (If you are new to Twilio, they have an interactive game where you can learn how to use their platform and get some free credits for beginners to the service.)

You can then create a helper function to send text messages by sending a POST request to the Twilio API endpoint. Refer to the Twilio reference to learn more about this endpoint.

Create a new function called sendText() that will handle making the request to Twilio:

index.js - sendText()
async function sendText(accountSid, authToken, message) {
const endpoint = `${accountSid}/Messages.json`;
const encoded = new URLSearchParams({
'Body': message
const token = btoa(`${accountSid}:${authToken}`);
const request = {
body: encoded,
method: 'POST',
headers: {
'Authorization': `Basic ${token}`,
'Content-Type': 'application/x-www-form-urlencoded',
const response = await fetch(endpoint, request);
const result = await response.json();
return Response.json(result);

To make this work, you need to set some secrets to hide your ACCOUNT_SID and AUTH_TOKEN from the source code. You can set secrets with wrangler secret put in your command line.

$ npx wrangler secret put TWILIO_ACCOUNT_SID
$ npx wrangler secret put TWILIO_AUTH_TOKEN

Modify your githubWebhookHandler to send a text message using the sendText function you just made.

index.js - fetch()
async fetch(request, env, ctx) {
if(request.method !== 'POST') {
return new Response('Please send a POST request!');
try {
const rawBody = await request.text();
if (!checkSignature(rawBody, request.headers, env.GITHUB_SECRET_TOKEN)) {
return new Response('Wrong password, try again', {status: 403});
const action = request.headers.get('X-GitHub-Event');
const json = JSON.parse(rawBody);
const repoName = json.repository.full_name;
const senderName = json.sender.login;
return await sendText(
`${senderName} completed ${action} onto your repo ${repoName}`
} catch (e) {
return new Response(`Error: ${e}`);

Run the npx wrangler publish command to redeploy your Worker project:

$ npx wrangler deploy

Video of receiving a text after pushing to a repo

Now when you make an update (that you configured in the GitHub Webhook settings) to your repository, you will get a text soon after. If you have never used Git before, refer to the GIT Push and Pull Tutorial for pushing to your repository.

Reference the finished code on GitHub.

By completing this tutorial, you have learned how to build webhooks using Workers, integrate Workers with GitHub and Twilio, and use Worker secrets with Wrangler.