i-doit icon

i-doit

i-doit JSON-RPC API

Actions7

Update

AI-generated

Overview

The i-doit n8n node allows you to interact with the i-doit CMDB (Configuration Management Database) system via its JSON-RPC API.
For the Resource: Default and Operation: Update, this node is used to update existing objects or categories within the i-doit CMDB.

Typical use cases include:

  • Updating the title of an existing CMDB object (e.g., renaming a server).
  • Modifying attributes of a specific category for a given object (e.g., updating network details, hardware specs, etc.).

Practical Example:
Suppose you have a workflow that detects changes in your infrastructure inventory. You can use this node to automatically update the corresponding object or category in i-doit when a change is detected.

Properties

Name Type Meaning
Namespace options Selects the type of resource to operate on (e.g., CMDB Object, CMDB Category).
Category options Specifies the category to update (required for "CMDB Category" namespace).
Object Type options The type of object (e.g., Server, Switch); relevant for some namespaces but not required here.
Id string The unique identifier of the object or resource to update.
Title string The new title for the object (used when updating a CMDB Object).
Property string Attribute in the category (not used for update in these namespaces).
Values to Set fixedCollection Key-value pairs specifying which attributes to update in the selected category.

Output

  • The output is always in the json field.
  • For successful updates, the output contains the response from the i-doit API, typically including status information and possibly the updated object/category data.
  • If an error occurs and "Continue On Fail" is enabled, the output will contain an error property with the error message.

Example output (success):

{
  "result": {
    "id": "1234",
    "title": "Updated Server Name",
    ...
  }
}

Example output (error, if continue on fail):

{
  "error": "Error message from i-doit API"
}

Dependencies

  • External Service: Requires access to an i-doit instance with the JSON-RPC API enabled.
  • API Key: You must provide valid i-doit credentials (API key) via n8n's credential system.
  • n8n Configuration: No special configuration beyond setting up the credentials.

Troubleshooting

Common Issues:

  • Invalid ID: If the provided "Id" does not exist, the API will return an error.
  • Missing Required Fields: Not providing required fields like "Id", "Title" (for object), or "Values to Set" (for category) will result in errors.
  • Permission Denied: If the API key lacks sufficient permissions, operations will fail.
  • Incorrect Namespace/Category: Selecting the wrong combination may cause the update to fail or have no effect.

Common Error Messages:

  • "Object not found": Check that the "Id" is correct and exists in i-doit.
  • "Missing required parameter": Ensure all required properties are filled.
  • "Permission denied": Verify the API key has the necessary rights.

Links and References

Discussion