Actions60
- Organization Actions
- Building Actions
- Resident Actions
- Channel Actions
- Message Actions
- Post Actions
- Event Actions
- Poll Actions
- Incident Actions
- Asset Actions
- Booking Actions
- Classified Actions
- Document Actions
- Notification Actions
- Council Project Actions
- Council Vote Actions
- Council Meeting Actions
- Council Task Actions
Booking → Update
AI-generatedSummary
Update a booking by ID, optionally modifying notes and status.
Inputs
- bookingId (required) — The ID of the booking to update, retrieved from the node parameter 'bookingId'. Default value is 0 but must be provided for the operation to succeed.
- additionalFields — A collection of optional fields to include in the update payload. Supported sub-fields per the node's definition are 'notes' (string) and 'status' (options: pending, confirmed, cancelled). The node passes whatever is provided in this collection as the 'booking' object in the API request body.
Output shape
The updated booking object as returned by the Nido API response (typically the full booking record after the PATCH operation).
If the API call succeeds, the result is pushed as the main output data. On failure with 'continue on fail' enabled, an error object is emitted instead.
Examples
Example 1: Update booking status to confirmed and add notes.
Set 'bookingId' to the target booking's numeric ID. In 'additionalFields', add a 'notes' string and set 'status' to 'confirmed'. The node will send a PATCH request to /bookings/{bookingId} with body { booking: { notes: '...', status: 'confirmed' } }.