Inmobalia CRM icon

Inmobalia CRM

Interact with Inmobalia CRM API
Join our community

Actions47

Overview

The node interacts with the Inmobalia CRM API to perform various operations on different resources such as users, contacts, properties, bookings, and more. Specifically, for the User resource with the Get operation, the node retrieves detailed information about a single user by their unique User ID.

This functionality is useful in scenarios where you need to fetch user details from the CRM system for further processing, reporting, or integration with other systems. For example, you might want to retrieve a user's profile data to personalize communications or to synchronize user information with another database.

Properties

Name Meaning
User ID The unique numeric identifier of the user to retrieve (e.g., 12345). This property is required for the "Get" operation on the User resource.

Output

The output is a JSON object representing the user data retrieved from the Inmobalia CRM API. The structure typically includes all available fields related to the user, such as name, email, role, status, and any other metadata stored in the CRM for that user.

Example output structure (simplified):

{
  "id": 12345,
  "name": "John Doe",
  "email": "john.doe@example.com",
  "role": "Agent",
  "status": "Active",
  ...
}

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Inmobalia CRM API.
  • Requires an API authentication token configured via OAuth2 credentials within n8n.
  • The node depends on the createClient function from the bundled client transport module to communicate with the API.

Troubleshooting

  • Common issues:

    • Invalid or missing User ID parameter will cause the operation to fail.
    • Authentication errors if the OAuth2 credential is not properly configured or expired.
    • Network connectivity issues preventing access to the Inmobalia CRM API.

  • Error messages:

    • "Unsupported operation: get" — indicates the operation name may be misspelled or not supported for the selected resource.
    • "Unsupported resource: users" — indicates the resource name may be incorrect or unsupported.
    • API errors returned from the CRM (e.g., user not found) will be wrapped and thrown as node API errors.

  • Resolutions:

    • Ensure the User ID is provided and valid.
    • Verify OAuth2 credentials are correctly set up and have necessary permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion