> 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/integrations/inbound-integrations/postman-monitors.md).

# Postman Monitors Integration

Connect ilert and Postman's Monitor to receive alerts via SMS, push, and voice notifications

Postman is a platform for API development, allowing developers to design, test, document, and monitor APIs. It offers a user-friendly interface and a comprehensive suite of tools to simplify working with APIs, making creating, sharing, and troubleshooting API requests easier. Postman's monitor feature enables developers to schedule and automate API tests. By integrating ilert with Postman, users can automatically send alerts from Postman to their incident management platform, ensuring the prompt delivery of alerts. This guide will walk you through setting up a connection between ilert and Postman.

## In ilert: Create a Postman Monitors alert source <a href="#create-alarm-source" id="create-alarm-source"></a>

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Postman Monitors**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.

   <figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgit-blob-8a281bf3931f5a1a531951ce97984d50989dd875%2Falert-source-escalation-step.png?alt=media" alt="The escalation step of the ilert alert source wizard, headed Who should be notified about alerts, with an escalation policy selected and a preview of its escalation rules below."><figcaption><p>Pick an existing escalation policy, or generate a basic one without leaving the wizard.</p></figcaption></figure>
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2F4CnhznTeLcACWchOSfTk%2Fil-1.png?alt=media&amp;token=37cc8789-1028-4d57-90e9-a0f6131b81f8" alt="" width="563"><figcaption></figcaption></figure>

## In Postman: Create a Webhook

1. On the Home page, click **Integrations**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Fgk1ufvcHwG1ybqot7OlG%2F1.png?alt=media&amp;token=fd8c6022-1d59-4007-a2f9-08941b8ff4e1" alt="" width="375"><figcaption></figcaption></figure>

2. Now click on **Browse All Integrations**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FPuW81WG4PPlXkjRyXvUb%2F2.png?alt=media&amp;token=78a54bdd-1fd5-4e57-8db2-a2606483e94f" alt="" width="563"><figcaption></figcaption></figure>

3. In the search field, enter webhooks and click the **Webhooks** tile.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FXObuEo8EGf74S11YQJ0S%2F3.png?alt=media&amp;token=eea729ed-dc49-4d2b-8850-bdad9f9a0cd2" alt="" width="563"><figcaption></figcaption></figure>

4. Now in the **Post monitoring results** section, click on **Add integration**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FrovC9wmcvCyHeKjouU6m%2F4.png?alt=media&amp;token=65f5aa57-e9aa-45e8-8d0d-b3e5102ca0b7" alt="" width="563"><figcaption></figcaption></figure>

5. Enter a **Nickname**, choose a desired **workspace** and **Monitor**.
6. Now enter the alert source url created in ilert into the **Webhook URL** field and select **Notify for 3 failures and then first success**.
7. Click on **Add Integration** to finish the setup.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FMBo7aelftRGoOf9ckkP3%2F5-2.png?alt=media&amp;token=0de0e0a7-1999-4c1f-a894-fa0a92cd3022" alt="" width="563"><figcaption></figcaption></figure>

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

**Will alerts in ilert be resolved automatically?**

Yes, as soon as the state of a Monitor in Postman is Healthy again, the alert in ilert will be fixed.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.ilert.com/integrations/inbound-integrations/postman-monitors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
