i-doit icon

i-doit

i-doit JSON-RPC API

Actions7

Delete

AI-generated

Overview

This n8n node integrates with the i-doit JSON-RPC API, specifically targeting the "Default" Resource and the "Delete" Operation. In this context, the node is used to mark records as deleted within the i-doit CMDB (Configuration Management Database). It supports deleting both objects and category entries, making it useful for automating cleanup or decommissioning tasks in IT asset management workflows.

Common scenarios:

  • Automatically removing decommissioned servers or devices from the CMDB.
  • Deleting specific category entries related to an object (e.g., network interfaces, software assignments).
  • Integrating with other automation tools to keep the CMDB up-to-date by removing obsolete data.

Practical example:
When a server is retired, this node can be triggered to delete its record from i-doit, ensuring the CMDB reflects the current state of your infrastructure.

Properties

Name Type Meaning
Namespace options Selects the API namespace; for deletion, typically "CMDB Object" or "CMDB Category".
Category options Specifies the category to target (required for "CMDB Category" deletions).
Object Type options Type of object (not required for delete operation).
Id string The unique identifier of the resource (object or category) to delete.
Category entry Id string Entry identifier within a category (required for "CMDB Category" deletions).
Search String string Not used for delete operation.
Retrieve and Split Data Items boolean Not used for delete operation.

Note:

  • For deleting a CMDB Object: only "Id" is required.
  • For deleting a CMDB Category entry: "Id", "Category", and "Category entry Id" are required.

Output

The node outputs a json field containing the response from the i-doit API after attempting the delete operation. The structure of this output depends on the i-doit API's response, but typically includes status information about the deletion request.

Example output:

{
  "result": {
    // Details about the deleted object or category entry
  },
  "id": 1,
  "jsonrpc": "2.0"
}

If an error occurs and "Continue On Fail" is enabled, the output will include:

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

Dependencies

  • i-doit API: Requires access to an i-doit instance with JSON-RPC enabled.
  • API Key: You must provide valid i-doit credentials (API key) via n8n's credential system.
  • n8n Configuration: No special environment variables are needed beyond standard credential setup.

Troubleshooting

Common issues:

  • Invalid ID or Category entry ID: If the provided IDs do not exist, the API will return an error.
  • Missing required fields: Omitting "Id" or "Category entry Id" (for category deletions) will cause the node to fail.
  • Insufficient permissions: The API key must have permission to delete objects or categories.
  • Network/API errors: Connectivity issues or incorrect API endpoint configuration may result in failures.

Common error messages:

  • "Object not found": Check that the "Id" matches an existing object.
  • "Entry not found": Ensure "Category entry Id" is correct for the specified object and category.
  • "Permission denied": Verify API key permissions in i-doit.
  • "Invalid parameters": Double-check all required fields are filled and correctly formatted.

Links and References

Discussion