Actions14
Overview
This node integrates with the onOffice API to manage real estate data. Specifically, the "Estate" resource with the "Update" operation allows users to modify details of an existing estate record in the onOffice system. This is useful for real estate agents or property managers who need to keep their listings up-to-date with changes such as price adjustments, location updates, or other property attributes.
Practical examples include:
- Updating the price of a property when market conditions change.
- Modifying the description or address details after renovations or corrections.
- Changing the marketing type from "For Sale" to "For Rent" or vice versa.
Properties
| Name | Meaning |
|---|---|
| Estate Title | Title or name of the estate (string). |
| Estate Type | Type of the estate; options: Apartment, House, Commercial, Land. |
| Marketing Type | Whether the estate is for sale or rent; options: For Sale, For Rent. |
| Price | Price of the estate if it is for sale (number, minimum 0). |
| Cold Rent | Cold rent price if the estate is for rent (number, minimum 0). |
| Warm Rent | Warm rent price if the estate is for rent (number, minimum 0). |
| Living Space (m²) | Living space area in square meters (number, minimum 0). |
| Land Area (m²) | Land area in square meters (number, minimum 0). |
| City | City where the estate is located (string). |
| Postal Code | Postal code of the estate (string). |
| Street | Street name of the estate (string). |
| Street Number | Street number of the estate (string). |
| Location Description | Description of the location (string). |
| External Object Number | External reference number of the estate (string). |
These fields are grouped under "Fields" → "Estate Fields" and can be updated in one request.
Output
The node outputs JSON data representing the updated estate records returned by the onOffice API. The output includes:
- The updated estate properties as key-value pairs.
- A
resourceTypefield indicating the resource type ("estate"). - In case of no results or parsing issues, a message indicating no results found.
- On errors, an error message and raw request details may be included if "Continue On Fail" is enabled.
No binary data output is involved.
Dependencies
- Requires an API authentication token and secret configured via credentials in n8n.
- Communicates with the onOffice API endpoint at
https://api.onoffice.de/api/stable/api.php. - Uses HMAC SHA256 signing for request authentication.
Troubleshooting
- Missing Credentials: The node will throw an error if API credentials are not provided.
- Invalid Resource or Operation: If the resource or operation parameters are incorrect, an error is thrown.
- API Errors: If the onOffice API returns an error status code, the node throws an error with the API message.
- Parsing Issues: If the response cannot be parsed properly, the node outputs a success message but indicates no results found.
- Required Parameters: For update operations, ensure the estate ID and fields to update are correctly specified.
- Network Issues: Connectivity problems with the onOffice API endpoint will cause request failures.
To resolve errors:
- Verify API credentials and permissions.
- Confirm that the estate ID exists and is correct.
- Check the field names and values conform to expected types and constraints.
- Enable "Continue On Fail" to handle partial failures gracefully.
Links and References
- onOffice API Documentation (general reference for API usage)
- HMAC SHA256 Algorithm (for understanding request signing)