OnOffice Estate

Work with OnOffice estate/property records

Actions4

Overview

This node integrates with the OnOffice real estate API to manage estate/property records. It supports operations such as finding a single estate, finding multiple estates with filters, creating new estates, and updating existing ones.

The Create operation allows users to add new estate records by specifying various property details. This is useful for real estate agencies or property managers who want to automate adding new listings into their OnOffice system directly from n8n workflows.

Practical examples:

  • Automatically create a new property listing when a form is submitted on a website.
  • Add new estates in bulk from an external data source.
  • Integrate with CRM systems to sync new properties.

Properties

Name Meaning
Fields to Include Choose which fields to include in the creation operation. Options: Title, Property Type, Marketing Type, Purchase Price, Cold Rent, Living Space, Number of Rooms, Postal Code, City, Street, House Number, Description, Status
Title The title/name of the estate (string).
Property Type Type of property. Options: House, Apartment, Land, Commercial
Marketing Type Marketing type of the property. Options: For Sale, For Rent
Purchase Price Numeric value representing the purchase price of the property
Cold Rent Numeric value representing the cold rent amount
Living Space Numeric value indicating the living space area in square meters
Number of Rooms Numeric count of rooms in the property
Postal Code Postal code of the property's location (string)
City City where the property is located (string)
Street Street name of the property address (string)
House Number House number of the property address (string)
Description Detailed description of the property (multi-line string)
Status Status of the property. Options: Active, Inactive

Output

The output JSON contains the result of the create operation with the following structure:

  • success: Boolean indicating if the operation was successful.
  • operation: The operation performed, here it will be "create".
  • data: An object containing the created estate record's data returned by the API.
  • message: Optional message from the API response, typically confirming success.

Example output JSON:

{
  "success": true,
  "operation": "create",
  "data": {
    /* Created estate record fields */
  },
  "message": "Estate created successfully"
}

No binary data output is produced by this node.

Dependencies

  • Requires an API token credential for authenticating with the OnOffice API.
  • Uses the OnOffice REST API endpoint at https://api.onoffice.de/api/latest/api.php.
  • Requires network access to the OnOffice API service.
  • No additional environment variables are needed beyond the API credentials configured in n8n.

Troubleshooting

  • Common issues:

    • Missing required fields in the input can cause API errors.
    • Invalid API credentials will result in authentication failures.
    • Network connectivity problems may cause request timeouts or failures.

  • Error messages:

    • "OnOffice API action error: <message>" indicates the API returned an error related to the request parameters or data.
    • "OnOffice API error: <message>" indicates a more general API failure, possibly due to authentication or server issues.

  • Resolutions:

    • Verify all required fields are included and correctly formatted.
    • Check that the API token and secret are valid and have necessary permissions.
    • Ensure stable internet connection and that the OnOffice API endpoint is reachable.
    • Use the node's "Continue On Fail" option to handle errors gracefully in workflows.

Links and References

Discussion