STRAX Reach · Team and community chat

Mattermost conversations through a slash command

Partners on a self-hosted Mattermost server type /reach with their question, and the answer comes back as a direct message from your bot.

Part of Reach
  • /reach slash command
  • Command token check
  • Bot direct messages

Built for self-hosted chat

Mattermost posts each /reach command to Reach with the command token in the body. Reach checks the token, strips it from what it stores and files the message against the sender.

Answers go out as direct messages from a bot account through the Mattermost API. A partner links their user id to an account by sending /reach link with a code.

Many banks and payment processors run Mattermost on their own networks for compliance reasons. The slash command lets their staff reach your operations team without leaving that environment, and every exchange is kept on your side as well.

Where it helps

Bank partner channels

Partner banks that run Mattermost internally ask your operations team about settlement files.

Operational escalations

Their operators raise a payment issue with /reach and follow the answer in a direct message.

Closed networks

Keep partner conversations on infrastructure both sides host themselves.

File exchange coordination

Coordinate the timing of daily settlement file drops with a partner's operations staff, who confirm receipt over the command.

What you need

  • A Mattermost server

    Reachable from the install, or able to reach its public address.

  • A bot account

    With an access token and its user id.

  • A custom slash command

    Set to post to the Reach inbound address; Mattermost shows the command token when you save it.

  • Reach Core

    The records and console the command files into.

Good to know

Needs a STRAX build with the body-token signature scheme from 24 September 2026. Ordinary direct messages to the bot need the WebSocket API, which this version does not use.

Questions

Can we use an outgoing webhook instead?

Yes, pointed at the same address. Outgoing webhooks only fire in public channels, so the slash command suits private questions better.

Where do answers appear?

As a direct message from your bot to the person who asked.

What is still missing?

Interactive message buttons and reading direct messages without the command.

Does our server need to reach theirs?

Their Mattermost server calls your public address for commands, and Reach calls their server to post replies, so both addresses must be reachable in the directions described.

Can several teams answer through one bot?

Yes, every answer is written in the Reach console, so any agent with access can reply and the partner still sees one bot.

Read more

Add Mattermost to Reach

Tell us which channels your clients use and we will plan the rollout with your team.

Premium Requires STRAX Reach - Core, which is licensed.

About this listing

Version1.0.0
AuthorSTRAX
CategoryCommunication
Published2026-09-24

What's inside

Credential 2
Global variable 2
Workflow 2

What happens on install

After the import, and only with your consent, the installer runs:

  • Reach - Register Channel : Registers the Mattermost channel with Reach Core, disabled until its credentials are entered
Security screening. This bundle carries executable workflow steps. These flags are recomputed server-side from the actual package contents (they are never taken from the author), and STRAX asks for your explicit consent before installing executable content.

Free listing

Install it from Feature Marketplace inside STRAX

It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.

Open Feature Marketplace

In your STRAX installation, open Feature Marketplace from the navigation.

Find "STRAX Reach - Mattermost"

Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.

Install

Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.

Back to the catalogue →

See it on your own systems.

A demo takes an hour, on your data landscape rather than ours.