Actions55
- Client Actions
- General Actions
- Mission Actions
- Agent Actions
- Invoice Actions
- Contact Actions
- Alert Actions
- Walter Actions
- Notification Actions
- Webhook Actions
- Route Actions
- Export Actions
Overview
The "Get Available Slots" operation under the "General" resource in this node allows users to retrieve available time slots for a specified service, optionally filtered by establishment and time constraints. This is useful in scenarios such as scheduling appointments, booking resources, or managing availability within a transport management system.
For example, a logistics coordinator could use this node to find open delivery windows for a particular service at a specific establishment starting from a given date/time, helping optimize route planning and resource allocation.
Properties
| Name | Meaning |
|---|---|
| Service | The specific service to get available slots for. |
| Establishment | (Optional) The establishment to narrow down the slot search. |
| From Time | (Optional) The start datetime from which to begin searching for available slots. |
| Maximum Days | (Optional) The maximum number of days to search for available slots, defaulting to 7 days. |
Output
The output is a JSON array containing the available slots retrieved for the specified service and optional filters. Each item in the array represents an available slot with details such as time and possibly location or other metadata depending on the API response.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to the slots, but this operation primarily returns structured JSON data about availability.
Dependencies
- Requires an API key credential for authenticating requests to the Everest Transport Management System.
- Relies on the Everest API endpoints to fetch services, establishments, and available slots.
- The node uses internal helper methods to load options dynamically for properties like Service and Establishment.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Specifying a service or establishment that does not exist or is unavailable may return empty results.
- Incorrect date/time formats for the "From Time" property can lead to errors or no results.
Error Messages:
- Authentication errors indicate issues with the provided API key; verify and update credentials.
- "No available slots found" means the query returned no results; try adjusting filters or date ranges.
- Network or timeout errors suggest connectivity problems; check network settings and retry.
Links and References
- Everest TMS official API documentation (refer to your organization's internal or public docs)
- n8n documentation on creating and using custom nodes
- General REST API best practices for handling authentication and pagination