Overview
This node acts as a webhook trigger for Apaleo events, starting an n8n workflow whenever specified events occur in the Apaleo system. It listens to real-time notifications from Apaleo about various domain-specific changes such as account updates, bookings, folios, reservations, payments, and more.
Common scenarios where this node is beneficial include:
- Automating workflows based on hotel management system events (e.g., when a reservation is created or canceled).
- Synchronizing data between Apaleo and other systems upon specific event triggers.
- Monitoring financial transactions or invoice status changes automatically.
- Reacting to property or unit changes in real time.
For example, you could use this node to trigger a workflow that sends a notification email every time a booking is created or to update an external CRM when a company record changes.
Properties
| Name | Meaning |
|---|---|
| Events | Select one or multiple Apaleo event types to trigger the workflow on. Options include broad categories like "Account - All Events" or specific events like "Booking - Created", "Invoice - Paid", "Reservation - Canceled", etc. |
| Property IDs | Comma-separated list of property IDs to filter events by. If left empty, the node will receive events for all properties. |
| Ignore Account Level Events Property Filter | Boolean option (default true). When enabled, property filters are ignored for account-level events because these events are not specific to any property. Recommended to keep enabled. |
Output
The node outputs the webhook payload received from Apaleo as JSON data. The output includes:
- The full event data sent by Apaleo.
- An added
_metadatafield containing:timestamp: The ISO timestamp when the event was processed.source: A string identifying the source as"apaleo-webhook".headers: HTTP headers received with the webhook request.query: Query parameters received with the webhook request.
This enriched output allows downstream nodes to access both the event details and contextual metadata about the webhook call.
The node does not output binary data.
Dependencies
- Requires an API authentication credential for Apaleo using OAuth2.
- Needs proper configuration of the webhook URL in Apaleo to point to the n8n webhook endpoint.
- Uses Apaleo's webhook subscription API to create, check, and delete webhook subscriptions automatically.
Troubleshooting
- No webhook data received: If the node receives a webhook request without body data, it returns an error message indicating no data was received. Ensure Apaleo is correctly configured to send event payloads.
- Webhook subscription errors: Errors during creation or deletion of webhook subscriptions may occur due to network issues or invalid credentials. Check API credentials and network connectivity.
- Event filtering issues: If no events trigger the workflow, verify that the selected events and property ID filters match those configured in Apaleo.
- Account-level event filtering: If account-level events are filtered out unexpectedly, ensure the "Ignore Account Level Events Property Filter" option is set appropriately.