MATTERMOST n8n INTEGRATION: AUTOMATE MATTERMOST WITH N8N

This action retrieves multiple user records from your Mattermost instance, making it perfect for syncing user directories, generating reports, or feeding user data into other workflow steps.

Key parameters:

• Credential to connect with: Select your Mattermost account credential (required)
• Resource: Set to "User" to target user data
• Operation: "Get Many" to retrieve multiple records
• Return All: Toggle to fetch all users without limits, or disable to use pagination

Use cases:

• Sync Mattermost users to your HR system or directory
• Generate weekly reports of active users
• Feed user lists into onboarding or offboarding workflows
• Audit user accounts across your organization

When you need information about specific users and already have their unique identifiers, this action retrieves detailed user data based on one or more User IDs.

Key parameters:

• Credential to connect with: Your Mattermost authentication (required)
• User IDs: Text field accepting one or more user ID values (required)
• Additional Fields: Optional extra parameters for refining the request

Use cases:

• Enrich contact data in your CRM with Mattermost profile information
• Verify user existence before performing channel operations
• Pull specific user details for personalized notifications

Retrieve user information when you have an email address but not a User ID. This action is particularly valuable when integrating with systems that primarily use email as an identifier.

Key parameters:

• Credential to connect with: Mattermost account credential (required)
• Resource: Set to "User"
• Operation: "Get By Email"
• Email: Text field for the user's email address (required)

Use cases:

• Look up Mattermost users from form submissions containing email addresses
• Match users between Mattermost and email-based systems like CRM or support tools
• Validate that a user exists before sending them direct messages

This action deactivates a user account in Mattermost, preventing them from logging in while preserving their message history and channel memberships for record-keeping.

Key parameters:

• Credential to connect with: Mattermost authentication (required)
• Resource: "User"
• Operation: "Deactivate"
• User ID: The unique identifier of the user to deactivate (required)

Use cases:

• Automate offboarding when employees leave (triggered by HR system webhooks)
• Temporarily disable accounts during security investigations
• Clean up test or demo accounts after trials end

Provision new user accounts programmatically, perfect for onboarding workflows that need to create Mattermost access alongside other system accounts.

Key parameters:

• Credential to connect with: Mattermost credential (required)
• Username: The desired username for the new account (required)
• Auth Service: Optional dropdown for SSO/LDAP authentication linking
• Auth Data: Additional authentication data if using external auth
• Additional Fields: Add email, nickname, and other profile details

Use cases:

• Automatically create Mattermost accounts when new employees are added to your HR system
• Provision accounts for external contractors with specific naming conventions
• Set up demo accounts for trials or training sessions

Retrieve all reactions on a specific post, useful for tracking engagement, gathering feedback, or triggering actions based on emoji responses.

Key parameters:

• Credential to connect with: Mattermost account (required)
• Resource: "Reaction"
• Operation: "Get Many"
• Post ID: The identifier of the post to check for reactions (optional filter)
• Return All: Toggle to retrieve all reactions or limit results

Use cases:

• Monitor approval posts where team members react to indicate agreement
• Track engagement metrics on announcements
• Trigger follow-up actions when posts receive specific emoji reactions

Remove a specific reaction from a post, enabling you to manage emoji responses programmatically or clean up outdated reactions.

Key parameters:

• Credential to connect with: Mattermost authentication (required)
• Post ID: Identifier of the post containing the reaction (required)
• User Name or ID: Specify whose reaction to remove (optional)
• Emoji Name: The specific emoji reaction to delete (optional)

Use cases:

• Clean up bot reactions after they've served their purpose
• Remove outdated approval reactions when processes restart
• Maintain channel hygiene by removing inappropriate reactions

Add an emoji reaction to a specific post programmatically. This action enables bots to acknowledge messages, indicate status, or participate in reaction-based workflows.

Key parameters:

• Credential to connect with: Mattermost credential (required)
• Post ID: The unique identifier of the target post (required)
• User Name or ID: Which user account adds the reaction
• Emoji Name: The name of the emoji to react with (e.g., "thumbsup", "white_check_mark")

Use cases:

• Acknowledge support requests automatically with a "eyes" emoji
• Mark posts as processed with a checkmark reaction
• Create reaction-based voting or polling systems

Send a temporary message visible only to a specific user within a channel. Ephemeral messages are perfect for notifications, warnings, or instructions that shouldn't clutter the channel for everyone.

Key parameters:

