Node.js SMS Quickstart

Build a simple Node.js application that receives an SMS message and sends a reply.

👍

You're ready for this quickstart if you've got the following:

A free trial account
A registered application
A configured FreeClimb Number
Your language and tools:

Trial accounts: A verified number


Clone your quickstart

For this quickstart, clone the repository for Node Receive Message Tutorial using GitHub's interface or git in the command line.

git clone https://github.com/FreeClimbAPI/Node-Receive-Message-Tutorial.git

Add your credentials to your project

Now that you've cloned the repo for your sample app, the next step is to add your API credentials so you can authenticate with FreeClimb. To do this, first copy your account ID and API key from your dashboard homepage.

1114

Your API credentials can be copied from your Dashboard homepage.

Create a .env file in the root directory of your repo. Make sure to add the file to your .gitignore file. Add your account ID and API key to your .env file, and save the file. Your .env file should look something like this:

ACCOUNT_ID=YOUR-ACCOUNT-TOKEN
API_KEY=YOUR-API-KEY

The quickstart uses dotenv to read in your credentials, and anything else you save, as environment variables.

Replace the placeholder values

In your receiveMessage.js file replace the placeholder values for the To and From numbers. The To number should be a verified number and the From number should be your configured FreeClimb number. Both should be in E.164 format.

When you're done your file should look something like this:

app.post('/incomingSms', (req, res) => {
  let to = '+15555550010' //your Verified Number
  let from = '+15555551101' //your FreeClimb Number
  freeclimb.api.messages.create(from, to, 'Hey! It is your application!').catch(err => {console.log(err)})
})

Make your local server publicly accessible

The fastest way to start testing your FreeClimb application is to temporarily make your local server publicly accessible through a tunneling service. We'll use ngrok to do this. Start by downloading ngrok. Unzip the file to install, then open your terminal and navigate to the directory where you've unzipped ngrok. Use the following command to start a HTTP tunnel on port 3000.

./ngrok http 3000

Once you run ngrok you should receive a response with a public URL, that looks something like this:

ngrok by @inconshreveable

Tunnel Status                 online
Version                       2.0/2.0
Web Interface                 http://127.0.0.1:4040
Forwarding                    http://92832de0.ngrok.io -> localhost:3000
Forwarding                    https://92832de0.ngrok.io -> localhost:3000

Connnections                  ttl     opn     rt1     rt5     p50     p90
                              0       0       0.00    0.00    0.00    0.00

The Forwarding URLs point to your local server. Save the URLs and go on to the next step.


Configure your application's endpoints

Now that you've got a public URL you're ready to configure your application's endpoints. We'll be configuring the smsUrl using your ngrok URL and the route reference /incomingSms.

Go to the Apps page in your dashboard. You should see your registered FreeClimb app..

1740

Your Apps page with your registered app

Open its App Config, and you'll se its application ID, alias, and some options for URL configuration. Enter your ngrok URL into the smsUrl field, and add the route /incomingSms at the end of the URL.

https://YOUR-URL.ngrok.io/incomingSms

When you're done the App Config should look something like this:

1380

Example of a completed App Config.

Save your updated App Config.


Experience your app

Once you've updated your App Config you're all ready to run your app! Run the quickstart application with the command:

node receiveMessage.js

Once the quickstart app is running, use your verified number to send a message to your configured FreeClimb number. If everything is set up right, you should receive the message "Hey! It's your application!"

Congratulations! You've just made your first messaging application!


Next steps

For a more detailed explanation of the code used, see our Receive a Message tutorial.