> For the complete documentation index, see [llms.txt](https://docs.birdie.so/birdie-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.birdie.so/birdie-docs/helpdesk/zendesk/flows/zendesk-macros.md).

# Zendesk Macros

This is how it looks like:

<figure><img src="/files/TQLgkx6PoACDNzBIMdKJ" alt=""><figcaption></figcaption></figure>

To create a macro that includes a Birdie Link, watch the video and follow these steps:

{% embed url="<https://youtu.be/PVth0F9lUPQ>" %}
How to add a Birdie link to your Zendesk macros
{% endembed %}

1. Create a new macro on Admin Center > Workspace > Macro > Create a Macro
2. Click on "*Add Action*" and select "*Comment/description*"
3. Go to your Birdie settings and copy "*<mark style="color:green;">Your Birdie link to paste in Triggers, Automations and Macros</mark>*"
4. Write the text you want in your Macro and paste your Birdie link into it
5. Save it. You're all set!

<details>

<summary>Using the Macro Suite app or HTML scenarios?</summary>

If you're using the [Macro Suite app](https://www.zendesk.com/marketplace/apps/support/213512/macro-suite/?queryID=e2b4fc13c27128af2f6e06b71f1ccc76) or working with URL-encoded HTML scenarios, Zendesk may break the Birdie link if it includes raw placeholders like `{{ticket.id}}`.

To prevent this, **URL-encode the link** so that special characters like `{` and `}` are safely interpreted.

For example, instead of:

```
https://your-subdomain.birdie.so/recorder?zar={{ticket.id}}&zce={{ticket.requester.email}}&via={{ticket.via}}
```

Use the URL-encoded version:

```
https://your-subdomain.birdie.so/recorder?zar=%7B%7Bticket.id%7D%7D&zce=%7B%7Bticket.requester.email%7D%7D&via=%7B%7Bticket.via%7D%7D
```

This ensures your macro works reliably in all scenarios.

</details>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.birdie.so/birdie-docs/helpdesk/zendesk/flows/zendesk-macros.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.