Skip to main content

Delete Item

Deletes an item from the specified vault.

Common Properties​

  • Name - The custom name of the node.
  • Color - The custom color of the node.
  • Delay Before (sec) - Waits in seconds before executing the node.
  • Delay After (sec) - Waits in seconds after executing node.
  • Continue On Error - Automation will continue regardless of any error. The default value is false.
info

If the ContinueOnError property is true, no error is caught when the project is executed even if the Catch node is used.

Options​

  • Credentials - Select the vault item to delete.

How It Works​

The Delete Item node removes credential items from Robomotion vaults:

  1. Credential Retrieval:

    • Retrieves vault and item credentials from configuration or message
    • Decodes the credentials structure to extract vault ID and item ID
    • Validates that both IDs are provided and not placeholder values

  2. Validation:

    • Ensures vault ID is selected and not empty
    • Ensures item ID is selected and not empty
    • Validates credential format is correct

  3. Deletion:

    • Calls the vault API to delete the specified item
    • Permanently removes the item from the vault
    • No confirmation dialog - deletion is immediate

  4. Completion:

    • Returns success with no output data
    • Item is no longer accessible in the vault
    • Deletion cannot be undone

Requirements​

  • Vault ID: Must be a valid GUID representing an existing vault
  • Item ID: Must be a valid GUID representing an existing item in the vault
  • Vault Access: User must have delete permissions on the specified vault
  • Item Existence: Item must exist in the vault (error if already deleted)

Error Handling​

Error CodeDescriptionSolution
Core.Vault.DeleteItem.ErrOnCreateConfiguration parsing failed during node creationCheck node configuration in the flow
Core.Vault.DeleteItem.ErrOnMessageMessage parsing errorVerify message format is valid JSON
Core.Vault.DeleteItem.ErrCredentialsInvalid credentials, vault not selected, or item not selectedVerify both vault ID and item ID are valid and selected
Core.Vault.DeleteItem.ErrOutputMarshalFailed to serialize outputCheck output variable configuration

Runtime Errors:

  • Item not found: Item may have been already deleted or ID is incorrect
  • Permission denied: User lacks delete permissions on the vault
  • Vault not accessible: Vault may be locked or unavailable

Usage Examples​

Example 1: Delete Specific Item​

// Delete a vault item by selecting it in the node configuration
// Credentials option: Select vault and item from dropdown
// After node execution:
// Item is permanently deleted from the vault

Example 2: Delete Item Dynamically​

// Delete an item using IDs from message
msg.credentials = {
  vaultId: "550e8400-e29b-41d4-a716-446655440000",
  itemId: "660e8400-e29b-41d4-a716-446655440001"
};
// Credentials option: Set scope to "Message"
// After node execution:
// Item with specified IDs is deleted

Example 3: Delete Item After Processing​

// Delete temporary credentials after use
// First, get the item
// ... use the credentials ...
// Then delete it
msg.vaultCreds = msg.tempItemMeta;
// After node execution:
// Temporary item is removed from vault

Usage Notes​

  • Permanent Deletion: Deleted items cannot be recovered
  • No Confirmation: Deletion is immediate with no confirmation prompt
  • Cascade Effects: Deleting an item doesn't affect flows using it until next execution
  • Error on Missing: If item doesn't exist, an error is thrown
  • Dynamic Selection: Credentials can be from dropdown or message variable
  • Permissions Required: User must have delete permission on the vault
  • No Output: Node produces no output data, only success/failure status

Tips​

  • Always confirm you have the correct item before deleting
  • Consider adding a confirmation step in your flow before deletion
  • Use Get Item first to verify the item exists and contains expected data
  • Store item backups before deletion if data might be needed later
  • Use Try-Catch to handle cases where item might not exist
  • Document why items are being deleted for audit purposes
  • Avoid deleting items that might be in use by running flows
  • Consider using Set Item to mark items as inactive instead of deleting
  • Test deletion logic thoroughly before deploying to production
  • Keep logs of deleted items for compliance and troubleshooting
  • Get Item - Verify item exists before deleting
  • Add Item - Create new vault items
  • Set Item - Update items instead of deleting and recreating
  • List Items - Find items to delete
  • Try-Catch - Handle deletion errors gracefully