Actions10
Overview
This node integrates with the onOffice API to manage address data, specifically allowing creation of new address records. It is useful in scenarios where you want to automate adding contact information into the onOffice system, such as importing leads or syncing contacts from other sources.
For example, you can use this node to create a new contact with details like salutation, name, email, phone, and address fields directly in onOffice, streamlining your CRM workflows.
Properties
| Name | Meaning |
|---|---|
| Salutation | Salutation for the contact; options: Mr, Ms, Company |
| First Name | First name of the contact |
| Last Name | Last name of the contact |
| Email address of the contact | |
| Phone | Phone number of the contact |
| Street | Street name of the contact |
| Postal Code | Postal code of the contact |
| City | City where the contact is located |
| Country | Country where the contact is located (default: Deutschland) |
| User | User responsible for this contact |
These fields are grouped under "Fields" → "Address Fields" and are used to specify the details of the address/contact to be created.
Output
The node outputs JSON data representing the response from the onOffice API after attempting to create the address record. The output JSON typically contains status information and the created record's details if successful.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error message describing the failure.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential and secret token for authenticating with the onOffice API.
- The node makes HTTP POST requests to
https://api.onoffice.de/api/stable/api.php. - HMAC SHA256 signing is used to secure API requests, requiring both an API token and secret.
Troubleshooting
- Missing Credentials: If no API credentials are provided, the node throws an error indicating missing credentials.
- Invalid Resource or Operation: Errors occur if unsupported resource-operation combinations are selected.
- API Errors: If the onOffice API returns an error status, the node surfaces the API error message.
- Network Issues: Connectivity problems may cause HTTP request failures.
- To resolve errors, verify that valid API credentials are configured, the correct resource and operation are selected, and network connectivity to the onOffice API endpoint is available.
Links and References
- onOffice API Documentation (official API docs for further details)
- n8n Documentation (for general usage of custom nodes and credentials)