onOffice

Consume onOffice API

Actions10

Overview

This node integrates with the onOffice API to retrieve address data. Specifically, the "Address - Get All" operation fetches multiple address records from the onOffice system, up to a specified limit.

Common scenarios for this node include:

  • Synchronizing contact or client address data from onOffice into other systems.
  • Bulk exporting address information for reporting or mailing purposes.
  • Automating workflows that require access to customer or contact addresses stored in onOffice.

For example, a user might configure this node to pull the latest 50 addresses and then use the data to update a CRM or send marketing emails.

Properties

Name Meaning
Limit Max number of address results to return (minimum 1). Defaults to 50.

Output

The node outputs an array of JSON objects, each representing an address record retrieved from onOffice. Each record contains 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 no records are found, the output will contain the raw API response.

No binary data is returned by this node.

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, resource, and action identifiers.

Troubleshooting

  • No credentials provided: The node will throw an error if the required API credentials are missing. Ensure you have configured valid onOffice API credentials in n8n.
  • Invalid resource or operation: If the resource or operation parameters are incorrect, the node throws an error indicating invalid input.
  • API errors: If the onOffice API returns an error status code, the node surfaces the message. Common causes include invalid tokens, expired credentials, or malformed requests.
  • Empty results: If no addresses match the query, the node outputs the raw API response which may be empty or contain metadata.
  • Limit parameter issues: Setting the limit below 1 may cause validation errors; ensure it is at least 1.

Links and References

Discussion