https://github.com/xmatters/xm-labs-slack-steps

Steps for interacting with Slack.
https://github.com/xmatters/xm-labs-slack-steps

Last synced: about 1 month ago
JSON representation

Steps for interacting with Slack.

• Host: GitHub
• URL: https://github.com/xmatters/xm-labs-slack-steps
• Owner: xmatters
• License: mit
• Created: 2020-01-22T18:37:53.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2020-06-25T16:56:17.000Z (over 4 years ago)
• Last Synced: 2024-11-06T08:30:42.301Z (3 months ago)
• Size: 380 KB
• Stars: 0
• Watchers: 5
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Slack Flow Steps

This Workflow contains an **Archive Channel** step for interacting with Slack.



  



# Pre-Requisites

- xMatters account - If you don't have one, [get one](https://www.xmatters.com)!

- Slack account

# Files

- [SlackSteps.zip](SlackSteps.zip)

# Example Usage

This flow shows the inbound HTTP Trigger on the left flowing into a switch step. Based on the state the flow will create a new xM Event for open or Breach, but for Closed will archive the associated Slack channel. 

The response trigger shows that Acknowledge will create a new channel, post a message, then invite several people to the new channel. For a breach, a VIP type is invited so they are aware. 



  



  

# xMatters Configuration

## Import the xMatters Workflow

1. Download the [SlackSteps.zip](SlackSteps.zip) file

2. Follow instructions for [Importing a workflow](https://help.xmatters.com/ondemand/xmodwelcome/workflows/manage-workflows.htm#ImportExport)

## Usage

### Archive Channel

The **Archive Channel** step is used for archiving channels that have been created. Handy for cleaning up all those channels that get created. 



  



The inputs are:

* **Channel Name** - The name or ID of the channel to archive

* **Throw error if not found?** - If the channel is not found, should we throw an error or ignore. This is helpful if there are flows that may not have created a channel as expected. So instead of building another step to see if the channel exists and then archiving, this will just continue happily if the channel is not found rather than throwing an error. 

### Invite Users

The **Invite Users** step is handy for inviting one or more users to a channel. 



  



The inputs are:

* **Channel Name** - The channel or ID to invite users to

* **Username** - The username, or a comma separated list of usernames to invite to the channel. Also supports userId and email addresses. 

## Profit

Add the steps to your desired workflow. 

# Troubleshooting

[Get help using Flow designer](https://help.xmatters.com/ondemand/xmodwelcome/flowdesigner/flow-designer.htm)