Slack App Integration
Sym uses Slack as its main control for making, routing, and approving requests.
Overview
Sym uses a special sym_integration
resource to connect with your Slack workspace. It requires only a name
and an external_id
, which is the ID of the target Slack workspace where Sym requests will be sent. For more information on the sym_integration
resource, see our Terraform Provider docs.
Did you use
symflow init
?If you followed our 10 Minute Quickstart, you will already have a Slack
resource
created in Terraform.
Changing Slack workspaces
If you've set Sym up on a test workspace and want to move the same configuration over to production, simply change the external_id
in Terraform, and re-apply
your configuration. That will leave the rest of your configuration unchanged, while routing all requests to the newly defined workspace.
resource "sym_integration" "slack" {
type = "slack"
name = "${local.environment_name}-slack"
#This is your Slack workspace ID
external_id = "T12345"
}
Reinstall Slack app
Here at Sym, we are constantly adding new features. Occasionally, they require a Slack scope that the older version of the app does not have. This means that in order to use a few specific new features, you may need to reinstall the Sym app.
Feature | Required Scopes | Date Added |
---|---|---|
Slackbot responds to DMs in messages tab | im:history | Apr 6, 2022 |
Post to a public channel without joining | chat:write.public , mpim:read | Dec 19, 2022 |
Use the slack.is_user_in_group SDK function | usergroups:read | August 22, 2023 |
Updated 3 days ago