Mattermost Trigger icon

Mattermost Trigger

Trigger for Mattermost events

Mattermost Trigger

AI-generated

Overview

This node acts as a trigger for Mattermost events by connecting to a Mattermost WebSocket server. It listens for specific event types such as message postings, user joins, or channel deletions, and emits the event data when these occur. It supports filtering events by channel IDs and can optionally listen to direct messages and group messages. This node is useful for automating workflows based on real-time Mattermost activity, such as notifying other systems when a message is posted or a user joins a team.

Use Case Examples

  1. Trigger a workflow when a new message is posted in specified Mattermost channels to log or process the message content.
  2. Trigger a workflow when a user joins a Mattermost team to update user records or send welcome messages.
  3. Trigger a workflow when a channel is deleted to clean up related resources or notify administrators.

Properties

Name Meaning
Event Type The type of Mattermost event to listen for, such as message posted, user joined, or channel deleted.
WebSocket URL The WebSocket URL of the Mattermost server to connect to for receiving events.
Channel Names or IDs List of channel IDs or names to filter events. Only events from these channels will trigger the node.
Listen to Direct Messages Whether to include events from direct message channels.
Listen to Group Messages Whether to include events from group message channels.

Output

JSON

  • eventData - The JSON data of the triggered Mattermost event. For 'posted' events, this is the parsed message post object; for other events, it is the raw event data.

Dependencies

  • Requires a Mattermost API access token credential for authentication.

Troubleshooting

  • Common issues include WebSocket connection failures due to incorrect WebSocket URL or network issues. Verify the WebSocket URL and network connectivity.
  • Authentication failures if the provided API token is invalid or expired. Ensure the API token credential is valid and has necessary permissions.
  • Event filtering may cause no triggers if channel IDs or event types are incorrectly specified. Double-check the event type and channel filters.
  • The node attempts automatic reconnection with exponential backoff on connection loss, but persistent failures may require checking server status or credentials.

Links

Discussion