> ## Documentation Index > Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt > Use this file to discover all available pages before exploring further. # Node alerts > Get an email when an API / SOAP node fails repeatedly or when an AI Agent has a model or security issue **Node alerts** notify you by email when something in your workflows' nodes needs your attention. You choose who receives the emails and, for AI Agents, which alert types you want. ## What node alerts are There are two groups of alerts, one for each node type: | Node type | Available alerts | | - | - | | **API / SOAP** | Repeated failures against the same endpoint | | **AI Agent** | Model lifecycle and Security | Model lifecycle notices also appear in the Notification Center bell, under the **Infrastructure** filter, whether or not you configured recipients. Email is an additional channel. ## How to configure them Go to **Settings** > **Node alerts**. In the **Node type** sub-menu select the **API / SOAP** or **AI Agent** tab. Each tab has its own list of recipients. In the **Recipients** card, type an email address and click **+ Add**. To remove one, click the **✕** next to it. In the **Alert types** card check **Model lifecycle**, **Security**, or both. Click **Save**. To undo what you changed, click **Discard**. Node alerts screen with the AI Agent tab, the recipients list and the alert type checkboxes While a tab has no recipients you will see the message *"There are no recipients yet. Alerts will not be sent by email."* ## API / SOAP alerts An email is sent when an API or SOAP node **fails 100 times in 5 minutes against the same endpoint**. After that alert, we wait **8 hours** before alerting again for that same endpoint. The email includes: * Company, service URL, affected users, event count and monitoring interval. * The failing request and the error message. * Model type and name, execution ID, alert ID and node ID. ## AI Agent alerts The **AI Agent** tab has an **Alert types** card with two options. If no specific selection is made, all types are sent. ### Model lifecycle You get an email when a model used by an **AI Agent** or **AI Task** node is about to be deprecated, has been retired, or no longer exists in the catalog. At most one email is sent every 3 days per model. The email includes the model, its status, the retirement date and where it is used (skill and node ID). Email with the amber model lifecycle badge and the details of the affected model ### Security You get an email when a security threat is detected or blocked in an AI agent, for example prompt injection, jailbreak or system prompt leak. The email includes the result (blocked or detected), the phase, the threat types, the level, the confidence, the detection methods and where it happened. Email with the red security badge and the details of the blocked threat ## Anti-spam limits | Alert | Limit | | - | - | | API / SOAP | 100 failures in 5 minutes per endpoint; then an 8-hour wait for that same endpoint | | Model lifecycle | At most one email every 3 days per model | | Security | At most one email per hour for each node and threat type | ## Email language Emails use the new Jelou design, with a colored badge by alert type: amber for model lifecycle and red for security. They are available in Spanish, English and Portuguese. ## FAQ Check these two causes: * **There are no recipients**: the node type tab has no emails added. Add them and click **Save**. * **The alert type is unchecked**: in the **AI Agent** tab, confirm that **Model lifecycle** or **Security** is checked. Also keep in mind that the sending limits can mean a new event does not trigger another email right away. Yes. **API / SOAP** and **AI Agent** are configured separately. Yes, model lifecycle notices still appear in the bell, under the **Infrastructure** filter. ## Related nodes Connect your flow to external services. Configure your AI agent. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.