Merge branch 'master' into esethna-air-gapped

Author: cwarnermm

source/administration-guide/onboard/migrate-from-slack.rst

@@ -29,4 +29,4 @@ Mattermost interoperability
 .. tip::
 
    - `Visit the Mattermost Marketplace <https://mattermost.com/marketplace/>`__ to find open source, community-supported integrations to common developer tools like `CircleCI <https://mattermost.com/marketplace/circleci/>`__, `Opsgenie <https://mattermost.com/marketplace/opsgenie/>`__, `PagerDuty Notifier <https://mattermost.com/marketplace/pagerduty/>`__; productivity tools like `Autolink <https://mattermost.com/marketplace/autolink-plugin/>`__, `ToDo <https://mattermost.com/marketplace/todo/>`__, and `WelcomeBot <https://mattermost.com/marketplace/welcomebot-plugin/>`__; as well as social tools like `Memes <https://mattermost.com/marketplace/memes-plugin/>`__ and `GIFs <https://mattermost.com/marketplace/giphy-plugin/>`__ that are freely available for use and customization.
-   - Looking for a way to get notifications of new Mattermost Marketplace integrations in your Mattermost channels? See the :ref:`integrations FAQ <integrations-guide/integrations-guide-index:frequently asked questions>` documentation for details.
+   - Looking for a way to get notifications of new Mattermost Marketplace integrations in your Mattermost channels? See the :doc:`integrations FAQ </integrations-guide/faq>` documentation for details.

source/end-user-guide/collaborate/extend-mattermost-with-integrations.rst

@@ -7,8 +7,6 @@ Mattermost keyboard shortcuts
   :titlesonly:
 
   Keyboard accessibility </end-user-guide/collaborate/keyboard-accessibility>
-  Run slash commands </integrations-guide/run-slash-commands>
-  Built-in-slash-commands </integrations-guide/built-in-slash-commands>
 
 .. include:: ../../_static/badges/allplans-cloud-selfhosted.rst
   :start-after: :nosearch:

source/end-user-guide/collaborate/keyboard-shortcuts.rst

@@ -6,6 +6,10 @@ Workflow Automation
 
 Mattermost Playbooks provides structure, monitoring and automation for repeatable, team-based processes integrated with the Mattermost platform. Playbooks are :doc:`configurable checklists </end-user-guide/workflow-automation/work-with-tasks>` for teams to achieve :doc:`specific and predictable outcomes </end-user-guide/workflow-automation/metrics-and-goals>`, such as incident response, software release management, and logistical operations.
 
+For instance, a playbook can be configured to automatically open a dedicated channel for an incident, send template messages or task checklists to that channel, update subscribers on status changes, and so on, all through configuration.
+
+While Playbooks primarily focus on coordinating people and tasks, they also have integration points. You can trigger a playbook run via an incoming webhook (allowing an external tool to trigger a playbook run). Within a playbook, you can define steps that execute webhooks or call external APIs. Additionally, Playbooks can work in conjunction with plugins, keeping the entire workflow visible in Mattermost, and reducing the need to switch between apps during critical processes.
+
 .. toctree::
    :maxdepth: 1
    :hidden:

source/end-user-guide/workflow-automation.rst

@@ -1,14 +1,9 @@
-Use built-in slash commands
+Built-In Slash Commands
 ============================
 
 .. include:: ../_static/badges/allplans-cloud-selfhosted.rst
   :start-after: :nosearch:
 
-You can interact with Mattermost users, channels, conversations, and more using `built-in slash commands <#slash-commands>`_, or interact with the data model programmatically using `API endpoints <https://api.mattermost.com/>`__. Responses are posted as the user who invoked the command, with possible username/icon overrides.
-
-Slash commands
---------------
-
 The following built-in slash comamnds are available in your Mattermost :doc:`workspace </end-user-guide/end-user-guide-index>`. 
 
 .. tip::

source/integrations-guide/built-in-slash-commands.rst

@@ -0,0 +1,91 @@
+Frequently Asked Questions
+===========================
+
+What is meant by no-code, low-code, and pro-code?
+-------------------------------------------------
+
+.. _no-code:
+
+No-code
+~~~~~~~~
+
+Integration or automation can be achieved without writing any code. All configuration is done via user-friendly interfaces or by installing pre-made components. This is ideal for non-technical users or admins. 
+
+For example, installing a plugin from the marketplace or using a drag-and-drop automation tool would be considered no-code. The heavy lifting is pre-built and you just need to configure it.
+
+.. _low-code:
+
+Low-code
+~~~~~~~~
+
+Minimal coding or scripting is needed to implement the integration. Low-code solutions might require writing a few lines of script or simple configuration in code-like logic, but not building a full software application. 
+
+In Mattermost’s context, something like setting up a webhook with a small custom script, or tweaking an automation template would be considered low-code. It typically assumes some technical knowledge, but far less than full-scale development. Utilizing templates or online AI tooling can likely meet the need for most low-code integration requirements.
+
+.. _pro-code:
+
+Pro-code
+~~~~~~~~
+
+These kinds of integrations require a professional software developer to write code and sometimes build underlying infrastructure. These integrations offer maximum flexibility at the cost of technical complexity, for example building a custom Mattermost plugin or writing a complex bot program using the Mattermost API in a custom application. 
+
+Pro-code integrations are essentially software projects – you’ll use developer tools, work with source code, and follow software development practices to build and maintain them.
+
+What does Slack-compatible mean?
+--------------------------------
+
+Slack compatible means that Mattermost accepts integrations that have a payload in the same format as Slack's legacy "Message Attachment" payload. If you have a Slack integration, you should be able to set it up in Mattermost without changing the format of the message being sent over.   
+
+What if I have a webhook from somewhere other than Slack?
+---------------------------------------------------------
+
+If you have an integration that outputs a payload in a different format, you need an intermediary service to act as a translation layer to change it to the format Mattermost uses. These intermediary services could be no-code or low-code integrations with n8n, Zapier, or Make, but they could also be pro-code integrations leveraging something like AWS Lambda or other hosted services. 
+
+There’s currently no general standard for webhook communication between services, so translating your webhooks is necessary otherwise Mattermost won't understand the data you're sending.
+
+What are attachments?
+----------------------
+
+When "attachments" are mentioned in Mattermost integrations documentation, it refers to Slack's message attachments functionality. These "attachments" can be optionally added as an array in the data sent by an integration, and are used to customize the formatting of the message.
+
+Mattermost doesn't currently support the ability to attach files to a post made via webhook. You can use the API to attach files to a message if needed. 
+
+Where can I find existing integrations?
+---------------------------------------
+
+Visit the `Mattermost Marketplace <https://mattermost.com/marketplace>`__ to access open source integrations to common tools like Jira, Jenkins, and GitLab, along with interactive bot applications, and other communication tools that are freely available for use and customization. 
+
+Alternatively, within Mattermost, when logged in as an Administrator, you can click on the "Marketplace" option in the main menu and easily install plugins or apps from there. 
+
+Where should I install my integrations?
+----------------------------------------
+
+For self-hosted deployments in small setups, you might host integrations on the same server on which Mattermost is installed. For larger deployments, you can set up a separate server for integrations, or add them to the server on which the external application is hosted. 
+
+For example, if you're self-hosting a Jira server you could deploy a Jira integration on the Jira server itself. When self-hosting restrictions are less strict, AWS, Heroku, and other public cloud options could also be used.
+
+Where can I get more information about integrations?
+-----------------------------------------------------
+
+Join our `Developers channel <https://community.mattermost.com/core/channels/developers>`_  on the Mattermost Community server  for technical discussions, and visit our `Integrations channel <https://community.mattermost.com/core/channels/integrations>`_ for all integrations and plugins discussions.
+
+Can I use webhooks to be notified when new integrations are available on the Mattermost Marketplace?
+-----------------------------------------------------------------------------------------------------
+
+Yes! A `bash script <https://gist.github.com/mickmister/543a49584146af18ba5e5f82dd86ea93>`_ is available that checks for new integrations in the Mattermost Marketplace, and triggers a post through a Mattermost `incoming webhook <https://developers.mattermost.com/integrate/webhooks/incoming/>`_ request. The script downloads the latest listing, compares it with a locally stored version of the listing, and, if a new plugin is identified, a notification is pushed to a Mattermost channel.
+
+Can I use Mattermost to add messaging functionality to my proprietary SaaS service?
+------------------------------------------------------------------------------------
+
+Mattermost is an open source, self-hosted alternative to proprietary SaaS services that lock in the data of users and customers.
+
+While you're welcome to use the Mattermost source code under its open source license, Mattermost, Inc. does not offer support or technical advice for proprietary SaaS projects that result in customers potentially being paywalled from their data should they stop paying SaaS fees.
+
+To learn more about why we strongly believe that users and customers should always have access to their data, please read `why we created Mattermost <https://mattermost.com/about-us/>`_.
+
+Can I customize the source code?
+--------------------------------
+
+Yes. As an open source project, we support your ability to modify the source code for the server or web app to make changes and customizations to meet your specific needs.
+
+Learn about `forking our open source repositories <https://developers.mattermost.com/integrate/other-integrations/customization/>`_ and `customizing the Mattermost source code <https://developers.mattermost.com/integrate/customization/customization/>`_ for your specific operational needs.

