> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/project-manager/workflows/actions/notification.md).

# Notification

Sends an email from the workflow to the given recipient list.

<figure><img src="https://2655769465-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjVABEcCgwItwY4IEAD%2Fuploads%2FMidxI3CzA3guH9iYfNok%2FNotification_Case1_Plain%20Text.png?alt=media&amp;token=f84bb39b-2261-449a-aef9-c7527fef847c" alt=""><figcaption></figcaption></figure>

### Options

* ***Send To*** - Recipient emails in comma-separated values
* ***Subject*** - Subject line of the email. Keep it short.
* ***Character Set*** - To be interpreted in the emails. Options: `US-ASCII, ISO-8859-1, UTF-8`
* ***Content Transfer Encoding*** - Mail encoding method. Options: `Quoted Printable, Base64, 7Bit, 8Bit, Binary`
* ***Message Type*** - `Plain Text` for sending string messages. `HTML` for sending mail as per a template
* ***Dynamic Data*** - Only for the `HTML` message type to pass the dynamic data. Provide in JSON format.
* ***Message*** - Email Content or Body.

### Examples

**Plain Email**

* Subject: `Plain Text Mail Demo`
* Character Set: `US-ASCII` (Default Value)
* Content Transfer Encoding: `7 bit` (Default Value)
* Message Type: `Plain Text`
* Message:&#x20;

  <pre><code><strong>Dear Sir,
  </strong>This is to inform you that we received your ticket.
  </code></pre>

![Example 1](https://2655769465-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjVABEcCgwItwY4IEAD%2Fuploads%2FDLMcIMDBbfb6g7iEtf3X%2Fex1.png?alt=media\&token=9bdbadd5-8f4a-45c8-b740-e3f695030864)

**HTML Email without dynamic content**

* Subject: `HTML Static Mail Demo`
* Character Set: `US-ASCII` (Default Value)
* Content Transfer Encoding: `7 bit` (Default Value)
* Message Type: `HTML`
* Message:&#x20;

  ```html
  <html>
     <head>
        <h1> Line1 </h1>
     </head>
     <body>
        <i>This is a mail to communicate that we are working on your ticket </i>
     </body>
  </html>
  ```

![Example 2](https://2655769465-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjVABEcCgwItwY4IEAD%2Fuploads%2FvdlMgaf9JyMXuwqvChJO%2Fex2.png?alt=media\&token=f765c476-01f2-456f-8502-0afa42aeec43)

**HTML Email with dynamic content**

* Subject: `Dynamic HTML Mail Demo`
* Character Set: `US-ASCII` (Default Value)
* Content Transfer Encoding: `7 bit` (Default Value)
* Message Type: `HTML`
* Dynamic Data&#x20;

  ```json
  {
      "keys": ["Name","Age","Company"],
      "records": [
          {"name": "Alex", "age": 25, "company": "DCKAP"},
          {"name": "David", "age": 28, "company": "DCKAP"}
      ]
  }
  ```
* Message:&#x20;

  ```html
  <!DOCTYPE html> 
  <html>
     <head>
        <style> 
           table, th, td { border: 1px solid black; } 
        </style>
     </head>
     <body>
        <table>
           <tr>
              {% for key in keys %}
              <td>{{key}}</td>
              {% endfor %} 
           </tr>
           <tr>
                 {% for dict_item in records %}
                        {% for key, value in dict_item.items() %} 
                                <td>{{value}}</td>
                        {% endfor %}
                        <tr></tr>
                 {% endfor %} 
           </tr> 
        </table>
     </body>
  </html>
  ```

![Example 3](https://2655769465-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjVABEcCgwItwY4IEAD%2Fuploads%2FXqEDcvrJqRLlifXf2sB9%2Fex3.png?alt=media\&token=0ca5f356-28a4-4dce-8f97-a155d8ba9c8d)

{% hint style="warning" %}
Base-64 HTML Combination and occasionally Base-64 plain text combinations don't work as expected. This will be addressed in the upcoming releases.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dckapintegrator.com/project-manager/workflows/actions/notification.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.