Actions7
Alert → List
AI-generatedOverview
This node interacts with the Level API to list alerts based on various filtering and pagination options. It is useful for scenarios where users need to retrieve alert data from their Level system, such as monitoring device alerts, filtering by status, or paginating through large sets of alerts. For example, a user can list all active alerts for a specific device or fetch a limited number of alerts with pagination support.
Use Case Examples
- List all active alerts for a device by specifying the device ID and status.
- Retrieve a limited number of alerts with pagination using 'starting_after' and 'ending_before' cursors.
- Fetch all alerts without limit by enabling the 'Return All' option.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of alert results to return when 'Return All' is false. |
| Device ID | Filter to only include alerts for the specified device ID. |
| Status | Filter to only include alerts with the given status. |
| Starting After | Cursor for pagination to fetch the next page of results after the specified alert ID. |
| Ending Before | Cursor for pagination to fetch the previous page of results before the specified alert ID. |
| Additional Query Parameters | Additional query string parameters supported by the API to customize the request. |
| Response Property Name | If the API response wraps the array in a property, specify that property name to extract the alerts array. |
| Request Options | Settings for batching, SSL validation, proxy, and timeout for the API request. |
Output
JSON
alerts- Array of alert objects returned from the API, filtered and paginated according to input parameters.
Dependencies
- Level API with API key credential
Troubleshooting
- Ensure the API credentials are correctly configured to avoid authentication errors.
- Check that the device ID and status filters are valid to prevent empty or incorrect results.
- If pagination cursors ('starting_after' or 'ending_before') are incorrect, the node may return unexpected pages or no results.
- Timeout or proxy settings may need adjustment if the API requests fail or are slow.
Links
- Level API Alerts Documentation - Official documentation for the Level API alerts endpoint, detailing available query parameters and response structure.