OnOffice

Consume OnOffice API

Actions12

Estate → Create

AI-generated

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 new estate records by sending structured JSON data representing the estate details to the OnOffice platform.

Common scenarios where this node is beneficial include:

  • Automating the addition of new real estate listings into the OnOffice system from other applications or workflows.
  • Integrating property management systems with OnOffice to keep estate data synchronized.
  • Bulk importing estate data by looping over multiple inputs and creating estates programmatically.

Example use case: A real estate agency uses this node in an n8n workflow to automatically add new properties submitted via a web form into their OnOffice account, ensuring all listings are up-to-date without manual entry.

Properties

Name Meaning
Data JSON object containing the details of the estate to create. This should be a valid JSON string representing the estate's attributes as expected by the OnOffice API.

Output

The node outputs a JSON object with the following structure:

  • success: Boolean indicating if the creation was successful (true).
  • resourceType: The resource type, here always "estate".
  • operation: The operation performed, here "create".
  • data: The response data from the OnOffice API about the created estate.
  • message: A status message returned by the API confirming the creation.

The output is wrapped in an array format compatible with n8n's execution metadata system.

No binary data output is produced by this operation.

Dependencies

  • Requires an API token and secret for authenticating with the OnOffice API.
  • The node expects these credentials to be configured in n8n under a generic API authentication credential (referred to internally but not named here).
  • Network access to https://api.onoffice.de/api/v1 is required.
  • Uses HMAC signature generation for request authentication.

Troubleshooting

  • Invalid JSON in Data Property: If the "Data" input is not valid 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 is missing or incorrect, requests will fail. Verify that the API credentials are correctly set up in n8n.
  • OnOffice API Errors: The node surfaces errors returned by the OnOffice API with messages like "OnOffice API error: ". Check the API documentation or your data payload for issues.
  • Network Issues: Errors such as "Network error: " indicate connectivity problems. Confirm network access and proxy settings if applicable.
  • Unsupported Resource or Operation: If the node configuration specifies unsupported resources or operations, it throws descriptive errors. Double-check the selected resource and operation.

Links and References

Discussion