Overview

This node operation retrieves multiple client records from the Everest Transport Management System (TMS). It supports filtering and pagination options, allowing users to specify the maximum number of clients to return, the starting offset for pagination, search terms to filter clients by name or other attributes, and date filters to return clients who had missions within a specified date range. Additionally, it can filter to return only clients who have missions. This operation is useful for scenarios where bulk client data retrieval is needed, such as generating reports, syncing client data with other systems, or performing batch updates.

Use Case Examples

1. Retrieve up to 50 clients who had missions between January 1, 2025, and December 31, 2025.
2. Search for clients with names matching a specific term and paginate results starting from the 10th client.
3. Get all clients who currently have missions assigned.

Properties

Output

JSON

• id - Unique identifier of the client.
• first_name - Client's first name.
• last_name - Client's last name.
• email - Client's email address.
• missions - List or count of missions associated with the client, if included.

Dependencies

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

Troubleshooting

• Common issues include API authentication failures due to invalid or missing credentials. Ensure the API key is correctly configured.
• Pagination parameters (limit and limit_start) must be within valid ranges; otherwise, the API may return errors or unexpected results.
• Date filters must be in the correct format and timezone (Europe/Paris) to work properly.
• If the 'With Missions Only' option is used without date filters, ensure that the API supports this filter to avoid empty results.