Next, go to the OAuth & Permissions screen (link on the left-hand side under Features). Once it's created, you'll need to grab the app's Signing Secret for use with our integration. Go to the Slack App console and create a new app. That's all we need from RingCentral for now!Ĭonfiguring the Slack application itself is equally straight-forward.

Your phone extension (by default this is 101, so we'll just use that).

Your account phone number (this is also be your username).

The API server URL (this should be for their dev/test platform).Once you've created an app, you can grab all of the credentials you'll need to configure our integration. I'll step through some significant functionality below once we've configured the rest of our credentials. Once your system is configured, you can clone my existing project and take a look through the code. That said, the next thing we need to do is configure our AWS credentials for Serverless to use - rather than walk you though those steps here, I'll refer you to Serverless' excellent configuration walkthrough. When we're ready to deploy our application, a simple sls deploy will push everything up to AWS. We install this tool globally to make the sls command available everywhere. We'll be leveraging the Serverless framework, so if you don't already have that installed go ahead and install it: Today we'll walk through the components required and all the steps for wiring together the full application.įirst things first, we need to build the application itself. Last time, we talked about my motivations for building a Slack autoresponder so I can better communicate with my colleagues.

$ npm install slack-keep-presence