> 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/tideways.md).
# Tideways Integration
Create alerts in ilert from Tideways notifications — with ilert's Tideways inbound integration.
[Tideways](https://tideways.com/) is an application performance monitoring and profiling platform for PHP applications. It detects errors, performance regressions, and slow transactions in production and forwards them to your tools through notifications. With this integration, Tideways notifications automatically create alerts in ilert, so the right responders are notified and escalations happen reliably.
## In ilert: Create a Tideways alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **Tideways**, 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 generates a webhook URL for your alert source. Copy it — you will need it in the next section.
## In Tideways: Create an integration
1. Open your **organization**, click on **Settings**, then on **Integrations** and click on **Create new integration**.
2. Choose a name for the integration, paste the webhook URL you copied from ilert, choose the settings you want, click on **Next** and then on **Create**.
## In Tideways: Create a notification
1. Go back to the project you want to be alerted on, click on **Project settings**, then on **Notifications** and on **Create new notification**. Choose the notification type you want.
2. Choose the settings you want, select the integration you created earlier and click on **Create**.
When the notification triggers, Tideways posts its payload to ilert, which creates an alert.
## FAQ
#### **Which Tideways payloads create alerts in ilert?**
Tideways sends multiple different payloads. The types `weekly_report`, `release`, and `compare_release` carry no actionable state, so they are dropped by default and do not create alerts.
#### **Can I still be alerted on the dropped payloads?**
Yes. You can opt in to them by editing the [event filters](/alerting/configure-alerting/alert-sources.md#event-filter) of your Tideways alert source.
#### **Is this integration bidirectional?**
No. The integration is one-directional: Tideways sends notifications to ilert. Acknowledging or resolving an alert in ilert is not synced back to Tideways, and vice versa.
#### **Can I connect Tideways with multiple alert sources in ilert?**
Yes. Create an additional integration in Tideways for each alert source and point it at that alert source's webhook URL, then reference the integration from the relevant project notifications.
---
# 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/tideways.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.
