Actions38
- Bookings Actions
- Customers Actions
- Agents Actions
- Services Actions
- Payments Actions
- Orders Actions
- Coupons Actions
- Locations Actions
- Availability Actions
Availability → Check Availability
AI-generatedSummary
Checks availability for a given service and agent on a specific date by sending a GET request to the LatePoint REST API /availability endpoint, and returns the API's response data.
Inputs
- Service ID (required) — ID of the service to check. Sent as the
service_idquery parameter. Defaults to an AI-fillable$fromAIexpression. - Agent ID (required) — ID of the agent/staff member to check. Sent as
agent_id. Defaults to an AI-fillable$fromAIexpression. - Date (required) — Date to check in YYYY-MM-DD format. Sent as
date. Defaults to an AI-fillable$fromAIexpression. - Description — Free-text prompt/context for AI use. It is not read by the execute code and is not sent to the API.
Output shape
One output item per input item. Its json is the data field of the API response if present. Otherwise, if the response is an array, each element becomes its own item. Otherwise the whole response body is returned.
The exact slot structure depends on the LatePoint REST API, which the source does not define. Authentication uses a Bearer API key and base URL from the node credentials. With 'Continue on Fail' enabled, errors are returned as items shaped
{ error: message }. The node does not validate the date format.
Examples
Example 1: Check whether a specific stylist is free for a haircut on a given day before booking.
Resource: Availability; Operation: Check Availability; Service ID: 3; Agent ID: 5; Date: 2026-10-15
Example 2: Let an AI agent find open slots from a chat request such as 'Is Anna free next Monday for a massage?'
Leave Service ID, Agent ID and Date as the default $fromAI expressions so the model fills them in from the conversation.