Skip to main content
U.S. flag

An official website of the United States government

Dot gov

The .gov means it’s official.
Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.

Https

The site is secure.
The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

Slack integrations

Back to Slack page

We have a few different Slack Apps and bots you’ll see in Slack:

  • Angry Tock: our fierce timesheet reminder.
  • Charlie, a.k.a. El Hubot Real: our Hubot instance. Knows all kinds of tricks. To get a list of them, send Charlie a direct message with the word help.
  • coffeemate: send a message with coffee me in a public channel or direct message @Charlie (El Hubot Real) with coffee me to set up a virtual coffee/tea with a random coworker.
  • Slackbot: We automate responses to frequently asked questions with a Slackbot. You can update or customize responses here. (You can also add emoji). Do not include private or sensitive information in Slackbot automatic responses.

Learn more about some of our unique channel customizations and auto-responses in the Slack @ TTS guide.

If you’re interested in learning more about the bots, or perhaps contributing to them, pop into #bots.

New integrations

You can add new “configurations” of pre-approved integrations to Slack, for things like posting Trello or GitHub notifications to a Slack channel. You can also freely add new configurations for “Incoming WebHooks,” which is on a different page. For any new integration types, please follow the process below.

Integration request form

Note this is only necessary for new bots or types of integrations — approval is not needed for new “configurations” of a previously-approved App. The form should be filled out again if the nature of the connection changes, e.g. a webhook connection changes to using OAuth.

Before completing this form, you might need to research how the integration interacts with Slack. For example, does the integration have read access to channels or not? Reach out to #admins-slack and/or Slack support for help.

New integrations being built/hosted by GSA should be developed against the test Slack—ask in #admins-slack for access. When ready to be integrated into the TTS Slack, fill out the form.

Responses will be reviewed in this spreadsheet. Edit the form.

New integrations/bots need approval from the following:

  • TTS Slack admins
  • Security Engineering (ISE)
  • OCTO
  • GSA IT Slack admins

Considerations:

  • Read access from Slack (e.g. RSS) will almost definitely be approved.
  • One-way integrations into Slack (e.g. via webhooks) are almost always fine.
  • Integrations from higher-risk systems (Moderate or High) into Slack will generally not be approved.
  • TTS Tech Portfolio will advise a hard veto on any externally hosted bots that can read all the messages in channels they are invited into and the only utility from the bot is achieved if they are invited into more or less all the channels.

Questions?