REST API for Latepoint icon

REST API for Latepoint

Consume REST API for LatePoint on Tools
Join our community

Actions40

Overview

This node provides integration with the LatePoint REST API, enabling users to manage various booking-related resources such as customers, bookings, agents, services, payments, orders, coupons, and locations. Specifically, for the Customers - Get operation, the node retrieves detailed information about a single customer by their unique identifier.

Common scenarios where this node is beneficial include:

  • Fetching customer details to display or process in workflows.
  • Integrating customer data retrieval into automated booking or CRM processes.
  • Using customer information to personalize communications or trigger other actions.

For example, you might use this node to get a customer's full profile when a new booking is created, allowing you to verify contact details or check customer status before proceeding.

Properties

Name Meaning
Description A text prompt or description to provide context or purpose of the API call (optional).
ID The unique identifier of the customer to retrieve. This is required for the "Get" operation.

Output

The output of the node is a JSON object representing the retrieved customer data from the LatePoint API. The structure typically includes all available fields for the customer resource, such as:

  • Customer ID
  • First name
  • Last name
  • Email address
  • Phone number
  • Status (e.g., active/inactive)
  • Created date
  • Metadata (if requested)

If multiple customers were returned (not applicable for the "Get" operation but relevant for "Get All"), the output would be an array of such objects.

The node does not output binary data.

Dependencies

  • Requires a configured API key credential for authenticating with the LatePoint REST API.
  • The base URL and API key must be set in the node credentials.
  • Network access to the LatePoint API endpoint is necessary.

Troubleshooting

  • No credentials configured!: This error occurs if the API key credential is missing or not set up correctly. Ensure that the API key credential is configured in n8n before running the node.
  • Invalid JSON in body: If using custom JSON bodies (not typical for "Get" operations), ensure the JSON syntax is correct.
  • Resource or ID missing: For the "Get" operation, the ID property is required. Omitting it will cause errors.
  • API connectivity issues: Check network connectivity and API endpoint availability if requests fail.
  • Permission errors: Ensure the API key has sufficient permissions to read customer data.

Links and References

Discussion