A guide to incident response playbooks
Learn the importance of incident response playbooks, how they enhance incident management, and automate your playbook with n8n workflow templates in this comprehensive article.
Back to Integrations 
Webhook and Mattermost integration
Save yourself the work of writing custom integrations for Webhook and Mattermost and use n8n instead. Build adaptable and scalable Development, Core Nodes, and Communication workflows that work with your technology stack. All within a building experience you will love.
How to connect Webhook and Mattermost
- Step 1: Create a new workflow
- Step 2: Add and configure nodes
- Step 3: Connect
- Step 4: Customize and extend your integration
- Step 5: Test and activate your workflow
Step 1: Create a new workflow and add the first step
In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.
Step 2: Add and configure Webhook and Mattermost nodes
You can find Webhook and Mattermost in the nodes panel. Drag them onto your workflow canvas, selecting their actions. Click each node, choose a credential, and authenticate to grant n8n access. Configure Webhook and Mattermost nodes one by one: input data on the left, parameters in the middle, and output data on the right.
Step 3: Connect Webhook and Mattermost
A connection establishes a link between Webhook and Mattermost (or vice versa) to route data through the workflow. Data flows from the output of one node to the input of another. You can have single or multiple connections for each node.
Step 4: Customize and extend your Webhook and Mattermost integration
Use n8n's core nodes such as If, Split Out, Merge, and others to transform and manipulate data. Write custom JavaScript or Python in the Code node and run it as a step in your workflow. Connect Webhook and Mattermost with any of n8n’s 1000+ integrations, and incorporate advanced AI logic into your workflows.
Step 5: Test and activate your Webhook and Mattermost workflow
Save and run the workflow to see if everything works as expected. Based on your configuration, data should flow from Webhook to Mattermost or vice versa. Easily debug your workflow: you can check past executions to isolate and fix the mistake. Once you've tested everything, make sure to save your workflow and activate it.
Popular Webhook and Mattermost workflows
+5
Standup bot (4/4): Worker
This is the fourth workflow for the Mattermost Standup Bot. This workflow sends the team a message every morning to ask them three standup questions.
What have you accomplished since your last report?
What do you want to accomplish until your next report?
Is anything blocking your progress?
Once answered, the answers are sent to a Mattermost channel.
The "Read Config" nodes will need to be updated to point to the ID of the "Standup Bot - Read Config" workflow and the "Override Config" node will need to point to "Standup Bot - Override Config"
Manage custom incident response in PagerDuty and Jira
This workflow automatically follows the steps in a custom incident response playbook and manages incidents in PagerDuty, Jira tickets, and notifies the on-call team in Mattermost.
This workflow consists of three sub-workflows, each automating specific steps in the playbook. Read more about this use case and learn how to set up the workflows step-by-step in the blog tutorial How to automate every step of an incident response workflow.
Prerequisites
A PagerDuty account and credentials
A Mattermost account and credentials
A Jira account and credentials
Nodes
Webhook nodes trigger the workflows when an incident is created in PagerDuty, and when the incidedent is acknowledged and resolved.
Mattermost nodes create an auxiliary channel for the on-call team to discuss the incident with buttons to acknowledge the incident and mark it as resolved.
PagerDuty nodes update the status of the incident.
Jira nodes create an issue about the incident and update its status when it's resolved.
Webhooks with Mattermost
Does pretty much what this workflow does but is triggered by a slash command using a Webhook node.
Send a message on Mattermost when a workflow is updated
This workflow allows you to send a message on Mattermost when a workflow is updated.
Workflow Trigger node: The Workflow Trigger node will trigger the workflow when the workflow gets updated.
Mattermost node: This node will send a message on Mattermost, notifying you about the update.
Incident Response Workflow - Part 3
This workflow is the third of three. You can find the other workflkows here:
Incident Response Workflow - Part 1
Incident Response Workflow - Part 2
Incident Response Workflow - Part 3
We have the following nodes in the workflow:
Webhook node: This trigger node listens to the event when the Resolve button is clicked.
PagerDuty node: This node changes the status of the incident report from Acknowledged to Resolved in PagerDuty.
Jira Software node: This node moves the incident issue to Done.
Mattermost node: This node publishes a message in the auxiliary channel mentioning that the incident has been marked as resolved in PagerDuty and Jira.
Mattermost node: This node publishes a message in the specified Incidents channel that the incident has been resolved by the on-call team.
Incident Response Workflow - Part 2
This workflow is the second of three. You can find the other workflkows here:
Incident Response Workflow - Part 1
Incident Response Workflow - Part 2
Incident Response Workflow - Part 3
We have the following nodes in the workflow:
Webhook node: This trigger node listens to the event when the Acknowledge button is clicked.
PagerDuty node: This node changes the status of the incident report from 'Triggered' to 'Acknowledged' in PagerDuty.
Mattermost node: This node publishes a message in the auxiliary channel saying that the status of the incident report has been changed to Acknowledged.
Gender inclusive language bot for Mattermost
This workflow ensures gender inclusive language in Mattermost channels. If someone addresses the group with “guys” or “gals”, a bot promptly replies with: "May I suggest “folks” or “y'all”? We use gender inclusive language here. 😄".
Webhook node**: triggers the workflow when a new message is posted in Mattermost.
IF node**: verifies if the message includes the words "guys" or "gals". If false, it does not take any action. If true, it triggers the Mattermost node.
Mattermost node**: posts the language warning message in the Mattermost channel.
Start a Whereby video call from Mattermost
Companion workflow for blog post
Build your own Webhook and Mattermost integration
Create custom Webhook and Mattermost workflows by choosing triggers and actions. Nodes come with global operations and settings, as well as app-specific parameters that can be configured. You can also use the HTTP Request node to query data from any app or service with a REST API.
Webhook and Mattermost integration details
Webhook
Webhooks are automatic notifications that apps send when something occurs. They are sent to a certain URL, which is effectively the app's phone number or address, and contain a message or payload. Polling is nearly never quicker than webhooks, and it takes less effort from you.
Other integrations with Mattermost
Webhook and Mattermost integration tutorials
5 workflow automations for Mattermost that we love at n8n
Discover five of our favorite use cases of n8n with Mattermost, for both work productivity and team engagement.
How to automate your team's video collaboration workflow
Create a custom Mattermost slash command that helps to quickly connect with other team members via Whereby.
FAQs
Can Webhook connect with Mattermost?
Can I use Webhook’s API with n8n?
Can I use Mattermost’s API with n8n?
Is n8n secure for integrating Webhook and Mattermost?
How to get started with Webhook and Mattermost integration in n8n.io?
Looking to integrate Webhook and Mattermost in your company?
Over 3000 companies switch to n8n every single week
Why use n8n to integrate Webhook with Mattermost
Build complex workflows, really fast
