Actions40
- Bookings Actions
- Customers Actions
- Agents Actions
- Services Actions
- Payments Actions
- Orders Actions
- Coupons Actions
- Locations Actions
- Availability Actions
- System Info Actions
- Test Actions
Overview
This node interacts with the LatePoint REST API to check the availability of a specific service and agent on a given date. It is useful in scheduling and booking scenarios where you need to verify if an agent (staff member) is available to provide a particular service on a certain day before creating or confirming appointments.
Practical examples include:
- Checking if a hairstylist is available for a haircut service on a requested date.
- Verifying the availability of a consultant for a meeting on a specific day.
- Automating appointment scheduling by validating agent availability programmatically.
Properties
| Name | Meaning |
|---|---|
| Description | A text field to describe the purpose or context of this API call, helping AI understand intent. |
| Service ID | The unique identifier of the service to check availability for. |
| Agent ID | The unique identifier of the agent or staff member whose availability is being checked. |
| Date | The date to check availability for, in YYYY-MM-DD format. |
Output
The output JSON contains the availability information returned by the LatePoint API for the specified service, agent, and date. This typically includes details such as available time slots or status indicating whether the agent is free or booked.
If multiple availability entries are returned, each will be output as a separate JSON item.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the LatePoint REST API.
- The node expects the base URL and API key to be configured in the credentials.
- Network access to the LatePoint API endpoint is necessary.
Troubleshooting
- Missing Credentials: If no API credentials are configured, the node will throw an error "No credentials configured!". Ensure that the API key credential is properly set up.
- Invalid Input Format: Providing invalid dates or non-existent service/agent IDs may result in API errors or empty responses. Verify input values carefully.
- API Errors: Errors from the LatePoint API (e.g., unauthorized, not found) will be surfaced. Check API key validity and resource identifiers.
- JSON Parsing Errors: Not applicable here since inputs are simple strings, but if extended to custom JSON bodies, ensure valid JSON syntax.