OnOffice Task

Work with OnOffice CRM tasks

Overview

This node allows users to create tasks within the OnOffice CRM system. It is designed to facilitate task management by enabling the creation of new tasks with various attributes such as subject, responsible user, status, due date, priority, and associations with addresses or estates.

Common scenarios where this node is beneficial include:

  • Automating task creation based on external triggers or workflows.
  • Integrating OnOffice task management into broader business processes.
  • Assigning tasks dynamically to users or linking them to specific properties or addresses.

For example, a real estate agency could use this node to automatically create follow-up tasks for agents when a new property inquiry is received, setting appropriate priorities and due dates.

Properties

Name Meaning
Subject Subject/title of the task (Betreff). This is a required field describing the task briefly.
Address ID ID of the address to associate with this task.
Responsible User ID or username of the user responsible for this task.
Status Status of the task. Options: Open, In Progress, Completed, Cancelled.
Due Date Due date for the task completion (date and time).
Priority Priority level of the task. Options: Low, Medium, High.
Description Detailed description of the task.
Estate ID ID of the estate/property to associate with this task.
Include Debug Info Whether to include debug information in the output (boolean). Defaults to true.

Output

The node outputs JSON data representing the result of the task creation request. The structure includes:

  • success: Boolean indicating if the task was created successfully.
  • resourceType: Always "task" for this node.
  • operation: The operation performed, here "create".
  • data: Contains the detailed response data from OnOffice API about the created task, including its records.
  • taskId: The unique identifier of the newly created task (if creation succeeded).
  • error: Error message string if the creation failed.
  • If debug info is enabled, additional fields are included:
    • debug: true
    • rawResponse: Raw API response object.
    • requestSent: The full request payload sent to the API.
    • url: The API endpoint URL used.
    • requestedFields: The input fields provided for task creation.

The node does not output binary data.

Dependencies

  • Requires an API token credential and secret for authenticating with the OnOffice API.
  • Uses the OnOffice stable API endpoint at https://api.onoffice.de/api/stable/api.php.
  • The node internally generates HMAC signatures for secure API requests.
  • Requires proper configuration of the API credentials in n8n before use.

Troubleshooting

  • Common issues:
    • Invalid or missing API credentials will cause authentication failures.
    • Providing invalid IDs for address, estate, or responsible user may result in errors or unsuccessful task creation.
    • Incorrect date formats for the due date might cause API rejections.
  • Error messages:
    • Errors returned from the API are surfaced in the error field of the output JSON.
    • Common error messages include authentication errors, validation errors for missing required fields, or unknown errors if the API response is unexpected.
  • Resolution tips:
    • Verify that the API token and secret are correctly set up in n8n credentials.
    • Ensure all required fields, especially the subject, are provided.
    • Check that optional IDs correspond to valid entities in the OnOffice system.
    • Enable debug info to get detailed request and response data for troubleshooting.

Links and References

Discussion