> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/outbound-integrations/zapier.md).
# Zapier Outbound Integration
Use ilert as the trigger in Zapier and perform any action in Zapier for new or updated alerts in ilert.
## In Zapier: Create a Zap
1. Go to Zapier and click on **Make a Zap**
2. On the next page, search for **iLert** trigger source and choose it:
3. In the section **Trigger Event** choose **New or Updated Alert** and click on the **Continue** button
4. On the next slide, choose your ilert account. Then click on the **Continue** button.
5. On the next slide, choose **an alert source** and **trigger types** e.g. Alert Created. Then click on the **Continue** button.
{% hint style="warning" %}
NOTE: you can't use an Zapier alert source here, as it will lead to an infinite loop
{% endhint %}
6. On the next slide, click on the **Test Trigger** button to see example data. Then click on the **Continue** button.
7. Now you can **add any action** available in Zapier, e.g. Jira to create a ticket on your Jira board
## FAQ
**Why the Zapier connector is in my alert source?**
Every time you create a Zap with an ilert trigger, the Zapier connector in ilert is created automatically for the alert source you selected in the trigger.
## Related articles
{% content-ref url="/pages/-MKotWYhT9DEBZjh8vMt" %}
[Zapier Inbound Integration](/~/changes/vPSzQFfkdJCVWGT5AL1m/inbound-integrations/zapier.md)
{% endcontent-ref %}
---
# 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.ilert.com/~/changes/vPSzQFfkdJCVWGT5AL1m/outbound-integrations/zapier.md?ask=&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.