i-doit icon

i-doit

i-doit JSON-RPC API

Actions7

Create

AI-generated

Overview

This node allows you to create new records in the i-doit CMDB (Configuration Management Database) system via its JSON-RPC API. Specifically, with the Resource: Default and Operation: Create, it supports creating either a new CMDB Object or a new Category entry for an existing object. This is useful for automating asset management, infrastructure documentation, or integrating i-doit with other ITSM/CMDB workflows.

Practical examples:

  • Automatically add new servers or network devices to your CMDB when they are provisioned.
  • Add category data (like location, hardware details, or custom attributes) to existing objects as part of an onboarding workflow.

Properties

Name Type Meaning
Namespace options Selects which i-doit API namespace to use. For creation, typically "CMDB Object" or "CMDB Category".
Category options The specific category within the selected namespace. Only shown for relevant namespaces.
Object Type options The type of object to create (e.g., Server, Switch). Only for "CMDB Object" namespace.
Id string The ID of the object to which a category entry will be added. Required for "CMDB Category".
Title string The title/name of the object to create. Required for "CMDB Object".
Property string Attribute in the category. Only relevant for "CMDB Dialog" (not used in this operation).
Values to Set fixedCollection Key-value pairs representing category attributes and their values. Used for "CMDB Category".
Retrieve and Split Data Items boolean Not used in "Create" operation; relevant for read/search operations.

Output

  • The output is a json field containing the response from the i-doit API after attempting to create the object or category entry.
  • The structure of the json output depends on the i-doit API's response for the respective creation method:
    • For CMDB Object: Contains details about the newly created object (such as its ID, title, and status).
    • For CMDB Category: Contains details about the created category entry.
  • If an error occurs and "Continue On Fail" is enabled, the output will include a field like { "error": "<error message>" }.

Note: No binary data is produced by this operation.

Dependencies

  • i-doit instance: You must have access to an i-doit server with the JSON-RPC API enabled.
  • API Key: The node requires valid i-doit credentials (API key) configured in n8n under the "idoit" credential type.

Troubleshooting

Common issues:

  • Invalid API Key: If the API key is missing or incorrect, the node will return an authentication error from i-doit.
  • Missing Required Fields: If required fields (like "Title" for objects or "Id" for categories) are not provided, the node will throw an error indicating missing parameters.
  • Category/Object Type Mismatch: Selecting an invalid combination of category and object type may result in errors from the i-doit API.
  • Network Issues: Connectivity problems between n8n and the i-doit server will cause request failures.

Error messages:

  • "error": "Missing parameter ..." – Ensure all required properties are filled.
  • "error": "Authentication failed" – Check your API key and i-doit server URL.
  • "error": "Object type/category not found" – Verify that the selected types/categories exist in your i-doit instance.

Links and References

Discussion