onOffice

Consume onOffice API

Actions10

Overview

This node integrates with the onOffice API to retrieve data related to real estate and contacts. Specifically, for the Address - Get operation, it fetches detailed information about a single address/contact by its unique ID. This is useful in scenarios where you need to pull contact details such as name, phone number, email, and address fields from the onOffice system into your workflow.

Practical examples include:

  • Automatically retrieving client contact details when processing a real estate transaction.
  • Enriching CRM records with up-to-date address information stored in onOffice.
  • Triggering follow-up actions based on specific contact data fetched dynamically.

Properties

Name Meaning
Address ID The unique identifier of the address/contact to retrieve. This is required to specify which contact's data to fetch.

Output

The node outputs JSON data representing the requested address/contact record. The structure includes fields such as:

  • KdNr (Customer Number)
  • Anrede (Salutation)
  • Vorname (First Name)
  • Name (Last Name)
  • Telefon1 (Phone Number)
  • Email
  • Strasse (Street)
  • Plz (Postal Code)
  • Ort (City)
  • Land (Country)
  • Benutzer (User)

If multiple records were returned (though for "get" only one is expected), each will be output as a separate item. If an error occurs, the output will contain an error message in the JSON.

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.
  • The API authentication uses HMAC SHA256 signatures generated from the API token, secret, timestamp, and request parameters.

Troubleshooting

  • No credentials provided: The node will throw an error if the required API credentials are missing. Ensure you have configured the API key and secret correctly in n8n.
  • Invalid resource or operation: If the resource or operation parameters are incorrect, the node will error out. Verify that "Address" resource and "Get" operation are selected properly.
  • API Error with status code: If the API returns an error status, the node surfaces the message. Common causes include invalid address IDs or expired credentials.
  • Empty results: If no matching address is found, the output may be empty or contain the raw API response. Double-check the provided Address ID.
  • Continue On Fail: If enabled, the node will continue processing subsequent items even if some fail, outputting error messages per failed item.

Links and References

Discussion