# Zammad Outbound Integration

The [Zammad](https://zammad.com/en) integration empowers ilert to generate support tickets in Zammad automatically. As alerts occur, they are instantly reflected in your support queue, keeping agents informed and aligned with real-time monitoring events.

{% hint style="warning" %}
To set up this integration, you must have admin rights in ilert.
{% endhint %}

## In Zammad: Create an API key <a href="#in-topdesk" id="in-topdesk"></a>

1. Optional: create a dedicated ilert user in Zammad. This has the advantage that you can distinguish the Zammad tickets created by ilert.
2. Go to **Profile**, then to **Token Access** and click on **Create**

![](/files/-MSwTfNxrLAx_RqXgL5H)

3. In the **Name** section, enter a name eg. ilert

![](/files/-MSwU9DJwl8BN6ndYD_t)

4. In the **Ticket** section, choose **Agent**

![](/files/-MSwUEfHnRpJiNaLkpP8)

5. Click on **Create**

{% hint style="warning" %}
An agent token has a group scope

An agent token has a group scope so if you want to use a group that the current user is not a member of, you need to create a token with the admin scope for all groups.
{% endhint %}

6. The modal window will open, copy the generated access token

![](/files/-MSwUbejdJ06JLKc6tLX)

## In ilert: Create a Zammad Connector and link to the alert source <a href="#in-ilert" id="in-ilert"></a>

1. Click on the gear icon and then on the **Connectors** button

![](/files/-Mkn3b39jQN6o8j4nVNJ)

2. Click on **Add Connector**

![](/files/-Ma8BCbPt5h67tGsMFBF)

3. Select **Zammad** as **type** and fill in all fields. Enter a name, the URL of your Zammad server and the access token that you have created in the previous step.

![](/files/-MSwVPv4XvzHp6V_tsi_)

4. Go to the alert sources tab and open the alert source whose alerts you want to publish in Zammad. Click on **Alert actions** and then on **Create alert action**.

![](/files/-Mkn3ka7m65J5wG7_1PK)

5. Select **Zammad** as the **type**; **futhermore** select the connector created in step 3, fill in all fields.

In the **Email** field enter the existing customer email of Zammad.

![](/files/-Ma86UG5M4-8xmZ1u_L9)

6. Finished! You can now test the connection by clicking on the button **Test this connection**.
7. A test ticket will be created in Zammad.

![](/files/-Ma86gIaGDXQTL13RyHj)

## FAQ <a href="#faq" id="faq"></a>

**Are updates to an alert added to the Zammad Ticket?**

Yes, the state of the ilert Alert is reflected in the brief description of the Zammad ticket eg. *\[RESOLVED] Host compute.infra is DOWN.*

**Can I choose which updates are to be published to a Zammad Ticket?**

Currently not. If you wish to, we look forward to your feedback via chat or e-mail

**Can I use custom group for the Zammad tickets?**

Yes, you need to create an agent token and include the user in the group or create an admin token with the group scope.

**Can I use multiple Zammad groups?**

Yes, just create an alert action for each Zammad group.

## Related articles

{% content-ref url="/pages/-MSwMZuUVnrHe0z1XREh" %}
[Zammad Inbound Integration](/integrations/inbound-integrations/zammad.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ilert.com/integrations/outbound-integrations/zammad.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
