Actions14
Overview
This node integrates with the onOffice API to retrieve detailed information about real estate properties (estates). Specifically, the "Estate - Get" operation fetches data for a single estate by its unique ID. It allows users to specify which fields of the estate they want to retrieve, enabling tailored queries that return only relevant information.
Common scenarios where this node is beneficial include:
- Real estate agencies wanting to pull detailed property data into their workflows.
- Automating updates or synchronization of estate information between onOffice and other systems.
- Generating reports or notifications based on specific estate attributes.
For example, a user can input an estate ID and select fields like title, price, city, and type to get a concise dataset about that property for further processing or display.
Properties
| Name | Meaning |
|---|---|
| Estate ID | The unique identifier of the estate to retrieve. |
| Fields to Retrieve | Select which fields to retrieve for the estate. Options include: |
| - ID: Estate ID in onOffice | |
| - External Object Number: External reference number | |
| - Title: Title of the estate | |
| - Type: Type of estate (apartment, house, etc.) | |
| - Marketing Type: Sale or rental | |
| - Price: Purchase price | |
| - Cold Rent: Cold rent price | |
| - Warm Rent: Warm rent price | |
| - Living Space: Living area in m² | |
| - Usable Space: Usable area in m² | |
| - Plot Area: Land area in m² | |
| - City: City | |
| - Postal Code: Postal/ZIP code | |
| - Street: Street name | |
| - House Number: House/building number | |
| - Location Description: Description of the location | |
| - Object Type: Detailed object type |
Output
The output JSON contains the requested estate data fields as key-value pairs corresponding to the selected fields. Each output item represents one estate record with its properties.
Example structure of the json output field:
{
"Id": "12345",
"objektnr_extern": "EXT-6789",
"objekttitel": "Beautiful Family Home",
"objektart": "House",
"vermarktungsart": "Sale",
"kaufpreis": 350000,
"ort": "Berlin",
"plz": "10115"
}
If no results are found or the response cannot be parsed, the output will contain a success message indicating no results.
The node does not output binary data.
Dependencies
- Requires an active connection to the onOffice API using valid API credentials (an API token and secret).
- The node uses HMAC SHA256 signing for request authentication.
- Network access to
https://api.onoffice.de/api/stable/api.phpis required. - Proper configuration of the API credentials within n8n is necessary before use.
Troubleshooting
- No credentials provided: The node will throw an error if API credentials are missing. Ensure you have configured the required API authentication token and secret in n8n.
- Invalid resource or operation: If the resource or operation parameters are incorrect, the node will report an invalid combination error.
- API errors: If the onOffice API returns an error status code, the node surfaces the API error message. Check the API token validity, permissions, and request parameters.
- No results found: If the estate ID does not exist or no matching records are found, the node outputs a message indicating no results.
- Malformed response: If the API response format changes or is unexpected, parsing may fail. Verify API stability and update the node if needed.
- Continue on Fail: If enabled, the node continues processing subsequent items even if some fail, returning error details in the output.