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
The "Get Categories" operation under the "Services" resource in this node allows users to retrieve a list of service categories from the LatePoint REST API. This is useful when you want to fetch all available categories that services are grouped into, for example, to display them in a UI dropdown or to filter services by category in subsequent operations.
Typical use cases include:
- Populating a selection list of service categories for booking or management interfaces.
- Synchronizing service category data with other systems.
- Automating workflows that depend on service categorization.
Properties
| Name | Meaning |
|---|---|
| Description | Provide a description or prompt for the AI to understand the context and purpose of this API operation. |
| Return All | Whether to return all results or only a limited number of categories. |
| Limit | Maximum number of categories to return if not returning all. Value range: 1 to 100. |
Output
The output is a JSON array where each item represents a service category object retrieved from the LatePoint API. Each category object typically contains details such as category ID, name, and possibly other metadata related to the service category.
If multiple categories are returned, the node outputs an array of these objects, each wrapped inside a JSON property named json.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured for the LatePoint REST API.
- The node makes HTTP requests to the LatePoint API base URL using the provided API key for authorization.
- Proper network access to the LatePoint API endpoint is necessary.
Troubleshooting
No credentials configured!
This error occurs if the required API key credential is missing or not set up correctly. To resolve, configure the API key credential in n8n before running the node.Invalid JSON in body (not typical for this operation but possible in others)
If you encounter errors about invalid JSON, ensure that any JSON input fields are properly formatted.API request failures
Network issues, incorrect API keys, or permission problems can cause request failures. Verify your API key validity and network connectivity.Limit and Return All settings
If you do not get all expected categories, check if "Return All" is false and the "Limit" is set too low.