• Credential to connect with: Mattermost authentication (required)
• Resource: "Message"
• Operation: "Post Ephemeral"
• User Name or ID: The recipient who will see the message (required)
• Channel Name or ID: Where the ephemeral message appears (required)
• Message: The content of your ephemeral message (required)

Use cases:

• Send personalized onboarding instructions to new channel members
• Warn users about policy violations without public embarrassment
• Deliver one-time notifications or reminders to specific individuals

The workhorse action for most Mattermost automations—post a message to any channel. This action supports rich formatting, attachments, and various customization options.

Key parameters:

• Credential to connect with: Mattermost account (required)
• Channel Name or ID: Target channel for the message (required)
• Message: The text content to post (required)
• Attachments: Add files or rich attachment cards
• Other Options: Additional message properties like mentions or formatting

Use cases:

• Post daily standup reminders or automated reports
• Announce new deals, deployments, or system status changes
• Forward important notifications from external services to team channels
• Create automated welcome messages for new channel members

Remove a message from a channel using its Post ID. Useful for cleaning up automated messages, removing outdated information, or managing bot-generated content.

Key parameters:

• Credential to connect with: Mattermost credential (required)
• Resource: "Message"
• Operation: "Delete"
• Post ID: The unique identifier of the message to delete (required)

Use cases:

• Remove temporary status messages after they're no longer relevant
• Clean up error messages or test posts from automated workflows
• Implement message lifecycle management for time-sensitive announcements

Retrieve statistical data about a specific channel, including member counts and post activity. Essential for monitoring channel health and generating engagement reports.

Key parameters:

• Credential to connect with: Mattermost authentication (required)
• Resource: "Channel"
• Operation: "Statistics"
• Channel Name or ID: The channel to analyze (required)

Use cases:

• Generate weekly engagement reports across key channels
• Monitor channel growth over time
• Identify inactive channels that might need attention or archiving

Search for channels within a team using keywords. This action helps locate channels dynamically when you don't have their IDs stored.

Key parameters:

• Credential to connect with: Mattermost credential (required)
• Team Name or ID: Which team to search within (required)
• Search Term: Keyword to match against channel names (required)
• Return All: Toggle to get all matches or limit results
• Limit: Maximum number of results when Return All is disabled

Use cases:

• Find project channels dynamically based on project codes
• Locate channels for cleanup or archiving workflows
• Build channel selection interfaces in custom applications

Bring back a previously deleted or archived channel, recovering its history and membership. Valuable for correcting accidental deletions or re-activating seasonal channels.

Key parameters:

• Credential to connect with: Mattermost authentication (required)
• Resource: "Channel"
• Operation: "Restore"
• Channel ID: The unique identifier of the channel to restore (required)

Use cases:

• Recover accidentally deleted channels
• Re-activate project channels when work resumes
• Implement channel lifecycle management with archive/restore cycles

Manage and retrieve channel membership information. This action handles operations related to who belongs to which channels.

Key parameters:

• Credential to connect with: Mattermost credential (required)
• Team Name or ID: The team containing the channel (required)
• Channel Name or ID: Target channel (required)
• Resolve Data: Toggle to convert IDs to readable names
• Return All: Retrieve all members or limit results

Use cases:

• Audit channel memberships for compliance
• Generate lists of channel members for reporting
• Verify user membership before performing channel operations

Permanently remove a channel from your Mattermost instance. This action requires appropriate permissions and should be used carefully.

Key parameters:

• Credential to connect with: Mattermost authentication (required)
• Resource: "Channel"
• Operation: "Delete"
• Channel Name or ID: The channel to delete (required)

Use cases:

• Clean up completed project channels automatically
• Remove test channels after development work
• Implement channel lifecycle policies with automatic deletion

Create new channels programmatically within a team. Perfect for standardizing channel creation or automating project setup workflows.

Key parameters:

• Credential to connect with: Mattermost credential (required)
• Team Name or ID: Where to create the channel (required)
• Display Name: The visible channel name (e.g., "Announcements")
• Name: The system/URL-friendly name (e.g., "announcements")
• Type: "Public" or "Private" visibility setting

Use cases:

• Automatically create channels for new projects from PM tools
• Set up standardized channel structures for new teams
• Generate temporary channels for specific events or campaigns

Add a specific user to a channel, automating membership management without manual intervention.

Key parameters:

• Credential to connect with: Mattermost authentication (required)
• Resource: "Channel"
• Operation: "Add User"
• Channel Name or ID: Target channel (required)
• User Name or ID: The user to add (required)

Use cases:

• Automatically add new employees to relevant channels during onboarding
• Add project team members to project channels when assigned
• Ensure managers are added to their team channels automatically