Define Automations for Slack operations

hackforla / ops

A repository for the OPS Community of Practice

MIT License

8 stars 7 forks source link

We need to define what automations Admin and projects need so that we can create a requirements document for a Slack Bot platform

[ ] Brainstorm ideas
[ ] Create Spreadsheet
[ ] Prioritize
[ ] Gather more info on the ideas that are Must Haves
[ ] Review Hack for LA's Bot History (some details available in the comments on this issue - do not read the history until we have other ideas, because it keeps pulling the project off track and killing any initiative anyone has!

### Proposal Overview

### Resources

### Priority
- [ ] Must Have
- [ ] Should Have
- [ ] Could Have
- [ ] Won't Have this time

When backend services go down, it would be convenient if the relevant team could be notified on Slack so they can address the issue.

These steps are part of the original proposal https://github.com/hackforla/ops/issues/1 and won't necessarily be used in this way.

[ ] Create a Slack app with "incoming webhooks" enabled.
[ ] For each team that wants to use the Slack app, create a webhook that's connected to the channel they want to receive notifications in.
[ ] Each team can connect to their webhook from whatever backend services they're using. This would have to be done on a team-by-team basis.

These are the Slack instructions for creating an app with incoming webhooks. https://api.slack.com/messaging/webhooks

hackforla / ops