GitHub

Updated 5 years ago

GitHub Integration

Prerequisite

You need a Zapier account first. If you don't have an account, click here to create a Zapier account.

Introduction

In this article, we will try integrating both ClickSend and GitHub. So what we want to achieve here is to send an SMS to a contacts list when a new commit occurs in order to instantly inform and log for the management team.

So, let's get started.

Instructions

Step 1:

Login to your Zapier account. And then click Make a Zap! button.

Step 2:

Let's search and select GitHub as our trigger app. Next, check New Commit as our trigger action. Then click Save + Continue button.

Step 3:

Let's link your GitHub account.

Select Choose Account.

Click Connect an Account button.

Enter your Username/Email Address and Password.

Then click Sign in button.

Then click Save + Continue button.

Step 4:

Let finish up our trigger app setup.

Go back to your Zapier setup page.

Then click Fetch & Continue button.

Lastly the Continue button.

Step 5:

Ok, let's set up our Action app. Let's search and choose ClickSend. 

Next select Send SMS to Contact List as our action. 

Then click Save + Continue button.

Step 6:

Next, let's add your ClickSend account. Click Connect an Account button.

There should be a popup saying to add or allow your Zapier and ClickSend account to be linked together.

Type in your ClickSend username and API key.

Click the Test button to check if it was successful.

Then click Save + Continue button.

Step 7:

Let's set up our SMS message.

In the Contact List input box, select the contact list that you want to be informed when a commit occurs.

Enter a custom generic message into the Message input box about the commit such as the Commit Message, Committer Name, Commit Date, Commit URL, etc...

Set the From input box as the name your business or project.

Then click Continue button.

Step 8:

Let's finish up everything.

Click Create & Continue button.

Then the Finish button.

Lastly, name your Zap, and turn it ON


How Did We Do?


Powered by HelpDocs (opens in a new tab)