onOffice

Consume onOffice API

Actions10

Overview

This node integrates with the onOffice API to retrieve real estate data. Specifically, the "Estate - Get All" operation fetches a list of real estate properties from the onOffice system. It is useful for scenarios where you want to bulk import or synchronize property listings into your workflow, such as for real estate agencies managing multiple properties or platforms aggregating listings.

For example, you could use this node to:

  • Retrieve all available estates up to a specified limit.
  • Automate updates of property databases by regularly fetching current listings.
  • Filter and process estate data downstream in your n8n workflows.

Properties

Name Meaning
Limit Maximum number of estate records to return. Must be at least 1. Defaults to 50.

Output

The node outputs an array of JSON objects, each representing a single estate record retrieved from the onOffice API. Each record includes fields such as:

  • Id (property identifier)
  • kaufpreis (purchase price)
  • warmmiete (gross rent)
  • kaltmiete (net rent)
  • objektart (type of object)
  • objekttyp (object subtype)
  • vermarktungsart (marketing type)
  • wohnflaeche (living area)
  • nutzflaeche (usable area)
  • grundstuecksflaeche (plot area)
  • plz (postal code)
  • ort (city)
  • strasse (street)
  • hausnummer (house number)
  • objekttitel (title of the property)
  • objektnr_extern (external property number)
  • lage (location description)

If no records are found, the raw API response is returned instead.

The node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the onOffice API.
  • The node makes HTTP POST requests to https://api.onoffice.de/api/stable/api.php.
  • HMAC SHA256 signing is used for request authentication, requiring both an API token and secret.
  • Proper configuration of the onOffice API credentials within n8n is necessary.

Troubleshooting

  • No credentials provided: The node will throw an error if the required API credentials are missing. Ensure that valid onOffice API credentials are configured in n8n.
  • Invalid resource or operation: If the resource or operation parameters are incorrect, the node throws an error indicating invalid input. Verify that "Estate" is selected as the resource and "Get All" as the operation.
  • API Error: If the onOffice API returns an error status, the node surfaces the message. Common causes include expired tokens, insufficient permissions, or malformed requests. Check your API credentials and request parameters.
  • Empty results: If no estates are returned, verify that there are listings available in your onOffice account and that the limit parameter is set appropriately.

Links and References

Discussion