Setting Up Slack Integration

Introduction

Sprintly offers integration with Slack. Slack is a chat messaging, archiving and search system. Our integration posts messages for new items and all comments to a designated Slack channel or direct message recipient. 

To enable the integration you will need to be a Sprintly admin, set up the incoming webhook in Slack and the Services setting in Sprintly.

Setting Up Slack's Incoming Webhook

1. Log into your Slack account and go to https://my.slack.com/services/new/incoming-webhook

2. Click on the Add New Integration link on the left-hand side. 

3. Scroll down and select Incoming Webhooks.

4. Select a channel/direct message recipient and click the green Add Incoming WebHook button. 

5. A green "New Integration added!" confirmation message will appear. Scroll down the page and copy the URL under "Your Unique Webhook URL." It will look something like this:  https://yourcompany.slack.com/services/hooks/incoming-webhook?token=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

6. Under the Integration Settings section, you have the option to label your integration, change the name of your Slack bot and its icon. By default, the bot name is incoming-webhook and the default icon is a Sprintly icon. These are optional settings. 

7. Scroll down to the bottom of the page and click the blue Save Integration button.


Setting Up Sprintly Services
Once you have the incoming webhook set-up in Slack, you will need to add it to your Sprintly Services.

1. Locate the Services menu from your Sprintly Settings. Only account owners and admins have access to these settings: 


2. Select the applicable Sprintly product and Slack from the Services drop-down menu:



3. The webhook field will display.  Paste the unique incoming webhook copied from Slack settings. 

5. Select the Enabled checkbox and click the green Save Slack Webhook Configuration button. 

The set up for your Sprintly + Slack is now complete! New Sprintly items and comments to items will now post to the designated channel. 


Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk