Fixes #1071 - Add text extraction handling and rework email filters

Author: ralf401

ai/ai-agents.rst

@@ -93,6 +93,8 @@ ticket and the content of the last article. You can choose to use all priorities
 or limit them to specific ones. In case you limit the priorities, you can also
 provide a description for each priority the AI agent can choose from.
 
+.. _text-extractor-ai-agent:
+
 Ticket Text Extractor
 ^^^^^^^^^^^^^^^^^^^^^
 

channels/email/filters.rst

@@ -1,6 +1,9 @@
 Filters
 =======
 
+Introduction
+------------
+
 .. toctree::
    :hidden:
 
@@ -10,57 +13,168 @@ Filters
    :alt: Account settings page
    :align: center
 
-Postmaster filters allow you to match email headers
-(e.g. ``From``, ``To``, ``Subject``, ``X-Spam-Flag`` etc.) and execute a set of
-actions whenever Zammad's email parser encounters a matching email. The actions
-will be applied to the ticket that is created or updated by this email.
+With filters in email-based channels ("postmaster filters"), you can
+adjust Zammad's behavior, automate actions and extract information when an email
+is received. The filters are based on conditions and differentiate between
+actions for the ticket creation and the ticket update. The available options
+differ from those available in other automation types (triggers and scheduler
+jobs). So if your use case isn't covered by filters, consider using triggers or
+scheduler jobs instead.
+
+Zammad includes some built-in system filters by default which you can't see or
+modify. Check the system filters section below for more information.
+
+Usage
+-----
+
+To create a new filter, click on the **New** button. This opens a dialog where
+you can configure it. To modify an existing filter, just click on its row in the
+table, which opens the same dialog.
+
+In addition to that, you can clone or delete a filter by clicking on the ``⠇``
+to open the action menu and select the corresponding option. The cloning can be
+useful if you have a complex configuration and don't want to start from scratch.
+Instead of deleting a filter, consider to setting it to inactive so you can
+easily activate it again later.
+
+In addition to some meta information, the configuration basically consists of
+two parts: the condition to define which emails are affected
+(**Match all of the following**) and the action to define the changes for
+matching emails (**Perform actions**).
+
+Name
+   Name of the filter. This is also shown in the ticket history if the filter
+   has been applied to a ticket.
+
+Match all of the following
+   Define which emails should be affected by the filter based on conditions.
+   You can use various email attribute checks such as sender, subject, or custom
+   headers. They all have to match for the action to get applied. The conditions
+   work similarly to other places in Zammad. Have a look at
+   the :doc:`object conditions page </misc/object-conditions/basics>`, where
+   you can find details about how the operators work.
+
+   It is even possible to extract information from incoming emails and to
+   use it in actions. An example for this could be to extract an order number
+   from the subject and write it into a custom object attribute. This is done
+   via regular expressions and their capture groups. To extract a string,
+   use *matches regex* as operator and add a capture group by using parentheses
+   for the part of the string you want to extract. Optionally, you can name
+   the capture group by adding ``?<name>`` at the beginning of the capture
+   group, e.g. ``.*order.*\D(?<order_number>\d+).*``.
+
+   .. hint:: Another way of extracting text is to use the
+      :ref:`text extractor AI agent <text-extractor-ai-agent>`.
+
+Perform actions
+   Define which actions should be performed on the matching emails. You can
+   differentiate between actions for the ticket creation and the ticket update.
+   Additionally, you have some related options available like changing the
+   visibility of the article.
+
+   If you extracted information in a condition, you can use it in the actions
+   and write it to any available and fitting attribute which is capable of
+   storing the extracted string (e.g. title or a custom object attribute).
+   To insert the extracted string, use ``#{regex.name}`` where ``name`` is the
+   name of the capture group you defined in the condition, e.g.
+   ``#{regex.order_number}``. For unnamed capture groups, use the number of the
+   capture group, e.g. ``#{regex.1}`` for the first capture group. Make sure to
+   always use the ``regex`` namespace.
+
+Note
+   Add a note about the filter. This note is only for internal use and visible
+   for other admins.
+
+Active
+   Set the filter to active or inactive. Only active filters are applied to
+   incoming emails.
+
+Examples
+--------
+
+Group Assignment Based on Sender Domain
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Example
+   Automatically move emails from ``@amazon.com`` to the "Purchasing" group.
+
+Condition
+   **From:** *matches regex:* ``(\.|@)amazon\.com``
+
+Action
+   **Group:** Purchasing
+
+Organization-Based Ticket Assignment
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Example
+   Automatically dispatch tickets to responsible staff based on the organization
+   name.
+
+Condition
+   **Organization:** *starts with one of:* ``A`` ``B`` ``C``
+
+Action
+   **Owner:** Emily Adams
+
+VIP Customer Handling
+^^^^^^^^^^^^^^^^^^^^^
+
+Example
+   Automatically increase the priority of tickets from a VIP customer.
+
+Condition
+   **From:** *contains:* ``ourvipcustomer@example.com``
+
+Action
+   **Priority:** 3 high
+
+Spam Handling
+^^^^^^^^^^^^^
 
-Zammad comes with system filters as well. While you can't change them, it might
-be useful for you what they actually do. Learn more on
-:doc:`filters/system-filters`.
+Example
+   Automatically tag and close spam tickets that have been marked as spam by an
+   external spam filter (e.g. SpamAssassin).
 
-Different attributes of a filter can be combined with each other. Likewise,
-the following operators can be combined. The supported matches are:
+Condition
+   **X-Spam-Flag:** *contains:* ``YES``
 
-   * *contains*
-   * *contains not*
-   * *is any of*
-   * *is none of*
-   * *starts with one of*
-   * *ends with one of*
-   * *matches regex*
-   * *does not match regex*
+Action
+   **Tag:** add: ``spam``
+   **State:** closed
 
-You can also have a look at the
-:doc:`object conditions </misc/object-conditions/basics>` for text fields, where
-you can find a description of how the operators are working.
+Extract Information from Subject
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-.. note::
+Example
+   Automatically extract an invoice number from the email subject (with an
+   unnamed capture group) and write it to the custom object attribute
+   "Invoice number".
 
-   Please note that the ticket actions are separated in "Ticket creation" and
-   "Ticket update". Make sure to use the appropriate variant for your scenario.
+Condition
+   **Subject:** *matches regex:* ``.*[Ii]nvoice.*\D(\d+).*``
 
-Here are some examples of what is possible with filters:
+Action
+   **Invoice number:** ``#{regex.1}``
 
-Automatically dispatch tickets into certain groups:
-  For example, tickets from ``amazon.com`` could automatically be dispatched to
-  the Purchasing group.
+Extract Information from Email Body
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-  | From: *matches regex:* ``(\.|@)amazon\.com``
-  | Group: Purchasing
+Example
+   Automatically extract an order number from the email body (with a
+   named capture group) and write it to the custom object attribute
+   "Order number".
 
-Automatically dispatch tickets to responsible staff based on organization name:
-  | Organization: *starts with one of:* ``A`` ``B`` ``C``
-  | Owner: Emily Adams
+Condition
+   **Body:** *matches regex:* ``.*[Oo]rder.*\D(?<order_number>\d+).*``
 
-Automatically increase the priority of tickets from a VIP customer:
-  | From: *contains:* ``ourvipcustomer@example.com``
-  | Priority: 3 high
+Action
+   **Order number:** ``#{regex.order_number}``
 
-Automatically tag and close spam tickets that have been marked as spam by an external spam filter (e.g. SpamAssassin):
-  | X-Spam-Flag: *contains:* ``YES``
-  | Tag: add: ``spam``
-  | State: closed
+System Filters
+--------------
 
-If a filter is no longer needed, it can either be temporarily set inactive or
-deleted directly.
+Zammad comes with some built-in system filters by default. You can't see them in
+the UI. The intention is to tweak the behavior of Zammad for emails from common
+systems which have some kind of special formatting. Have a look at our separate
+subpage about :doc:`filters/system-filters` where you can find more details.