Actions45
- Block Actions
- Block Action Actions
- Booking Actions
- Group Actions
- Offer Actions
- Reservation Actions
- Folio Actions
- Types Actions
Overview
This node integrates with the Apaleo API to manage group bookings. Specifically, for the "PATCH group" operation, it allows users to update details of an existing group booking by applying a set of changes described in JSON Patch format. This is useful when you need to modify attributes of a group booking such as dates, guest counts, or other metadata without replacing the entire resource.
Practical examples include:
- Adjusting the number of guests in a group reservation.
- Changing the group's booking dates.
- Updating contact information or special requests associated with the group.
Properties
| Name | Meaning |
|---|---|
| Group ID | The unique identifier of the group booking to be updated. |
| Operations | A JSON Patch array describing the operations to perform on the group (e.g., add, replace, remove). |
The "Operations" property expects a JSON array following the JSON Patch standard (RFC 6902), which defines how to specify modifications to apply to the group resource.
Output
The node outputs an array where each element corresponds to the processed input item. Each output item contains a json field representing the updated state of the group booking after applying the patch operations.
If the operation succeeds, the json output will contain the updated group booking data as returned by the Apaleo API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Apaleo API.
- Needs an API authentication token (access token) configured in the node credentials to authorize requests.
- The base URL for API requests is
https://api.apaleo.com.
Troubleshooting
- Invalid Group ID: If the provided Group ID does not exist or is malformed, the API will return an error. Verify that the Group ID is correct.
- Malformed JSON Patch: The "Operations" property must be a valid JSON Patch array. Errors will occur if the JSON is invalid or the patch operations are incorrect. Use a JSON validator and ensure compliance with RFC 6902.
- Authentication Errors: Missing or expired API tokens will cause authorization failures. Ensure the API credentials are correctly set and valid.
- API Rate Limits or Network Issues: Temporary network problems or rate limiting by Apaleo may cause errors. Retry after some time or check network connectivity.
Common error messages typically reflect these issues and can be resolved by verifying inputs and credentials.