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 integrates with the LatePoint REST API to manage bookings and related resources such as customers, agents, services, payments, orders, coupons, locations, and availability. Specifically, the Bookings - Create operation allows users to create new booking records in the LatePoint system.
Typical use cases include:
- Scheduling appointments or services for customers.
- Automating booking creation based on customer requests or external triggers.
- Creating bookings with either existing customers or new customer details embedded.
- Sending custom JSON or form data bodies for advanced booking creation scenarios.
For example, a business could use this node to automatically create a booking when a customer fills out a web form, specifying service, agent, date/time, and customer contact info.
Properties
| Name | Meaning |
|---|---|
| Description | A text description or prompt explaining the purpose of the API call, helping AI understand context. |
| Send Body | Whether to send a custom request body (JSON or form data) instead of using individual fields. |
| Body Content Type | Format of the custom body content: either JSON or Form Data. |
| JSON Body | The raw JSON object to send as the request body when Send Body is true and Body Content Type is JSON. Example structure includes service ID, agent ID, start date/time, customer details, status, and confirmation flag. |
| Form Data | Collection of key-value pairs to send as form data in the request body when Send Body is true and Body Content Type is form. |
| Additional Fields | Collection of individual fields to specify booking details when not sending a custom body. Includes: |
| - Service ID: Identifier of the service being booked. | |
| - Agent ID: Identifier of the assigned agent/staff member. | |
| - Customer ID: Identifier of the customer making the booking. | |
| - Start Date: Booking start date (YYYY-MM-DD). | |
| - Start Time: Booking start time (HH:MM 24-hour format). | |
| - End Time: Optional booking end time. | |
| - Status: Booking status (default "approved"). | |
| - Notes: Additional notes about the booking. |
Output
The node outputs the response from the LatePoint API after creating the booking. The output is structured as JSON containing the newly created booking record's details, including identifiers, timestamps, status, and any other relevant booking metadata returned by the API.
If multiple bookings are created (e.g., bulk create), the output will be an array of booking objects.
No binary data output is involved.
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 or form data payloads depending on configuration.
Troubleshooting
- Invalid JSON in body: If using custom JSON body, ensure the JSON syntax is valid. Errors parsing JSON will cause the node to throw an error.
- Missing credentials: The node requires a configured API key credential; otherwise, it throws an error.
- Incorrect field values: Ensure required fields like service_id, agent_id, start_date, and start_time are provided and correctly formatted.
- API errors: The node surfaces API error messages. Common issues include invalid IDs, missing required fields, or permission errors.
- To resolve errors, verify input parameters, credential setup, and consult LatePoint API documentation for correct usage.