Actions10
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 want to programmatically update property listings such as changing prices, updating descriptions, or modifying location details.
Practical examples include:
- Updating the price or rent of a property when market conditions change.
- Correcting or adding address information for an estate.
- Changing the marketing type from "For Sale" to "For Rent" or vice versa.
Properties
| Name | Meaning |
|---|---|
| Estate ID | The unique identifier of the estate to update. |
| Fields | A collection of fields representing the estate's attributes to update: |
| - Estate Title | Title or name of the estate. |
| - Estate Type | Type of the estate; options are: Apartment, House, Commercial, Land. |
| - Marketing Type | Whether the estate is listed For Sale or For Rent. Options: For Sale, For Rent. |
| - Price | Sale price of the estate (used if marketing type is For Sale). |
| - Cold Rent | Cold rent price (used if marketing type is For Rent). |
| - Warm Rent | Warm rent price including utilities (used if marketing type is For Rent). |
| - Living Space (m²) | Living area size in square meters. |
| - Land Area (m²) | Land area size in square meters. |
| - City | City where the estate is located. |
| - Postal Code | Postal code of the estate's location. |
| - Street | Street name of the estate's address. |
| - Street Number | Street number of the estate's address. |
| - Location Description | Additional description of the estate's location. |
| - External Object Number | External reference number for the estate, useful for cross-referencing systems. |
Output
The node outputs JSON data representing the updated estate record(s) returned by the onOffice API. The structure typically includes all requested estate fields such as IDs, pricing, location, and descriptive information.
If the update is successful, the output contains the updated estate data under json. If there is an error, the output will contain an error field describing the issue.
The node does not output binary data.
Dependencies
- Requires an active connection to the onOffice API using valid credentials (an API token and secret).
- The node uses HMAC SHA256 signing for request authentication.
- Requires network access to
https://api.onoffice.de/api/stable/api.php. - Must be configured with appropriate API credentials in n8n before use.
Troubleshooting
- No credentials provided: The node will throw an error if API credentials are missing. Ensure you have set up the required API key and secret in n8n credentials.
- Invalid resource or operation: If the resource or operation parameters are incorrect, the node will error out. Verify that "Estate" and "Update" are selected correctly.
- API Error with status code: If the onOffice API returns an error status, the node surfaces this message. Common causes include invalid estate IDs, malformed requests, or permission issues.
- Empty or missing response data: If no records are returned after update, check that the estate ID exists and the fields are valid.
- Continue On Fail: If enabled, the node will continue processing other items even if one fails, outputting error details per item.
Links and References
- onOffice API Documentation (official API docs for detailed endpoint info)
- n8n Documentation (for general usage of custom nodes and credentials setup)