OnOffice Estate

Work with OnOffice estate/property records

Actions4

Overview

The node "OnOffice Estate" allows users to interact with OnOffice's real estate/property records via their API. Specifically, the Update operation lets you modify an existing estate record by specifying its ID and updating selected fields.

This node is useful in scenarios where you need to programmatically update property details such as title, price, location, or status within an automated workflow. For example, you could update the purchase price or status of a property after receiving new information from another system or user input.

Properties

Name Meaning
Estate ID The unique identifier of the estate record to update.
Fields to Include Select which fields you want to update on the estate. Options include: Title, Property Type, Marketing Type, Purchase Price, Cold Rent, Living Space, Number of Rooms, Postal Code, City, Street, House Number, Description, Status.
Load Values from Previous Node Boolean flag indicating whether to load field values from a previous Find operation's output before applying updates.
Title The title/name of the estate (string).
Property Type The type of property. Options: House, Apartment, Land, Commercial.
Marketing Type The marketing type. Options: For Sale, For Rent.
Purchase Price Numeric value representing the purchase price.
Cold Rent Numeric value representing the cold rent amount.
Living Space Numeric value for the living space area.
Number of Rooms Numeric count of rooms in the property.
Postal Code Postal code string of the property's location.
City City name string.
Street Street name string.
House Number House number string.
Description Text description of the estate.
Status Status of the estate. Options: Active, Inactive.

Output

The node outputs JSON data containing the result of the update operation. The structure includes:

  • success: Boolean indicating if the update was successful.
  • operation: The operation performed ("update").
  • data: The updated estate data returned from the API.
  • message: Optional message from the API about the update status.

Example output JSON:

{
  "success": true,
  "operation": "update",
  "data": {
    /* Updated estate fields */
  },
  "message": "Update successful"
}

No binary data output is produced by this node.

Dependencies

  • Requires an API token and secret credential for authenticating with the OnOffice API.
  • The node makes HTTP POST requests to the OnOffice API endpoint at https://api.onoffice.de/api/latest/api.php.
  • Proper configuration of the API credentials in n8n is necessary for successful communication.

Troubleshooting

  • Common issues:

    • Invalid or missing estate ID will cause the update to fail.
    • Incorrect or expired API credentials will result in authentication errors.
    • Attempting to update fields not included in "Fields to Include" will have no effect.
    • Network connectivity problems can cause request failures.

  • Error messages:

    • "OnOffice API action error: <message>" indicates an error response from the API, often due to invalid parameters or permissions.
    • "OnOffice API error: <message>" indicates a more general API failure.

  • Resolutions:

    • Verify that the estate ID exists and is correct.
    • Check that API credentials are valid and have required permissions.
    • Ensure all required fields are included and properly formatted.
    • Use the "Load Values from Previous Node" option carefully to avoid overwriting unintended fields.

Links and References

Discussion