Actions15
Overview
This node integrates with the OnOffice API to manage various real estate-related resources, including tasks. Specifically, for the Task - Create operation, it allows users to create new tasks within the OnOffice system. This is useful for automating task creation related to real estate contacts or activities, such as scheduling follow-ups, assigning responsibilities, or tracking actions.
Typical scenarios include:
- Automatically creating a task when a new lead is added.
- Assigning a task to a user responsible for a particular contact.
- Linking tasks to specific contacts (addresses) for better context and follow-up.
Example: Creating a task with a subject "Call client", a detailed description, assigning it to a responsible user, and linking it to a related contact by their address ID.
Properties
| Name | Meaning |
|---|---|
| Subject | The title or main subject of the task. |
| Task Description | A detailed description or notes about the task. |
| Responsible User | The user assigned responsibility for completing the task. |
| Related Address ID | The ID of the related address (contact) associated with this task, providing context. |
Output
The node outputs JSON data representing the result of the task creation request. The structure includes:
success: Boolean indicating if the operation was successful.resourceType: The resource type, here always"task".operation: The operation performed, here"create".data: An object containing details of the created task as returned by the OnOffice API.message: Optional message from the API response, typically confirming success.rawResponse: The full raw API response for debugging purposes (included in debug mode).
If an error occurs, the output will contain error details including the error message and any API error response.
The node does not output binary data.
Dependencies
- Requires an API token credential and API secret for authenticating with the OnOffice API.
- The node sends HTTP POST requests to the OnOffice API endpoint at
https://api.onoffice.de/api/latest/api.php. - HMAC signature generation is used for request authentication.
- Proper configuration of the OnOffice API credentials in n8n is necessary.
Troubleshooting
- Invalid JSON Data: If the "Data" property contains invalid JSON, the node throws an error stating "Data must be a valid JSON". Ensure the JSON syntax is correct.
- API Request Failed: Network issues or incorrect credentials can cause API request failures. Check API token and secret validity and network connectivity.
- Unsupported Resource or Operation: Errors occur if an unsupported resource or operation is selected. Verify that "Task" resource and "Create" operation are chosen.
- API Action Error: If the API returns an error code, the node surfaces the error message. Review the message for details and adjust input parameters accordingly.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, outputting error details instead of stopping execution.
Links and References
- OnOffice API Documentation (general reference for API capabilities)
- n8n documentation on Creating Custom Nodes
- HMAC Authentication concepts: HMAC Wikipedia
If you need further details on other operations or resources, feel free to ask!