Overview
This node integrates with the onOffice API to manage real estate data. Specifically, for the Estate - Create operation, it allows users to create new estate entries by sending structured JSON data representing the estate details to the onOffice system.
Common scenarios where this node is beneficial include:
- Automating the addition of new real estate listings from external sources or forms.
- Integrating property management systems with onOffice to keep estate data synchronized.
- Bulk importing estate data into onOffice via workflows.
For example, a user could use this node to create a new estate record by providing all relevant property details (like address, price, features) in JSON format, which the node then sends to onOffice to register the estate.
Properties
| Name | Meaning |
|---|---|
| Data | The estate data to create, provided as a JSON string. This should contain all necessary fields describing the estate according to onOffice's expected schema. |
Output
The node outputs the response from the onOffice API after attempting to create the estate. The output is a JSON object containing the API's response data, which typically includes confirmation of creation and any identifiers assigned to the new estate.
If multiple estates were created (in batch scenarios), the output would be an array of such JSON objects. However, for the single create operation, it is a single JSON object.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the onOffice API.
- Needs an API authentication credential configured in n8n to authorize requests.
- The node uses POST requests to the
/api.phpendpoint of onOffice. - The input estate data must be valid JSON matching onOffice's expected structure.
Troubleshooting
- Invalid JSON in Data Property: If the JSON string provided in the "Data" property is malformed, the node will throw a parsing error. Ensure the JSON is correctly formatted.
- API Authentication Errors: If the API key or credentials are missing or invalid, the node will fail to authenticate. Verify that the onOffice API credential is properly set up in n8n.
- Missing Required Fields: If the estate data lacks required fields expected by onOffice, the API may return validation errors. Check the onOffice API documentation for required estate fields.
- Network Issues: Connectivity problems to the onOffice API endpoint will cause request failures. Confirm network access and endpoint availability.
Links and References
- onOffice API Documentation (general reference for API usage)
- n8n Documentation on Creating Custom Nodes
- JSON formatting tools to validate your estate data before inputting it into the node.