Actions10
Overview
This node integrates with the onOffice API to manage real estate data. Specifically, for the "Estate" resource and the "Create" operation, it allows users to create new estate entries in the onOffice system by providing detailed property information such as title, type, marketing type, pricing, location, and other relevant attributes.
Common scenarios where this node is beneficial include:
- Real estate agencies automating the addition of new property listings from external sources or internal databases.
- Property management systems syncing newly acquired estates into onOffice automatically.
- Bulk creation of estate records during data migration or integration workflows.
Example use case: Automatically creating a new apartment listing for sale with specified price, living space, and address details directly into onOffice when a new property is added to an internal CRM.
Properties
| Name | Meaning |
|---|---|
| Estate Title | Title 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" in the node's UI.
Output
The node outputs JSON data representing the response from the onOffice API after attempting to create the estate record. The structure typically includes:
status: An object containing status code and message indicating success or failure.response: Contains results with created estate data records.- Each output item corresponds to one input item processed, paired accordingly.
If the API returns multiple records, each is output as a separate item. In case of errors, the output JSON contains an error field with the error message.
The node does not output binary data.
Dependencies
- Requires an active connection to the onOffice API using valid credentials that include 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 execution.
Troubleshooting
- No credentials provided: The node will throw an error if API credentials are missing. Ensure you have configured the required API key and secret in n8n credentials.
- Invalid resource or operation: If the resource or operation parameters are incorrect or unsupported, the node throws an error. Verify that "Estate" and "Create" are selected correctly.
- API Error: If the onOffice API returns an error status, the node surfaces the message. Common causes include invalid data fields, missing required fields, or authentication issues.
- Network issues: Connectivity problems to the onOffice API endpoint can cause failures. Check network settings and firewall rules.
- Data validation: Ensure numeric fields like prices and areas are non-negative as per the property definitions.
Using the node's "Continue On Fail" option can help handle individual item errors gracefully in batch operations.