> 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/ixon.md).
# IXON Cloud Integration
IXON Cloud is an Industrial IoT platform for the advanced machine manufacturer with a tailor-made cloud platform for optimal remote service and applicable data insights.
This integration uses IXON's Cloud Notify to dispatch real-time notifiations from your machine(s) to ilert. That way, you can leverage ilert's alerting, scheduling and escalation capabiltites to send critical alerts from your machines to the right personnel and take immediate action.
### In ilert: Create an IXON Cloud alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **IXON Cloud**, 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**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
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.
### Advanced routing configuration
By default ilert will route the alerts of your IXON alert source to the configured escalation policy.\
However if you need a more flexible routing for your IXON use cases you may use our advanced routing options.
You may choose the fields **user id, system label or company id** as dynamic routing fields.\
ilert will then extract the given value e.g. user id from the IXON event and search for an escalation policy that has a matching routing key.
Navigate to the escalation policy that you wish to route to and set its routing key to the IXON value:
Note that if no match for the routing key is found, ilert will fall back to using the configured escalation policy.
### In IXON Cloud
#### Create ilert webhook
1\. Navigate and login to Ixon Cloud Portal at
2\. Click on the  icon on the top right of the dashboard to navigate to **Messages**
3\. Click on the  icon on the top right of the dashboard and select **Configure webhooks**
4\. Add the name of the webhook and the webhook url of the ilert alert source from above.
#### Setup alarm and alarm trigger
Now that the ilert webhook is configured, we're going to setup an alarm and alarm trigger to test the integration. Refer to this [support article](https://support.ixon.cloud/hc/en-us/articles/360016805380) from the IXON documentation for information on how to setup alarms.
1\. Navigate to [**Fleet Manager**](https://portal.ixon.cloud/fleet-manager) \*\*\*\* by clicking on the  icon on the top right and selecting  **Fleet Manager**
2\. Go to **Devices**  and select the device that you need create an ilert alarm trigger for
3\. If you haven't added any Data Source, add a **Data Source.** In the screenshot below, we chose **Modbus**
4\. If you haven't added any variables, add them by clicking on the **Variable** under **Data Source**
5\. Add Alarms by clicking on the **Alarm Triggers** and based on the alarm trigger, a message will be sent through Webhook and alerts will be created in ilert
6\. Click **\[Push config to device]** in the top right corner for your changes to take effect.
For more information on IXON Cloud, please refer to .
### References
* [IXON support article: Expand on notifications: call, sms and more, using webhooks](https://support.ixon.cloud/hc/en-us/articles/360018158379-Expand-on-notifications-call-sms-and-more-using-webhooks)
---
# 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/ixon.md?ask=&goal=
```
`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.
