Overview
This node interacts with the onOffice API to manage address data. Specifically, for the Address - Delete operation, it deletes an existing address record identified by its unique ID. This is useful in scenarios where you need to programmatically remove outdated or incorrect address entries from your onOffice database.
Practical examples include:
- Cleaning up contact lists by removing obsolete addresses.
- Automating address management workflows where addresses are deleted based on certain triggers or conditions.
Properties
| Name | Meaning |
|---|---|
| Address ID | The unique identifier of the address to delete. This is a required string input. |
Output
The output JSON contains the response from the onOffice API after attempting to delete the specified address. Typically, this will confirm whether the deletion was successful or provide error details if it failed.
The node does not output binary data.
Example output structure (simplified):
{
"actionid": "urn:onoffice-de-ns:smart:2.5:smartml:action:delete",
"resourceid": "address-id-used",
"identifier": "",
"resourcetype": "address",
"parameters": {}
}
Dependencies
- Requires an active connection to the onOffice API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node sends POST requests to the
/api.phpendpoint of the onOffice API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Address ID will likely result in an error or no action.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems can prevent the node from reaching the onOffice API.
Error messages and resolutions:
- "Address not found" — Verify that the Address ID is correct and exists in onOffice.
- Authentication errors — Check that the API key or token is valid and properly configured in n8n.
- Timeout or network errors — Ensure stable internet connection and that the onOffice API endpoint is reachable.
Links and References
- onOffice API Documentation (general reference for API actions)
- n8n documentation on creating custom nodes