REST API for Latepoint icon

REST API for Latepoint

Consume REST API for LatePoint on Tools
Join our community

Actions40

Overview

This node integrates with the LatePoint REST API to manage services and other related resources such as bookings, customers, agents, payments, orders, coupons, locations, and availability. Specifically for the Services - Create operation, it allows users to create a new service record in the LatePoint system.

Typical use cases include:

  • Adding new services that your business offers, specifying details like name, description, duration, pricing, and visibility.
  • Automating service creation workflows when new offerings are added or updated in external systems.
  • Integrating with booking or CRM systems to keep service catalogs synchronized.

For example, you might use this node to create a new massage therapy service with a 60-minute duration, set pricing, and mark it as publicly visible so customers can book it.

Properties

Name Meaning
Description A text prompt describing the purpose of the API call, helping AI understand the context.
Send Body Boolean flag indicating whether to send a custom JSON or form data body instead of individual fields.
Body Content Type When sending a custom body, choose between JSON or Form Data format.
JSON Body The raw JSON object to send as the request body when using JSON format. Example structure for bookings is provided in the description but for services, this would contain service-specific fields.
Form Data Collection of key-value pairs to send as form data parameters when using form data format.
Additional Fields Collection of individual service properties to include when creating the service. These fields are:
- Name The name/title of the service.
- Short Description A brief description of the service.
- Duration (minutes) Length of the service in minutes (default 60).
- Charge Amount The price charged for the service.
- Deposit Amount Any deposit amount required for the service.
- Category ID Identifier for the category this service belongs to.
- Order Number Numeric order for sorting services.
- Visibility Whether the service is Public or Private. Public services are visible to customers; private ones are not.

Output

The node outputs the response from the LatePoint API after creating the service. The output is a JSON object representing the newly created service record, including all its properties as stored by the API.

If multiple items were returned (not typical for create), each item would be output separately. There is no binary data output for this operation.

Dependencies

  • Requires an API key credential for authenticating with the LatePoint REST API.
  • The base URL and API key must be configured in the node credentials.
  • The node sends HTTP requests with JSON content type by default.
  • No additional external dependencies beyond the LatePoint API and n8n environment.

Troubleshooting

  • Invalid JSON in body: If using the JSON Body option, ensure the JSON syntax is correct. Errors will indicate parsing issues.
  • Missing credentials: The node throws an error if the API key credential is not configured.
  • API errors: The LatePoint API may return errors for invalid field values, missing required fields, or permission issues. Check the API documentation for specific error codes.
  • Empty or incorrect fields: Ensure required service fields like name and duration are provided either via Additional Fields or JSON/Form Data body.
  • Network issues: Verify connectivity to the LatePoint API endpoint and that the API key has proper permissions.

Links and References

Discussion