Actions9
- User Actions
- Company Actions
- Immobilie Actions
Overview
The node interacts with the ImmoJump API, specifically supporting operations on various resources including "Immobilie" (real estate properties). For the "Get Many" operation on the "Immobilie" resource, it retrieves multiple real estate entries from the API. This is useful for scenarios where users want to fetch a list of properties, for example, to display available real estate listings, synchronize property data with another system, or perform batch processing on multiple properties.
Practical examples:
- Fetching up to 50 real estate properties to show in a dashboard.
- Retrieving all properties without limit for full data export.
- Paginating through large sets of properties by controlling the number of results per request.
Properties
| Name | Meaning |
|---|---|
| Return All | Boolean flag indicating whether to return all matching properties or limit the results. |
| Limit | Maximum number of properties to return when "Return All" is false. Range: 1 to 100. |
- Return All: If set to true, the node will paginate through all available properties and return them all. If false, only up to the specified "Limit" number of properties are returned.
- Limit: Defines the maximum number of properties to retrieve when not returning all. Defaults to 50.
Output
The node outputs JSON data representing an array of real estate property objects retrieved from the ImmoJump API. Each item corresponds to one property with its associated fields as provided by the API.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the ImmoJump API.
- Needs configuration of base URL, token, and organization ID in the credentials.
- The node uses HTTP requests with bearer token authorization and includes the organization ID header if provided.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Not setting the organization ID may result in errors or empty responses.
- Requesting too many items without pagination might lead to incomplete data or API rate limits.
Error messages:
- API errors will be logged with their message and status code.
- Unexpected payloads (non-array responses) will trigger warnings.
- Missing organization ID will log an error and may prevent tag retrieval (related resource).
Resolutions:
- Verify that API credentials are correctly configured with valid token and base URL.
- Ensure the organization ID is set if required by your ImmoJump account.
- Use the "Return All" option to handle pagination automatically for large datasets.
Links and References
- ImmoJump API Documentation (replace with actual URL)
- n8n documentation on HTTP Request Node for understanding API calls
- General guidance on Pagination in APIs