Inmobalia CRM icon

Inmobalia CRM

Interact with Inmobalia CRM API
Join our community

Actions47

Overview

This node integrates with the Inmobalia CRM API to retrieve detailed information about a booking's check-out event. Specifically, the "Get Check-Out Event" operation under the "Booking" resource fetches data related to the check-out details of a specified booking.

This node is beneficial in scenarios where you need to automate workflows involving property bookings, such as:

  • Automatically retrieving check-out times and statuses for guest management.
  • Triggering follow-up actions after a guest checks out (e.g., cleaning schedules, billing).
  • Integrating booking check-out data into other systems like accounting or customer relationship management.

Example use case: After a guest completes their stay, this node can be used to fetch the check-out event details by providing the booking ID, enabling downstream processes like invoicing or feedback requests.

Properties

Name Meaning
Booking ID The unique numeric identifier of the booking for which the check-out event details are requested. Example: 12345

Output

The node outputs an array containing one item per execution, each with a json field holding the check-out event data retrieved from the Inmobalia CRM API.

The structure of the json output corresponds to the check-out event object associated with the specified booking. This typically includes details such as:

  • Check-out date and time
  • Status of the check-out
  • Any notes or metadata related to the check-out event

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Inmobalia CRM API.
  • Requires configuration of an OAuth2 API credential for authentication with the Inmobalia CRM service within n8n.
  • The node depends on the internal client created via createClient() to communicate with the API.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Booking ID will likely result in an error or empty response.
    • Missing or misconfigured API credentials will cause authentication failures.
    • Network connectivity issues may prevent successful API calls.

  • Error messages:

    • "Unsupported operation: getCheckOut" — indicates that the operation name was incorrect or not supported; ensure the operation is exactly "getCheckOut".
    • API errors wrapped as NodeApiError may include HTTP status codes and messages from the Inmobalia CRM API; verify the booking ID and API access rights.

  • Resolution tips:

    • Double-check the Booking ID input for correctness.
    • Verify that the OAuth2 credential is properly set up and authorized.
    • Ensure network access to the Inmobalia CRM API endpoint.
    • Review API limits or permissions if encountering authorization errors.

Links and References

Discussion