-
Notifications
You must be signed in to change notification settings - Fork 625
Gateway config (channel rules)
Victor edited this page Oct 31, 2019
·
17 revisions
Below you can find how the channels (protocolchannel
and protocol2channel
) should be filled in:
- irc
-
#channel_name
- # is required
- must be lowercase
-
- slack
-
channel_name
- without the #
-
ID:C123456
- where C123456 is the channel ID
- does not work with webhook
-
- discord
-
channel_name
- without the #
-
ID:123456789
- where 123456789 is the channel ID
-
- mattermost
-
channel_name
- the channel name as seen in the URL, not the displayname
- https://yourmattermostserver/yourteam/channels/channel_name <- channel_name
-
- gitter
-
username/room
- as seen in the gitter.im url
-
- xmpp
channel_name
- telegram
-
chatid
- a large negative number, eg -123456789
- more information
-
- hipchat
-
id_channel
- see here for the correct channel
-
- rocketchat
-
#channel_name
- # is required (also for private channels)
-
- matrix
-
#channel:server
- e.g.
#yourchannel:matrix.org
- encrypted rooms are not supported in matrix
- e.g.
-
- steam
-
chatid
- a large number
- the number in the URL when you click "enter chat room" in the browser
-
- 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
-
- zulip
-
stream/topic:mytopic
- without the #
-
See Section docs for special features
Getting started
How to create your config
Discord bot setup
Slack bot setup
MS Teams setup
Deploy
DigitalOcean
Azure
Docker
Heroku
Gateways
Config: basic
Config: channel rules
Discord
Gitter
Hipchat
IRC
Keybase
Matrix
Mattermost
Microsoft Teams
Mumble
Nextcloud Talk
RocketChat
Slack
Sshchat
Steam
Telegram
Twitch
VK
WhatsApp
XMPP
Zulip
Advanced
Mediaserver setup
Service files
Developer
API
Tengo scripting
Making gateways