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 interacts with the Apaleo API to perform various operations related to hotel management. Specifically, for the Folio Action resource and the PUT move multiple charges operation, it allows users to move multiple charges, allowances, or transitory charges from one folio to another within the Apaleo system.
This is useful in scenarios such as correcting billing errors, reallocating charges between guest accounts, or consolidating charges under a single folio for easier management and reporting.
Practical example:
A hotel front desk agent realizes that some charges were mistakenly posted to the wrong guest folio. Using this node operation, they can specify the original folio ID, the target folio ID, and the IDs of the charges to be moved, optionally providing a reason for the move. The node then performs the transfer of these charges via the Apaleo API.
Properties
| Name | Meaning |
|---|---|
| Folio ID | The ID of the source folio from which charges will be moved. |
| Target Folio ID | The ID of the destination folio to which the charges will be moved. |
| Reason | Optional text describing the reason for moving the charges. |
| Charge IDs | Comma-separated list of charge IDs to move from the source folio to the target folio. |
| Allowance IDs | Comma-separated list of allowance IDs to move. |
| Transitory Charge IDs | Comma-separated list of transitory charge IDs to move. |
Output
The node outputs an array of JSON objects representing the result of the move operation for each input item processed. Each output JSON object typically contains details confirming the successful movement of specified charges, allowances, and/or transitory charges between folios.
If the operation fails for any item and "Continue On Fail" is enabled, the output for that item will contain an error message describing the failure.
The node does not output binary data.
Dependencies
- Requires an active connection to the Apaleo API using a valid API authentication token.
- The node expects the user to provide the necessary credentials (an API key or OAuth token) configured in n8n.
- Network access to
https://api.apaleo.commust be available.
Troubleshooting
Common issues:
- Invalid or missing folio IDs: Ensure that both source and target folio IDs exist and are correctly typed.
- Incorrect charge/allowance/transitory charge IDs: Verify that the IDs provided are valid and belong to the source folio.
- Insufficient permissions: The API token used must have rights to modify folios and move charges.
- API rate limits or network connectivity problems may cause failures.
Error messages:
"Invalid folio ID": Check that the folio ID exists and is correct."Charge ID not found": Confirm that the charge IDs belong to the source folio."Unauthorized"or"Forbidden": Verify API credentials and permissions."Failed to move charges": Review the reason field and ensure all required parameters are set properly.
To resolve errors, verify all input parameters, check API credentials, and consult Apaleo API documentation for specific error codes.