mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
b5f007d35e
* docs: resolve cross-file anchor mismatches from RST-to-MDX migration
The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.
Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.
* docs: manually resolve remaining anchor mismatches after cross-file audit
Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):
- Typos and dropped words carried over from the original Sphinx docs
(e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
"follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
(environment-configuration-settings instead of
push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
(authentication-configuration-settings#saml-2-0), recovered from the
original RST label definition that the automated registry missed
because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
malformed-path anchors to correct page links.
* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)
github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.
* docs: fix broken path links found during docs/main migration cleanup
* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components
* docs: restore missing Kubernetes deployment architecture diagrams
The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.
* docs: fix 7 anchor mismatches from the fragment/heading audit
Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
(experimental-configuration-settings, push-notification-server-
configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
of being used as a real cross-page link.
* docs: fix 8 anchor slugs that were close but didn't match the real heading
Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.
* docs: merge split Tabs blocks so tabs render horizontally
The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.
* docs: remove Azure tab and restore Kubernetes deploy content
The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.
* addresscoderabbitreview
* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement
Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.
Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.
* docs: fix review findings — image alt text, Important callout markup, typo
- Replace generic alt="image" on scaling diagrams with descriptive text
identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.
---------
Co-authored-by: Hanzo Dev <[email protected]>
147 lines
6.6 KiB
Plaintext
147 lines
6.6 KiB
Plaintext
---
|
||
title: "Integrations Guide"
|
||
---
|
||
Mattermost provides a variety of methods to integrate with your favorite tools, automate critical workflows, and extend the capabilities of the platform. This guide provides a high-level overview of integration options and the level of technical skills required [(no-code, low-code, or pro-code)](/integrations-guide/faq#what-is-meant-by-no-code-low-code-and-pro-code), and links to detailed documentation for each.
|
||
|
||
## Choose Your Path
|
||
|
||
<table>
|
||
<colgroup>
|
||
<col style={{width: '15%'}} />
|
||
<col style={{width: '40%'}} />
|
||
<col style={{width: '45%'}} />
|
||
</colgroup>
|
||
<thead>
|
||
<tr>
|
||
<th>Skill Level</th>
|
||
<th>Best Options</th>
|
||
<th>Examples</th>
|
||
</tr>
|
||
</thead>
|
||
<tbody>
|
||
<tr>
|
||
<td><a href="mm-ref:no-code">No-code</a></td>
|
||
<td><ul>
|
||
<li><a href="#pre-built-plugins">Pre-built plugins</a></li>
|
||
<li><a href="#built-in-slash-commands">Built-in slash commands</a></li>
|
||
<li><a href="#no-code-automation-platforms">No-code automation</a></li>
|
||
<li><a href="#mattermost-playbooks">Playbooks</a></li>
|
||
</ul></td>
|
||
<td><ul>
|
||
<li>Connect Jira, GitHub, Zoom</li>
|
||
<li>Command line interactions</li>
|
||
<li>Automate with n8n, Zapier</li>
|
||
<li>Run incident playbooks</li>
|
||
</ul></td>
|
||
</tr>
|
||
<tr>
|
||
<td><a href="mm-ref:low-code">Low-code</a></td>
|
||
<td><ul>
|
||
<li><a href="#webhooks">Webhooks</a></li>
|
||
<li><a href="#custom-slash-commands">Custom slash commands</a></li>
|
||
</ul></td>
|
||
<td><ul>
|
||
<li>Send monitoring alerts</li>
|
||
<li>Trigger actions with keywords</li>
|
||
</ul></td>
|
||
</tr>
|
||
<tr>
|
||
<td><a href="mm-ref:pro-code">Pro-code</a></td>
|
||
<td><ul>
|
||
<li><a href="#restful-api">REST API</a></li>
|
||
<li><a href="#custom-built-plugins">Custom plugins</a></li>
|
||
</ul></td>
|
||
<td><ul>
|
||
<li>Build custom apps</li>
|
||
<li>Extend Mattermost core</li>
|
||
</ul></td>
|
||
</tr>
|
||
</tbody>
|
||
</table>
|
||
|
||
## Integration Options
|
||
|
||
### Plugins
|
||
|
||
Learn more about [Mattermost plugins](/integrations-guide/plugins).
|
||
|
||
#### Pre-Built Plugins
|
||
|
||
**Technical complexity:** [No-code](./faq#no-code)
|
||
|
||
Mattermost provides a set of [pre-built plugins](/integrations-guide/popular-integrations) that require no coding to install, configure, and use. These plugins are installed and managed entirely through the System Console, where you can enable, configure, and customize settings without any development work.
|
||
|
||
<img src="../images/prebuilt-integrations.png" width="800" alt="Pre-built plugins available for no-code integration" />
|
||
|
||
#### Custom-Built Plugins
|
||
|
||
**Technical complexity:** [Pro-code](./faq#pro-code)
|
||
|
||
[Building custom plugins](/integrations-guide/plugins#custom-built-plugins) are the most comprehensive way to add new features and customization to self-hosted Mattermost deployments. Custom plugins are ideal for customers wanting to change the behavior of the Mattermost server, desktop, and web apps without forking the core codebase to suit their organization’s needs.
|
||
|
||
Building a custom plugin is a **software development** task, using `Go` for the server-side functionality and optionally `TypeScript/React` for UI components.
|
||
|
||
### Webhooks
|
||
|
||
Learn more about [Mattermost webhooks](/integrations-guide/webhook-integrations).
|
||
|
||
#### Incoming Webhooks
|
||
|
||
**Technical complexity:** [No-code](./faq#no-code)
|
||
|
||
[Incoming webhooks](/integrations-guide/incoming-webhooks) allow external applications to post messages into Mattermost channels and direct messages. They are a simple way to receive notifications and data from other services in real-time and require only basic setup.
|
||
|
||
Additionally, Mattermost webhook payloads are [fully compatible](/integrations-guide/incoming-webhooks#slack-compatibility) with Slack’s webhook format to make migration easier.
|
||
|
||
#### Outgoing Webhooks
|
||
|
||
**Technical complexity:** [Low-code](./faq#low-code)
|
||
|
||
[Outgoing webhooks](/integrations-guide/outgoing-webhooks) allow Mattermost to send messages and trigger actions in external applications when specific keywords are typed in channels. They are a straightforward way to connect Mattermost conversations to other services and automate responses. Outgoing webhooks require no coding to configure in Mattermost. Some light coding is required to parse the request from the external service and format a JSON response payload.
|
||
|
||
### Slash Commands
|
||
|
||
Learn more about [Mattermost slash commands](/integrations-guide/slash-commands).
|
||
|
||
#### Built-In Slash Commands
|
||
|
||
**Technical complexity:** [No-code](./faq#no-code)
|
||
|
||
Out-of-the-box [built-in slash commands](/integrations-guide/built-in-slash-commands) enable command line interaction with users, channels, and conversations.
|
||
|
||
#### Custom Slash Commands
|
||
|
||
**Technical complexity:** [Low-code](./faq#low-code)
|
||
|
||
You can create [custom slash commands](/integrations-guide/slash-commands#custom-slash-commands) that run preconfigured commands that can return a response, such as plain text, rich message content, interactive buttons or forms, directly into a channel.
|
||
|
||
Mattermost's slash command format is Slack compatible, so you can easily migrate your commands from Slack.
|
||
|
||
### RESTful API
|
||
|
||
**Technical complexity:** [Pro-code](./faq#pro-code)
|
||
|
||
With [Mattermost's RESTful API](/integrations-guide/restful-api), you have full developer control for automation, bots, and integrations.
|
||
|
||
## Build and Automate Workflows
|
||
|
||
**Technical complexity:** [No-code](./faq#no-code)
|
||
|
||
In addition to direct tool integrations, Mattermost can be part of larger automated workflows across your integrated services. Automate multi-step processes across Mattermost and other systems, often with no coding required.
|
||
|
||
### No-code Automation Platforms
|
||
|
||
Platforms like n8n, Zapier, and Make provide powerful visual editors that support thousands of connected tools, with triggers and actions that integrate Mattermost to external services, enabling teams to build complex workflows without writing code. Admins migrating from tools like Slack Workflow Builder can recreate familiar automations in Mattermost using these platforms.
|
||
|
||
Learn more about additional [no-code automation options](/integrations-guide/no-code-automation) available in Mattermost.
|
||
|
||
### Mattermost Playbooks
|
||
|
||
[Mattermost Playbooks](/end-user-guide/workflow-automation) lets you define and execute repeatable processes without any coding. Playbooks are often used for incident response, onboarding checklists, or any workflow that involves multiple steps, owners, and notifications. Playbooks have integration points you can use to trigger actions, and they can work in conjunction with plugins, making them a powerful no-code automation tool for orchestrating both human and system actions.
|
||
|
||
Learn more about using [Playbooks](/end-user-guide/workflow-automation).
|
||
|
||
## Frequently Asked Questions
|
||
|
||
Have questions about coding levels, Slack compatibility, or setup options? Visit the [Integrations FAQ](/integrations-guide/faq).
|