Mattermost Nodes
Post messages and attachments to your own Mattermost server from a pipeline, by webhook or bot.
- Operations
- Send Message
Mattermost is a chat platform you host yourself, so plants whose network has no internet connection can still put alarms in front of operators. The Mattermost node posts a message to a channel through the connection's incoming webhook or bot. See the Mattermost connection guide for setting up either mode.
Configuration Quick Reference
| Field | What you choose | Details |
|---|---|---|
| Parameters | Connection, Function, Function Parameters, Timeout Override | Select the connection profile, function, configure function parameters with expression support, and optionally override timeout. |
| Settings | Description, Timeout (seconds), Retry on Timeout, Retry on Fail, On Error | Node description, maximum execution time, retry behavior on timeout or failure, and error handling strategy. All execution settings default to pipeline-level values. |
Mattermost Send Message Node
Mattermost Send Message Node
Post a message, with optional attachments, to a Mattermost channel. A webhook connection posts to the webhook's own channel; a bot connection posts to the channel the function names.
Supported Function Types:
| Function Name | Purpose | Common Use Cases |
|---|---|---|
| Send Message | Post text and attachments to a Mattermost channel | Line-stop alarms, shift summaries, batch completion notices, quality holds |
The channel list you see while building a Send Message function in bot mode comes from the connection's channel picker. It is not a function you can save, so no node returns it.
Retries. A send that Mattermost refused (a bot outside the channel, an archived channel, a revoked token) fails with a permanent error and is not worth retrying. A send whose outcome is unknown (a timeout, a dropped connection, a 5xx or a rate limit) may already be posted, so Retry on Fail can post it twice.
Output
The Mattermost node delivers its data under result, and execution facts (success, functionId, durationMs, timestamp) under _metadata:
| Expression | Description |
|---|---|
$node["Name"].result.via | How the message was posted: webhook (the server answers with no post id) or bot |
$node["Name"].result.postId | The id Mattermost gave the post; present only on a bot connection |
$node["Name"].result.channelId | The channel the post landed in; present only on a bot connection |
$node["Name"].result.createdAt | When the server recorded the post, UTC RFC 3339; present only on a bot connection |
$node["Name"]._metadata.method, $node["Name"]._metadata.connectionId, $node["Name"]._metadata.protocol, $node["Name"]._metadata.authType, $node["Name"]._metadata.message | The call's own facts: the operation, the connection it ran over, mattermost, webhook or bot, and a one-line note about what happened |