Overview

This node operation retrieves multiple alert records from the Everest Transport Management System (TMS). It is useful for scenarios where users need to fetch a list of alerts with optional filtering and pagination, such as monitoring unread alerts, searching alerts by text, or limiting the number of results returned. For example, a user can fetch the first 50 unread alerts or search alerts containing specific keywords.

Use Case Examples

1. Fetch the first 50 alerts regardless of status.
2. Retrieve unread alerts starting from the 10th alert for pagination.
3. Search alerts containing the term 'delivery delay'.

Properties

Output

JSON

• id - Unique identifier of the alert.
• title - Title or summary of the alert.
• message - Detailed message content of the alert.
• status - Read status of the alert (e.g., unread or read).
• createdAt - Timestamp when the alert was created.
• updatedAt - Timestamp when the alert was last updated.

Dependencies

• Requires an API key credential for Everest TMS to authenticate requests.

Troubleshooting

• If the node returns no alerts, verify that the search term meets the minimum character requirement (3 characters) and that the status filter is set correctly.
• Errors related to authentication indicate issues with the provided API key credential; ensure it is valid and has necessary permissions.
• Pagination parameters (Limit and Limit Start) must be non-negative integers; invalid values may cause errors or unexpected results.