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 within a property management or booking system. Specifically, for the "Group" resource and the "GET group" operation, it retrieves detailed information about a specific group booking by its unique identifier. This is useful in scenarios where you need to fetch comprehensive data about a group reservation, such as for reporting, auditing, or further processing in workflows.
Practical examples include:
- Fetching details of a corporate group booking to verify reservation status.
- Retrieving additional related data like blocks or actions associated with the group when managing complex group reservations.
- Integrating group booking data into external systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Group ID | The unique identifier of the group booking to retrieve. This is required to specify which group to fetch. |
| Expand | Optional additional data to include in the response. Possible values: "Blocks", "Actions". Selecting these will include related block or action data linked to the group. |
Output
The node outputs JSON data representing the group booking details retrieved from the Apaleo API. The structure includes all standard fields describing the group booking, such as identifiers, dates, status, and potentially expanded related data if requested (blocks or actions).
If the "Expand" property includes "Blocks," the output will contain detailed information about blocks associated with the group. Similarly, if "Actions" is selected, the output will include action records related to the group.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Apaleo API via an API authentication token credential configured in n8n.
- The node depends on network access to
https://api.apaleo.com. - Proper permissions on the API key are necessary to read group booking data.
Troubleshooting
- Missing or invalid Group ID: The operation requires a valid group booking ID. Ensure the "Group ID" property is correctly set and corresponds to an existing group.
- Authentication errors: If the API token is missing, expired, or lacks permissions, the node will fail. Verify that the API credentials are correctly configured and have sufficient rights.
- API rate limits or connectivity issues: Network problems or hitting API rate limits can cause failures. Check network connectivity and consider retry logic or error handling in your workflow.
- Invalid expand options: Providing unsupported values in the "Expand" property may result in incomplete or failed responses. Use only the documented options ("Blocks", "Actions").