Actions57
- Booking Actions
- Group Actions
- Offer Actions
- Block Actions
- Block Action Actions
- Reservation Actions
- Reservation Action Actions
- Types Actions
- Folio Actions
- Folio Action Actions
Overview
This node integrates with the Apaleo API to manage group-related operations, specifically allowing users to create reservations for a group booking. It is useful in scenarios where multiple reservations need to be handled collectively under a single group booking, such as corporate travel arrangements, event bookings, or group tours.
For example, a travel agency can use this node to add multiple guest reservations to an existing group booking in Apaleo, streamlining the management of group stays and ensuring all reservations are linked properly.
Properties
| Name | Meaning |
|---|---|
| Group ID | The unique identifier of the group booking for which reservations will be created. |
| reservations Data | JSON-formatted data containing details of the reservations to be added to the group. |
Output
The node outputs an array of JSON objects representing the results of the reservation creation requests for the specified group. Each object typically contains the response data from the Apaleo API about the newly created reservations, including confirmation details and any relevant metadata.
If errors occur during processing, the output may include error messages associated with specific input items, depending on whether the node is configured to continue on failure.
Dependencies
- Requires an active connection to the Apaleo API via an API authentication token.
- The node expects the user to provide valid credentials with appropriate permissions to manage group bookings and reservations.
- Network access to
https://api.apaleo.comis necessary.
Troubleshooting
- Invalid Group ID: If the provided Group ID does not exist or is incorrect, the API will return an error. Verify the Group ID before running the node.
- Malformed Reservations Data: The reservations data must be valid JSON and conform to the expected schema by Apaleo. Invalid JSON or missing required fields will cause failures.
- Authentication Errors: Ensure that the API token is valid and has not expired. Authentication failures will prevent the node from executing successfully.
- API Rate Limits: Excessive requests might trigger rate limiting by Apaleo. Implement retries or backoff strategies if needed.
- Continue On Fail Setting: If enabled, the node will continue processing subsequent items even if some fail, returning error details in the output.
Links and References
- Apaleo API Documentation
- Apaleo Group Bookings Guide (if available)
- n8n Documentation on Using HTTP Request Nodes for custom API calls