matrix-docker-ansible-deploy/docs/configuring-playbook-bridge-mautrix-slack.md

Setting up Mautrix Slack bridging (optional)

^{Refer the common guide for configuring mautrix bridges: Setting up a Generic Mautrix Bridge}

The playbook can install and configure mautrix-slack for you.

See the project's documentation to learn what it does and why it might be useful to you.

See the features and roadmap for more information.

Prerequisites

For using this bridge, you would need to authenticate by providing your username and password (legacy) or by using a token login. See more information in the docs.

Note that neither of these methods are officially supported by Slack.

Enable Appservice Double Puppet (optional)

If you want to set up Double Puppeting (hint: you most likely do) for this bridge automatically, you need to have enabled Appservice Double Puppet service for this playbook.

See this section on the common guide for configuring mautrix bridges for details about setting up Double Puppeting.

Adjusting the playbook configuration

To enable the bridge, add the following configuration to your inventory/host_vars/matrix.example.com/vars.yml file:

matrix_mautrix_slack_enabled: true

Extending the configuration

There are some additional things you may wish to configure about the bridge.

See this section on the common guide for configuring mautrix bridges for details about variables that you can customize and the bridge's default configuration, including bridge permissions, encryption support, relay mode, bot's username, etc.

Installing

After configuring the playbook, run it with playbook tags as below:

ansible-playbook -i inventory/hosts setup.yml --tags=setup-all,start

The shortcut commands with the just program are also available: just install-all or just setup-all

just install-all is useful for maintaining your setup quickly (2x-5x faster than just setup-all) when its components remain unchanged. If you adjust your vars.yml to remove other components, you'd need to run just setup-all, or these components will still remain installed. Note these shortcuts run the ensure-matrix-users-created tag too.

Usage

To use the bridge, you need to start a chat with @slackbot:example.com (where example.com is your base domain, not the matrix. domain).

You can then follow instructions on the bridge's official documentation on Authentication.

If you authenticated using a token, the recent chats will be bridged automatically (depending on the conversation_count setting). Otherwise (i.e. logging with the Discord application), the chats the bot is in will be bridged automatically.

Troubleshooting

As with all other services, you can find the logs in systemd-journald by logging in to the server with SSH and running journalctl -fu matrix-mautrix-slack.

Increase logging verbosity

The default logging level for this component is warn. If you want to increase the verbosity, add the following configuration to your vars.yml file and re-run the playbook:

# Valid values: fatal, error, warn, info, debug, trace
matrix_mautrix_slack_logging_level: 'debug'