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 provides access to the LatePoint REST API, enabling interaction with various resources such as bookings, customers, agents, services, payments, orders, coupons, locations, availability, and system information. Specifically, the "System Info" resource with the "Get" operation allows users to retrieve general system information from the LatePoint API.
Common scenarios for this node include:
- Fetching system metadata or status information for monitoring or reporting.
- Integrating LatePoint system details into workflows for administrative or diagnostic purposes.
Practical example:
- Use the node to get current system info before performing batch operations, ensuring the system is operational and retrieving version or configuration data.
Properties
| Name | Meaning |
|---|---|
| Description | Provide a description or prompt for the AI to understand the context and purpose of this API call. |
Note: For the "System Info" resource and "Get" operation, only the "Description" property is relevant based on the provided input properties.
Output
The node outputs JSON data representing the response from the LatePoint API for the requested resource and operation.
For the "System Info" resource with the "Get" operation, the output JSON contains system-related information returned by the API. This typically includes metadata about the LatePoint system such as version, status, or other informational fields.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests to the LatePoint REST API.
- The base URL for the LatePoint API must be set in the credentials.
- Network connectivity to the LatePoint API endpoint is necessary.
Troubleshooting
- No credentials configured!: The node will throw this error if the required API authentication token is not set up. Ensure that the API key credential is properly configured in n8n.
- Invalid JSON in body: If using custom JSON bodies (not typical for "System Info" Get), malformed JSON will cause errors. Validate JSON syntax before use.
- API request failures: Network issues, incorrect base URL, or invalid API keys can cause request failures. Verify credentials and network access.
- Unexpected response format: If the API changes or returns unexpected data, the node may not parse it correctly. Check API documentation and update node configuration accordingly.