Inmobalia CRM icon

Inmobalia CRM

Interact with Inmobalia CRM API

Overview

The node interacts with the Inmobalia CRM API to retrieve detailed information about a specific subarea within a location. This operation is useful when you need to fetch granular geographic or administrative subdivision data, such as neighborhoods or districts, identified by their unique Subarea ID.

Common scenarios include:

  • Enriching property listings with precise location details.
  • Filtering or categorizing real estate data based on subareas.
  • Integrating location-specific data into workflows for reporting or analytics.

For example, you might use this node to get detailed information about a subarea to display on a real estate website or to trigger actions based on the subarea's characteristics.

Properties

Name Meaning
Subarea ID The unique numeric identifier of the subarea to retrieve information for.

Output

The node outputs a JSON object containing detailed information about the requested subarea. The exact structure depends on the API response but typically includes fields describing the subarea's name, code, parent area, and other relevant metadata.

No binary data output is produced by this operation.

Example output (simplified):

{
  "id": 123,
  "name": "Downtown",
  "code": "DTN",
  "areaId": 45,
  "additionalInfo": { /* ... */ }
}

Dependencies

  • Requires an active connection to the Inmobalia CRM API.
  • Needs an API authentication token configured in n8n credentials (OAuth2 or similar).
  • Network access to the Inmobalia CRM service endpoint.

Troubleshooting

  • Invalid Subarea ID: If the provided Subarea ID does not exist or is incorrect, the node may throw an error indicating the resource was not found. Verify the ID before running the node.
  • Authentication Errors: Ensure that the API credentials are valid and have sufficient permissions to access location data.
  • Unsupported Operation or Resource: This node only supports the "Get Subarea" operation under the "Location" resource. Using unsupported combinations will result in errors.
  • Network Issues: Connectivity problems can cause timeouts or failures. Check network settings and API availability.

Links and References

Discussion