Actions12
Overview
This node integrates with the OnOffice API to manage real estate-related data, specifically estates, addresses, and relations. For the Address resource with the Create operation, it allows users to create a new address record in the OnOffice system by providing the necessary address data in JSON format.
Typical use cases include:
- Automating the addition of new contact addresses into a real estate management system.
- Integrating form submissions or CRM data to automatically create address entries.
- Synchronizing external address data sources with OnOffice.
Example: A user can input structured JSON data representing an address (e.g., name, street, city, email) and have this node create the corresponding address record in OnOffice without manual entry.
Properties
| Name | Meaning |
|---|---|
| Data | JSON object containing the details of the address to create. This should include all relevant fields as expected by the OnOffice API for an address record. Example fields might be id, name, vorname (first name), email, etc. The JSON must be valid. |
Output
The node outputs a JSON array where each item corresponds to an input item processed. For the Create Address operation, the output JSON structure includes:
success: Boolean indicating if the creation was successful.resourceType: The resource type, here"address".operation: The operation performed, here"create".data: The response data from the OnOffice API about the created address record.message: A status message returned by the API.
If the API call fails, the output will contain an error message describing the failure.
No binary data is output by this node.
Dependencies
- Requires an API token and secret credential for authenticating with the OnOffice API.
- The node makes HTTP POST requests to the OnOffice API endpoint at
https://api.onoffice.de/api/latest/api.php. - Proper configuration of the API credentials within n8n is necessary before using this node.
Troubleshooting
- Invalid JSON in Data property: If the JSON provided in the "Data" field is malformed, the node throws an error stating "Data must be a valid JSON". Ensure the JSON syntax is correct.
- API errors: Errors returned by the OnOffice API are surfaced with messages like "OnOffice API error: [message]". Check that the API token and secret are valid and have sufficient permissions.
- Network issues: Network connectivity problems result in errors like "Network error: [message]". Verify internet access and API endpoint availability.
- Unsupported operations or resources: If an unsupported resource or operation is selected, the node throws an error indicating the unsupported combination.
- Filter parsing errors: When using filters (not applicable for create but relevant for other operations), invalid JSON filters cause errors.
Links and References
- OnOffice API Documentation (official API docs for reference on data structure and endpoints)
- n8n documentation on Creating Custom Nodes (for understanding node development concepts)
If you need further details on other operations or resources, feel free to ask!