Actions12
Overview
This node integrates with the OnOffice API to manage real estate-related data. Specifically, for the Estate - Create operation, it allows users to create a new estate record in the OnOffice system by providing the estate data in JSON format.
Common scenarios where this node is beneficial include:
- Automating the addition of new estate listings from external sources or forms.
- Integrating property management systems with OnOffice to keep estate data synchronized.
- Bulk creation of estates by feeding multiple JSON objects representing different properties.
Example use case: A real estate agency collects property details via a web form and uses this node to automatically create corresponding estate records in their OnOffice database.
Properties
| Name | Meaning |
|---|---|
| Data | JSON object containing the details of the estate to create. This should conform to the expected schema of the OnOffice API for an estate resource. |
Output
The node outputs a JSON object with the following structure:
success: Boolean indicating if the creation was successful (true).resourceType: The string"estate".operation: The string"create".data: The response data from the OnOffice API representing the created estate record.message: A status message returned by the API confirming the creation.
The output is wrapped as an array of such JSON objects, one per input item processed.
No binary data output is produced by this node.
Dependencies
- Requires valid credentials for the OnOffice API, specifically an API token and secret.
- The node makes HTTP POST requests to the OnOffice API endpoint at
https://api.onoffice.de/api/v1. - HMAC signature generation is used for request authentication.
- The user must provide correctly formatted JSON data for the estate to be created.
Troubleshooting
- Invalid JSON in Data Property: If the "Data" field contains invalid JSON, the node will throw an error stating "Data must be a valid JSON". Ensure the JSON syntax is correct before running.
- API Authentication Errors: If the API token or secret are incorrect or missing, the node will fail with an authentication error. Verify that the API credentials are properly configured.
- OnOffice API Errors: Any errors returned by the OnOffice API (e.g., validation errors on the estate data) will be surfaced with messages prefixed by "OnOffice API error:". Review the message for details and adjust the input data accordingly.
- Network Issues: Network connectivity problems will result in errors starting with "Network error:". Check your internet connection and firewall settings.
- Unsupported Resource or Operation: If the node is misconfigured with unsupported resource or operation values, it will throw descriptive errors indicating the unsupported combination.
Links and References
- OnOffice API Documentation (official API docs for reference on estate data schema and endpoints)
- n8n documentation on HTTP Request Node for understanding underlying HTTP calls
- General JSON formatting guides to help prepare the "Data" input property correctly