> 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/4me.md). # 4me Integration Create alerts in ilert based on problems or requests from 4me. [4me](https://www.4me.com/) is a service management platform designed to streamline collaboration and workflow management across various departments and organizations. It focuses on providing seamless service integration and management capabilities, allowing businesses to handle IT, HR, and other service-related processes efficiently. Following the instructions below, you can connect 4me with ilert and automatically notify your team when a request or a problem is created within 4me. ## In ilert: Create a 4me alert source 1. Go to **Alerting** → **Alert sources** and click **Create new alert source**. 2. Search for **4me**, 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**.
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.

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. ## In 4me: Create a an OAuth token 1. Click on the profile avatar -> **My Profile**.
2. Now click on **Personal Access Tokens** -> **Generate new token**.
3. Enter a name and click on **Add record types...**.
4. Add Problem and Request. 5. Activate all checkboxes and click on **Generate Token.**
6. Copy the token. ## In ilert: Finish 4me alert source setup 1. Select your previously created 4me alert source and click on 4me settings. 2. Enter the 4me account name and the previously created OAuth token into the associated fields.
3. Select the 4me region. The region can be found in the URL of your 4me instance.
## In 4me: Create a webhook 1. Click on the hamburger menu on the top left corner -> settings icon.
2. In the searchbar enter: "webhook" and click on **Webhooks** in the search result.
3. Click on the "+" to create a new webhook.
4. Add following webhooks each event: `problem.create`, `problem.update`, `request.create`, `request.update`, `automation_rule`. 5. Enter a name, the Event type and your 4me alert source URL.
6. The webhook will then be verified.
7. After couple seconds the webhook should update with **Last deilvery 200**.
## FAQ **Will alerts in ilert be resolved automatically?** Yes, make sure that webhooks for following events have been created: `problem.update`, `request.update`. As soon as the status of a problem or request is solved in 4me, the corresponding alert in ilert will be resolved. **Will alerts in ilert be accepted automatically?** Yes, make sure that webhooks for following events have been created: `problem.update`, `request.update`. As soon as the status of a problem or request is accepted in 4me, the corresponding alert in ilert will be accepted. --- # 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/4me.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.