- Status: ???
- Maintainers: @asdfzdfj
- Features: ???
Basic configuration example:
[slack]
[slack.myslack]
RemoteNickFormat="{BRIDGE} - @{NICK}"
# this requires *two* different tokens
Token="xoxb-*****"
AppToken="xapp-*****"
# this will maps threads from other bridges on slack threads
PreserveThreading=trueSee account.md.
Did you set RemoteNickFormat?
Try adding RemoteNickFormat="<{NICK}>"
If you're using WebhookURL in your Slack configuration, this is normal.
If you only have Token configuration, this could be a bug. Please open an issue.
If you get the message:
ERROR slack: Connection failed "not_allowed_token_type" &errors.errorString{s:"not_allowed_token_type"}
For more information look at:
- slackapi/node-slack-sdk#921 (comment)
- https://github.com/nlopes/slack/issues/654
- our issue 42wim#964
The bot based setup can currently operate in 2 modes:
-
socket mode Events API mode (recommended, preferred)
this mode works with modern Slack apps and is recommended for setting up Slack bridges. However this mode requires two tokens to operate:- a Bot User OAuth Token bot token having prefix
xoxb-, configured withToken=option - an App token having prefix
xapp-, configured withAppToken=option
- a Bot User OAuth Token bot token having prefix
-
legacy RTM mode
previously the primary mode of operation for the bridge. This mode only works with bot token belonging to a classic Slack apps; and as of 2024-06-04 it's no longer possible to create any new classic Slack apps. This mode only requires a single bot tokenToken=to be configured.If you already have an existing bridge setups with classic Slack apps then it should continue to work as before without changing the existing Slack app settings or matterbridge config (leave the
AppToken=unset or set to empty value). Should you want to set up a new bridge, then the socket mode Events API mode is the recommended (and the only) way forward.