Everest icon

Everest

Interact with Everest TMS (Transport Management System)

Route → Get Many

AI-generated

Overview

This node operation retrieves multiple route records from the Everest Transport Management System (TMS). It supports filtering and pagination options to customize the query, such as limiting the number of results, filtering by agent, service, search terms, route statuses, and date ranges. It also allows sorting the results by various fields like start date or creation date in ascending or descending order. This operation is useful for users who need to fetch and analyze multiple routes, for example, to monitor ongoing deliveries, generate reports, or integrate route data into other workflows.

Use Case Examples

  1. A logistics manager wants to get a list of all ongoing routes assigned to a specific agent within a certain date range to monitor delivery progress.
  2. A transportation coordinator needs to retrieve the last 50 routes sorted by start date to analyze route efficiency.
  3. A system integrator fetches routes filtered by service type and status to synchronize with an external reporting tool.

Properties

Name Meaning
Options Collection of optional parameters to filter, paginate, and sort the routes retrieved.

Output

JSON

  • id - Unique identifier of the route.
  • title - Title or name of the route.
  • status - Current status of the route.
  • start_date - Start date and time of the route.
  • end_date - End date and time of the route.
  • agent_id - Identifier of the agent assigned to the route.
  • service_id - Identifier of the service associated with the route.
  • distance - Distance covered by the route.
  • duration - Duration of the route.

Dependencies

  • Everest TMS API with an API key credential

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to access route data.
  • Check that the date filters are in the correct timezone (Europe/Paris) and format to avoid empty results.
  • If no routes are returned, verify the filter criteria such as agent, service, statuses, and search terms are valid and exist in the system.
  • Pagination parameters (limit and limit_start) should be set correctly to avoid missing data or excessive data retrieval.

Links

Discussion