Gateway config (channel rules)

Channel configuration for each protocol

⚠️ Needs to be lowercase

Below you can find how the channels (protocolchannel and protocol2channel) should be filled in:

• discord
  • channel_name
    • without the #
  • ID:123456789
    • where 123456789 is the channel ID
• gitter
  • username/room
    • as seen in the gitter.im url
• hipchat
  • id_channel
    • see here for the correct channel
• irc
  • #channel_name
    • # is required
    • must be lowercase
• keybase
  • channel_name
    • without the #
    • if your team doesn't have multiple channels, use general
• matrix
  • #channel:server
    • e.g. #yourchannel:matrix.org
    • encrypted rooms are not supported in matrix
• mattermost
  • channel_name
    • the channel name as seen in the URL, not the displayname
    • https://yourmattermostserver/yourteam/channels/channel_name <- channel_name
• msteams
  • `channel="19:[email protected]"
    • as seen in the URL ?threadId=19:[email protected]
    • more information
• rocketchat
  • #channel_name
    • # is required (also for private channels)
• slack
  • channel_name
    • without the #
  • ID:C123456
    • where C123456 is the channel ID
    • does not work with webhook
• sshchat
  • channel_name must be channel="sshchat"
• steam
  • chatid
    • a large number
    • the number in the URL when you click "enter chat room" in the browser
• telegram
  • channel
    • a large negative number, eg -123456789
    • more information
• whatsapp
  • [email protected]
    • a unique group JID
    • if you specify an empty string bridge will list all the possibilities
  • "Group Name"
    • if you specify a group name the bridge will hint its JID to specify as group names might change in time and contain weird emoticons
• xmpp
  • channel_name
• zulip
  • stream/topic:mytopic
    • without the #

Discord

See Section docs for special features