Actions66
- Block Actions
- Block Action Actions
- Booking Actions
- Group Actions
- Offer Actions
- Payment Account Actions
- Payment Account Action Actions
- Reservation Actions
- Reservation Action Actions
- Types Actions
- Folio Actions
- Folio Action Actions
Folio → HEAD folio exists
AI-generatedOverview
This node operation checks the existence of a specific folio in the Apaleo system by performing a HEAD request. It is useful in scenarios where you need to verify if a folio exists before proceeding with further actions, such as updates or deletions. For example, before attempting to update a folio's details, you can use this operation to confirm the folio's presence to avoid errors.
Use Case Examples
- Check if a folio with a given ID exists before updating it.
- Verify folio existence to conditionally trigger workflows based on folio availability.
Properties
| Name | Meaning |
|---|---|
| Folio ID | The ID of the folio to check for existence. |
Output
JSON
statusCode- HTTP status code indicating the result of the HEAD request (e.g., 200 if folio exists, 404 if not found).
Dependencies
- Requires an API authentication token (access token) for the Apaleo API.
Troubleshooting
- If the folio ID is incorrect or does not exist, the node will return a 404 status code indicating the folio was not found.
- Ensure the API credentials are valid and have the necessary permissions to access folio data.
- Network issues or incorrect base URL configuration can cause request failures.
Links
- Apaleo API - HEAD Folio Exists - Official API documentation for checking folio existence using a HEAD request.