Everest icon

Everest

Interact with Everest TMS (Transport Management System)
Join our community

Actions55

Overview

The node integrates with the Everest Transport Management System (TMS) to retrieve various types of data related to transport management. Specifically, for the "General" resource and the "Get Skills" operation, it fetches a list of skills available in the system. This can be useful for scenarios where you want to filter or assign tasks based on specific skill sets within your transport operations.

Practical examples include:

  • Fetching all skills to populate dropdowns in other workflows.
  • Filtering transport agents or missions by required skills.
  • Automating assignment of tasks based on skill availability.

Properties

Name Meaning
Options A collection of optional filters to refine the results:
- Search A string term to filter skills by name (e.g., "driving").
- Establishment (Not applicable for Get Skills operation; used for other operations.)

Note: For the "Get Skills" operation, only the "Search" option is relevant and visible.

Output

The output is a JSON array where each item represents a skill object retrieved from Everest TMS. Each skill typically contains at least:

  • name: The name of the skill.
  • id: The unique identifier of the skill.

Example output structure:

[
  {
    "id": "skill_id_1",
    "name": "Driving"
  },
  {
    "id": "skill_id_2",
    "name": "Forklift Operation"
  }
]

No binary data is output by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Everest TMS API.
  • The node uses the Everest API endpoints internally to fetch skills (POST /skills).
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Empty results: If no skills are returned, verify that the API credentials are correct and have sufficient permissions. Also, check if the search term is too restrictive.
  • API errors: Common error messages may relate to authentication failures or network issues. Ensure the API key is valid and the Everest service is reachable.
  • Load options failure: If the dynamic loading of establishments or skills fails, it might be due to API downtime or permission issues.

Links and References

  • Everest TMS official documentation (not provided here, but recommended to consult for API details)
  • n8n documentation on creating and using custom nodes and credentials

Discussion