REST API for LatepointInstall

Summary

Deletes a single LatePoint booking by ID by sending a DELETE request to the REST API's /bookings/{id} endpoint, once per input item.

Inputs

• ID (required) — Unique identifier of the booking to delete. It is appended to the URL path as /bookings/{id}. Can be set by an expression or filled by an AI agent.
• Description — Free-text note describing the purpose of the call, mainly as context for AI agents. The execute code does not read it, so it has no effect on the request.

Output shape

One output item per input item. It holds the API response's data field if present, otherwise the raw response body (array responses are split into one item per element).

The node sends no request body or query string. The exact response shape depends on the LatePoint REST API. If 'Continue on Fail' is enabled, a failed item returns {error: message} instead of stopping the workflow. Authentication uses the Bearer API key and base URL from the configured credentials.

Examples

Example 1: Remove a booking that was cancelled in an external system

Resource: Bookings, Operation: Delete, ID: {{ $json.booking_id }}

Example 2: Let an AI agent delete a booking on request

Resource: Bookings, Operation: Delete, ID filled by the agent from conversation context, Description: 'Delete the booking the user asked to remove'

Links

• n8n community nodes installation guide