Actions14
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.
Common scenarios where this node is beneficial include:
- Real estate agencies automating the addition of new property listings from external sources or internal systems.
- Synchronizing property databases by programmatically adding estates without manual entry.
- Integrations where new estate data needs to be pushed into onOffice as part of a workflow.
For example, a user can configure this node to create a new apartment listing with details such as title, type, price, location, and size, which then becomes available in their onOffice account.
Properties
| Name | Meaning |
|---|---|
| Estate Title | Title of the estate |
| 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 (numeric, minimum 0) |
| Cold Rent | Cold rent price if the estate is for rent (numeric, minimum 0) |
| Warm Rent | Warm rent price if the estate is for rent (numeric, minimum 0) |
| Living Space (m²) | Living space area in square meters (numeric, minimum 0) |
| Land Area (m²) | Land area in square meters (numeric, minimum 0) |
| City | City where the estate is located |
| Postal Code | Postal code of the estate |
| Street | Street name of the estate |
| Street Number | Street number of the estate |
| Location Description | Description of the location |
| External Object Number | External reference number of the estate |
These fields are grouped under "Fields" → "Estate Fields" in the node's UI.
Output
The node outputs JSON objects representing the created estate records returned by the onOffice API. Each output item contains:
- The full response data from the API about the created estate.
- A
resourceTypefield set to"estate"indicating the type of resource. - If the API returns an error, the output will contain an error message and raw request details.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the onOffice API.
- The node uses HMAC SHA256 signing for requests, requiring both an API token and secret.
- HTTP POST requests are made to
https://api.onoffice.de/api/stable/api.php. - Proper configuration of the API credentials within n8n is necessary.
Troubleshooting
- Missing Credentials: The node throws an error if no API credentials are provided. Ensure that a valid API key and secret are configured.
- Invalid Resource or Operation: Errors occur if unsupported resource-operation combinations are selected.
- API Errors: If the API responds with a non-200 status code, the node throws an error with the API message. Check the API token and permissions.
- Required Fields Missing: Although not explicitly checked for estate creation in the code snippet, ensure mandatory fields like "Estate Title" are provided to avoid API rejection.
- Parsing Response Failures: If the API response format changes or is unexpected, the node may return a success message with raw response but no parsed results.
To resolve errors, verify credentials, input parameters, and consult the onOffice API documentation for correct usage.
Links and References
- onOffice API Documentation (general reference for API capabilities)
- n8n Documentation for configuring credentials and using custom nodes