> 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/particle.md).

# Particle Integration

Create alerts in ilert from Particle alerts.

[Particle.io](https://www.particle.io) is a platform that provides everything necessary for organizations to develop, deploy, and manage their Internet of Things (IoT) products. It serves as a comprehensive ecosystem for connected device development with robust tools, APIs, and hardware kits. With Particle.io, you can build IoT devices at scale, delivering connectivity, device management, and security features out-of-the-box.

ilert's integration for Particle enables users to receive alerts from their devices via SMS, push, voice, and messenger notifications. It helps to connect Particle devices with other services and tools in the tech stack and speed up incident response.

## In ilert: Create a Particle alert source

1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Particle**, 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.

## In Particle: Create a Webhook

1. In the sidebar click on **Integrations**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FZUAV0HH18wUflfJirhOK%2FParticle-1.png?alt=media&amp;token=5b7f95a8-a8de-4157-8e16-d586ab8c10e0" alt="" width="563"><figcaption></figcaption></figure>

2. Now click on **ADD NEW INTEGRATION**.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FM8S29bDkhTCmNXaHgFtA%2FParticle-2.png?alt=media&amp;token=207fef25-554b-44e0-839b-9856e8bd078e" alt="" width="563"><figcaption></figcaption></figure>

3. Click on **Webhook**, to create a new webhook integration.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FeCJvb9CZdfE78rtQ3Qvy%2FParticle-3.png?alt=media&amp;token=675bdb62-61b3-4acd-8df6-fe62ebfd5dc0" alt="" width="563"><figcaption></figcaption></figure>

4. Enter a **Name**, an **Event Name**(ALERT or RESOLVE) and the [previous](#in-ilert-create-a-particle-alert-source) generated ilert webhook URL into the **URL** field.
5. Change the **Request Type** to **POST** and open the **Advanced Settings**.

{% tabs %}
{% tab title="ALERT" %}

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FnbtDRLTAmZZfXSa5NSJm%2FParticle-5.png?alt=media&amp;token=e744ccfa-5b95-43ea-9b26-2195a9e06f4e" alt="" width="563"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="RESOLVE" %}

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2Ft2Zwt7Zc0YDogbDM84xj%2FParticle-7.png?alt=media&amp;token=4507fe40-f649-494c-9a15-231d69e1a82f" alt="" width="563"><figcaption></figcaption></figure>
{% endtab %}
{% endtabs %}

6. Select **Default**. (for custom json data follow this [step](#in-particle-custom-json-data))

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2F93gLfYIeY3Mm8vZuZ6zP%2FParticle-10.png?alt=media&amp;token=d7c29694-d9c3-496e-ac49-d9fa5393fc21" alt="" width="563"><figcaption></figcaption></figure>

7. Click on **SAVE**.
8. Optional: Click on **TEST** to test the integration.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FHPVOuu5PzixvQkZK9QCo%2FParticle-9.png?alt=media&amp;token=6a2a12d4-2098-429a-a834-c70732423804" alt="" width="563"><figcaption></figcaption></figure>

## Custom Webhooks

### In Particle: Custom json data

1. Under Advanced Settings choose **Custom** for **JSON DATA**.
2. Create a template using the Particle [documentation](https://docs.particle.io/reference/cloud-apis/webhooks/). (it is also possible to add own customized values)

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FF8z5YmylBHGjIYVrODRy%2FParticle-template-1.png?alt=media&amp;token=677c0cf3-7f75-4583-bbf9-e23eea5e8d83" alt="" width="563"><figcaption></figcaption></figure>

### In ilert: Create a custom template

1. Go to the alert source edit view.
2. Under **Alert template** enable **Alert summary** and **Alert details**.
3. For a detailed guide on how to use our alert templating click [here](/alerting/configure-alerting/alert-sources.md#alert-template).
4. Use the payload keys created in this [step](#in-particle-custom-json-data) to create the alert template.

<figure><img src="https://3394882078-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M76ygPnS4HUcFSX8ulm%2Fuploads%2FSY0WKy55ZLh0Mbkih7Ta%2FParticle-template-2.png?alt=media&amp;token=c39aaf6d-188d-469c-8ae5-b65e3097d8b6" alt=""><figcaption></figcaption></figure>

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

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

Yes, as soon as a webhook integration is sending an RESOLVE event, the alert in ilert will be fixed. To create RESOLVE events, follow the [guide](#in-particle-create-a-webhook) and use RESOLVE as Event Name.


---

# 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/particle.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.
