Overview
This node interacts with OnOffice address records, allowing users to find, create, update, or retrieve multiple addresses via the OnOffice API. It is useful for automating workflows that involve managing contact information within the OnOffice system, such as syncing address data, updating customer details, or bulk querying addresses based on filters.
For the Update operation specifically, the node updates an existing address record identified by its ID. Users can selectively update specific fields of the address, either by manually providing new values or by loading values from a previous Find operation in the workflow. This operation is beneficial when you need to keep address data current without overwriting all fields, for example, updating only the phone number or email of a contact.
Practical Example
- Automatically update a customer's address details after receiving updated information from a form submission.
- Sync changes made in another CRM system back into OnOffice by updating only changed fields.
- Batch update multiple addresses by chaining Find and Update operations in a workflow.
Properties
| Name | Meaning |
|---|---|
| Address ID | The unique identifier of the address record to update. |
| Fields to Include | Select which fields of the address should be updated. Options: Form of Address, First Name, Last Name, Email, Phone 1, Street, Postal Code, City, Country. |
| Load Values from Previous Node | Boolean flag indicating whether to load field values from a previous Find operation's output before applying updates. |
| Form of Address | The salutation or form of address (Mr, Mrs, Company). |
| First Name | The first name of the contact. |
| Last Name | The last name of the contact. |
| The email address of the contact. | |
| Phone 1 | Primary phone number. |
| Street | Street address. |
| Postal Code | Postal or ZIP code. |
| City | City name. |
| Country | Country name (default is "Deutschland"). |
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 performed operation name ("update").data: The updated address data returned by the API.message: Optional message from the API about the operation status.
If the update fails, the output will contain:
success: falseerror: Error message describing what went wrong.
No binary data output is involved in this node.
Dependencies
- Requires an active connection to the OnOffice API using valid API credentials (an API token and secret).
- The node uses HTTP POST requests to communicate with the OnOffice API endpoint at
https://api.onoffice.de/api/latest/api.php. - Proper configuration of the API credentials in n8n is necessary for authentication and authorization.
Troubleshooting
Common Issues:
- Invalid or missing Address ID: The update operation requires a valid address ID; ensure it is correctly provided.
- Missing required fields: If no fields are selected to include in the update, the operation cannot proceed.
- API authentication errors: Incorrect or expired API tokens/credentials will cause failures.
- Network or connectivity issues to the OnOffice API endpoint.
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, possibly network-related or server-side.
Resolutions:
- Verify the Address ID exists and is correct.
- Ensure at least one field is selected to update.
- Check and refresh API credentials if authentication errors occur.
- Confirm network access to the OnOffice API endpoint.
Links and References
- OnOffice API Documentation (general reference for API capabilities)
- n8n documentation on HTTP Request node for understanding underlying HTTP calls (not directly used but conceptually related)