REST API for Latepoint icon

REST API for Latepoint

Consume REST API for LatePoint on Tools

Actions38

Bookings → Create

AI-generated

Summary

Creates a booking in LatePoint by sending a POST request to the REST API's /bookings endpoint. It uses either the individual required fields or a custom JSON or form body.

Inputs

  • Service ID (required) — ID of the service being booked (sent as service_id). Defaults to an $fromAI expression.
  • Agent ID (required) — ID of the agent/staff member assigned (agent_id).
  • Start Date (required) — Booking start date in YYYY-MM-DD format (start_date).
  • Start Time (required) — Booking start time in HH:MM 24-hour format (start_time).
  • Customer ID (required) — ID of an existing customer (customer_id). To create a new customer in the same call, use Send Body with a customer object.
  • Additional Fields — Optional booking fields: end_time, status (default 'approved'), notes, and service_id, agent_id, customer_id, start_date and start_time. The five required fields above override any duplicates here.
  • Send Body — When on, the node sends your custom body and ignores the individual fields, including the required ones and Additional Fields.
  • Body Content Type — JSON or Form Data, shown when Send Body is on. Either way, the node sends the request as JSON.
  • JSON Body — JSON object used as the request body, for example with a nested customer object, status, or send_confirmation. Invalid JSON throws an error.
  • Form Data — Name/value pairs that are assembled into a key-value object body.
  • Description — Free-text prompt/context for AI use. The execute code does not read it, so it has no effect on the request.

Output shape

One item whose json is the response's data object (the created booking). If the response has no data field, the item holds the whole response, or one item per element if the response is an array.

The request is authenticated with a Bearer API key and base URL from the credentials. Errors throw unless Continue On Fail is set, in which case an item with {error: message} is returned. The Send Body fields are not validated, so the API enforces required fields.

Examples

Example 1: Book an existing customer into a service slot

Set Service ID=7, Agent ID=3, Start Date=2024-01-20, Start Time=16:00, Customer ID=42. Optionally add Additional Fields: Status=pending and Notes.

Example 2: Create a booking and a new customer in one call

Enable Send Body, choose JSON, and set JSON Body to {"service_id":7,"agent_id":3,"start_date":"2024-01-20","start_time":"16:00","customer":{"first_name":"Ana","last_name":"López","email":"ana@example.com"},"status":"pending"}.

Links

Discussion