An open source integration manager for Matrix

Try it out or run your own

Visit t2bot.io/riot and log in with your Matrix account or point your Riot config.json at our servers:

{{ integrationsConfig }}

Widgets

Add utility for everyone in your room by embedding an application.

Jitsi
Etherpad
TradingView
Spotify
YouTube
Twitch Livestream
Grafana
Google Docs
Google Calendar
Custom Widget

Bots

Bots bring entertainment or productivity to the room. They're here to help at your command.

Guggy
Giphy
Imgur
Google Image Search
Wikipedia
Travis CI
RSS Notifications
Echo
Custom Bots

Bridges

Bring the outside world into your room with bridges.

IRC
Telegram
Gitter
Slack
Webhooks

Stickers

Have some fun and post a sticker.

Huskies
Cats
Cat Faces
Loading Artist

Welcome to Dimension!

Join #dimension:t2bot.io for news and updates. Don't forget to star the repository on GitHub.

Here's the configuration options you'll need to update in your Riot config.json:

{{ integrationsConfig }}

Configuring integrations

If everything is set up correctly, you'll be able to access the admin area of Dimension by clicking the 3x3 grid in the top right of any room in Riot. The gear icon () in the top right is where you can configure your bots, bridges, and widgets.

"Could not connect to integrations server" error

When Riot cannot reach Dimension or Dimension is unable to reach your homeserver an error saying "Could not contact integrations server" shows up in every room. Before visiting us in #dimension:t2bot.io on Matrix, here's a few things to check:

  • Verify the homeserver configuration in Dimension. The name, client/server URL, and access token all need to be valid and directed at your homeserver.
  • Verify federation is enabled on your homeserver. Even in a private, or non-federated, environment federation needs to be enabled so Dimension can work correctly. Dimension should still work okay if federation on your homeserver is bound to a private interface instead of being public - just be sure to set the federation URL in your configuration.
  • Verify that federation is working on your homeserver. Using tools like the federation tester, make sure that federation is working on your homeserver.