source/integrations-guide/faq.rst

@@ -1,11 +1,28 @@
 Incoming Webhooks
 =================
 
-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.
+**Technical complexity:** :ref:`No-code <no-code>`
 
-You can create an incoming webhook in Mattermost, which generates a unique URL. External systems send HTTP POST requests to that URL with a JSON payload containing the message text and optional formatting (attachments, images, links, etc.). Messages are created under the webhook’s configured user (typically the creator). Username/icon can be overridden in the payload.
+Send or receive real-time data from external tools. Webhooks require minimal coding and are easy to set up with virtually any tool or platform because they use lightweight HTTP POST requests with JSON payloads.
 
-For example, your monitoring tool detects high CPU usage and sends an alert message directly into your **#devops-alerts** channel. All webhook posts will display a ``BOT`` indicator next to the username in Mattermost clients to help prevent against phishing attacks.
+Using incoming webhooks in Mattermost requires only basic setup. You generate a webhook URL using the Mattermost interface, then point another service to send data to that address. No coding is required if your external service triggering the events is able to send data via webhooks or HTTP POST requests, which most modern applications and platforms support. Setting this up usually involves pasting the Mattermost webhook URL into the service’s settings and selecting what type of events you want it to send. 
+
+Example Use Cases
+-----------------
+
+Here are some example use cases for incoming webhooks in Mattermost:
+
+**Monitoring alerts**
+
+Send real-time alerts from monitoring systems (such as Prometheus or Datadog) into a dedicated Mattermost channel so your team is immediately notified about system issues or downtime.
+
+**Build and deployment notifications**
+
+Post automated updates from CI/CD pipelines (such as Jenkins or GitLab CI) to a channel, keeping developers informed of build status, test results, and deployment progress.
+
+**Customer support updates**
+
+Forward new support ticket notifications from systems like Zendesk or ServiceNow into a support channel, ensuring the team can respond quickly to incoming requests.
 
 Create
 ------
@@ -49,8 +66,8 @@ A successful request will receive an HTTP 200 response with `ok` in the response
 
 For compatibility with Slack incoming webhooks, if no ``Content-Type`` header is set, the request body must be prefixed with ``payload=``.
 
-Post examples
---------------
+Post Examples
+~~~~~~~~~~~~~
 
 Here are some examples of simple messages posted using incoming webhooks: