Apaleo icon

Apaleo

Interact with Apaleo API
Join our community

Actions45

Overview

This node interacts with the Apaleo API, specifically allowing management of various resources including Folios. For the DELETE folio operation, it deletes a folio identified by its ID from the Apaleo system. This is useful in scenarios where you need to remove billing or accounting records (folios) associated with bookings or reservations that are no longer valid or required.

Practical examples:

  • Automatically deleting folios when a booking is canceled.
  • Cleaning up test or temporary folios created during development or integration testing.
  • Managing folios programmatically as part of a larger workflow for hotel or property management automation.

Properties

Name Meaning
Folio ID The unique identifier of the folio to delete. This is a required string input.

Output

The node outputs an array of JSON objects corresponding to each input item processed. For the DELETE folio operation, the output typically contains confirmation of deletion or relevant response data from the Apaleo API indicating success or failure of the deletion request.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Apaleo API.
  • Needs an API authentication token (access token) configured via credentials in n8n.
  • The base URL for API requests is https://api.apaleo.com.
  • Proper permissions on the API key to perform delete operations on folios.

Troubleshooting

  • Common issues:

    • Invalid or missing Folio ID will cause the API call to fail.
    • Insufficient permissions on the API token may result in authorization errors.
    • Network connectivity issues can prevent successful API communication.

  • Error messages and resolutions:

    • "Folio not found" — Verify the Folio ID is correct and exists.
    • "Unauthorized" or "Forbidden" — Check API credentials and ensure they have delete rights.
    • "Request failed" or timeout errors — Confirm network access and API availability.

  • To handle failures gracefully, enable "Continue On Fail" in the node settings to process subsequent items even if one fails.

Links and References

Discussion