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, specifically enabling operations on various resources related to booking and customer management. For the Agents resource with the Get operation, the node retrieves detailed information about a specific agent by their unique identifier.
Typical use cases include:
- Fetching detailed data about an individual agent/staff member in a booking system.
- Integrating agent information into workflows for scheduling, notifications, or reporting.
- Automating retrieval of agent profiles based on dynamic input such as user requests or other system events.
Example: You want to get the profile details of an agent with ID "123" to display their availability or contact info in your CRM or booking interface.
Properties
| Name | Meaning |
|---|---|
| Description | Provide a description or prompt for the AI to understand the context and purpose of this API call. |
| ID | The unique identifier of the agent to retrieve. This is required for the Get operation on Agents. |
Output
The output is a JSON object representing the agent's data retrieved from the LatePoint API. The structure typically includes fields such as agent name, contact details, status, creation date, and any metadata associated with the agent.
If multiple agents were returned (not applicable for the Get operation), the output would be an array of such objects. Since this is a single item retrieval, the output is a single JSON object wrapped inside an array element for n8n compatibility.
No binary data output is involved in this operation.
Dependencies
- Requires configuration of an API key credential for authenticating with the LatePoint REST API.
- The base URL and API key must be set up in the node credentials before execution.
- Network connectivity to the LatePoint API endpoint is necessary.
Troubleshooting
- Missing Credentials Error: If no API key credential is configured, the node will throw an error "No credentials configured!". Ensure you have set up the required API authentication token in n8n credentials.
- Invalid ID: Providing an invalid or non-existent agent ID may result in an API error or empty response. Verify the ID is correct and exists in the LatePoint system.
- API Request Failures: Network issues or incorrect base URL can cause request failures. Check your API endpoint URL and network connectivity.
- JSON Parsing Errors: Not applicable for this operation since it uses GET without custom body content.