Actions21
Overview
This node integrates with the Square API to manage bookings. Specifically, the Update Booking operation allows users to modify details of an existing booking by providing its ID and the fields to update. This is useful in scenarios where appointment times, customer notes, or seller notes need to be changed after a booking has been created.
Practical examples include:
- Changing the start time of a scheduled appointment.
- Adding or updating notes from the customer or seller regarding the booking.
- Correcting booking details without needing to cancel and recreate the booking.
Properties
| Name | Meaning |
|---|---|
| Booking ID | The unique identifier of the booking to update. |
| Update Fields | A collection of fields that can be updated for the booking: |
| - Customer Note: A note from the customer about the booking. | |
| - Seller Note: A note from the seller about the booking. | |
| - Start At: The new start time of the booking in RFC 3339 date-time format (e.g., ISO). |
Output
The output is a JSON object representing the updated booking resource as returned by the Square API. It contains all relevant booking details including any updated fields such as start time and notes.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Square API via an API key credential.
- The node uses the Square API endpoint for bookings, switching between sandbox and production environments based on the configured credentials environment setting.
- No additional external dependencies are required beyond the Square API access.
Troubleshooting
- Missing or invalid Booking ID: The node requires a valid booking ID to update. Ensure the ID exists and is correctly provided.
- Empty update fields: If no fields are specified to update, the API call may fail or have no effect. Always provide at least one field to update.
- API authentication errors: Verify that the API key credential is valid and has permissions to update bookings.
- Date format issues: The "Start At" field must be in proper RFC 3339 format (ISO 8601). Invalid formats will cause errors.
- Continue On Fail behavior: If enabled, errors for individual items will be captured in the output instead of stopping execution.