{"id":1842,"date":"2025-07-06T19:30:13","date_gmt":"2025-07-06T17:30:13","guid":{"rendered":"https:\/\/cln.io\/blog\/?p=1842"},"modified":"2025-07-11T22:33:48","modified_gmt":"2025-07-11T20:33:48","slug":"mattermost-bridge-consolidating-messages-from-multiple-external-servers","status":"publish","type":"post","link":"https:\/\/cln.io\/blog\/mattermost-bridge-consolidating-messages-from-multiple-external-servers\/","title":{"rendered":"Mattermost Bridge: Consolidating Messages from Multiple External Servers"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">NOTE:\u00a0Claude Opus 4 was used for the blog post and the project on github<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/github.com\/cln-io\/mattermost-bridge\">https:\/\/github.com\/cln-io\/mattermost-bridge<\/a><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Requirements<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">We needed a solution to monitor (multiple) external Mattermost instances and forward relevant messages to our primary Mattermost server. <\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The specific requirements were:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Monitor specific channels on various external Mattermost servers (run 1 docker per external server, to be seen if I make it multi server compatible)<\/li>\n\n\n\n<li>Forward messages in real-time to designated channels on our main server<\/li>\n\n\n\n<li>Preserve message context (author, timestamp, origin server)<\/li>\n\n\n\n<li>Handle file attachments seamlessly<\/li>\n\n\n\n<li>Support MFA-enabled accounts<\/li>\n\n\n\n<li>Maintain professional appearance of forwarded messages<\/li>\n\n\n\n<li>Minimize manual configuration and maintenance<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Screenshots<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The left mattermost (the one we want to monitor messages on) has a user posting a message<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"322\" src=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/sourcemm-1024x322.png\" alt=\"The left mattermost (the one we want to monitor messages on) has a user posting a message:\" class=\"wp-image-1846\" title=\"\" srcset=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/sourcemm-1024x322.png 1024w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/sourcemm-300x94.png 300w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/sourcemm-768x241.png 768w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/sourcemm-1536x483.png 1536w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/sourcemm.png 1712w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><figcaption class=\"wp-element-caption\"><br>The bridge will mirror the message to the right mattermost (the destination mattermost)<\/figcaption><\/figure>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"447\" src=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/example-1024x447.png\" alt=\"\" class=\"wp-image-1845\" srcset=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/example-1024x447.png 1024w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/example-300x131.png 300w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/example-768x335.png 768w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/example-1536x671.png 1536w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/example.png 1690w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The console \/ app log:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"925\" src=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/console-light-1024x925.png\" alt=\"\" class=\"wp-image-1843\" srcset=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/console-light-1024x925.png 1024w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/console-light-300x271.png 300w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/console-light-768x694.png 768w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/console-light-1536x1388.png 1536w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/console-light.png 1970w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\">Built-in Status Monitoring<a href=\"https:\/\/github.com\/cln-io\/mattermost-bridge#built-in-status-monitoring\"><\/a><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">As we use mattermost on the fly, I don&#8217;t want to check dockerlogs to verify all is going well, so the bridge includes a built-in status channel that provides real-time monitoring of bridge activity and logs. When enabled with\u00a0<code>STATS_CHANNEL_UPDATES=logs<\/code>, it creates a dedicated #mattermost-bridge-status channel that continuously updates with:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Event summaries<\/strong>\u00a0&#8211; Message counts and bridge activity<\/li>\n\n\n\n<li><strong>Live log feed<\/strong>\u00a0&#8211; Last 30 log lines updated every 10 minutes<\/li>\n\n\n\n<li><strong>Single message updates<\/strong>\u00a0&#8211; No channel spam, just one continuously updated status message<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"625\" src=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/status-channel-1024x625.png\" alt=\"\" class=\"wp-image-1850\" srcset=\"https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/status-channel-1024x625.png 1024w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/status-channel-300x183.png 300w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/status-channel-768x469.png 768w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/status-channel-1536x937.png 1536w, https:\/\/cln.io\/blog\/wp-content\/uploads\/2025\/07\/status-channel-2048x1250.png 2048w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Solution<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Mattermost Bridge is a TypeScript application that connects to multiple Mattermost instances simultaneously and forwards messages between them.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Key Features<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Real-time Message Forwarding<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>WebSocket connections for instant message detection<\/li>\n\n\n\n<li>Automatic forwarding to configured target channels<\/li>\n\n\n\n<li>No polling delays or missed messages<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Complete Context Preservation<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Original author name and profile picture<\/li>\n\n\n\n<li>Source server identification<\/li>\n\n\n\n<li>Original timestamps<\/li>\n\n\n\n<li>All file attachments re-uploaded to target server<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Professional Message Presentation<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Forwarded messages appear as formatted attachments<\/li>\n\n\n\n<li>Clean blue styling distinguishes forwarded content<\/li>\n\n\n\n<li>Clear metadata showing origin and context<\/li>\n\n\n\n<li>Maintains readability in busy channels<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Robust Architecture<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Automatic reconnection on network failures<\/li>\n\n\n\n<li>Profile picture caching to reduce API calls<\/li>\n\n\n\n<li>Configurable rate limiting<\/li>\n\n\n\n<li>Comprehensive error logging<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><\/h2>\n","protected":false},"excerpt":{"rendered":"<p>NOTE:\u00a0Claude Opus 4 was used for the blog post and the project on github https:\/\/github.com\/cln-io\/mattermost-bridge Requirements We needed a solution to monitor (multiple) external Mattermost instances and forward relevant messages to our primary Mattermost server. [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":1847,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[57,3,26,58],"tags":[],"class_list":["post-1842","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-apis","category-automation","category-it","category-miscellaneous"],"_links":{"self":[{"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/posts\/1842","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/comments?post=1842"}],"version-history":[{"count":2,"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/posts\/1842\/revisions"}],"predecessor-version":[{"id":1851,"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/posts\/1842\/revisions\/1851"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/media\/1847"}],"wp:attachment":[{"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/media?parent=1842"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/categories?post=1842"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cln.io\/blog\/wp-json\/wp\/v2\/tags?post=1842"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}