Skip to main content

Get Item

Retrieves an item from the 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 ContinueOnError property is true, no error is caught when the project is executed even if Catch node is used.

Output​

  • Item - Retrieved item.

Options​

  • Credentials - The Vault and the Item to retrieve should be selected from here.
info

For this node to work, you should have injected this Vault's Vault Secret Key into the robot.

How It Works​

The Get Item node retrieves credential items from Robomotion vaults:

  1. Credential Configuration:

    • Retrieves vault and item credentials from configuration or message
    • Supports both dropdown selection and dynamic message-based selection
    • Validates credential structure and decodes vault/item IDs

  2. Validation:

    • Ensures vault ID is selected and not a placeholder
    • Ensures item ID is selected and not a placeholder
    • Validates vault secret key has been injected into the robot

  3. Retrieval:

    • Calls the vault API to retrieve the encrypted item
    • Decrypts the item using the vault secret key
    • Parses the item data based on its category type

  4. Output:

    • Returns the decrypted item with all fields
    • Adds metadata including vault ID and item ID
    • Provides structured data ready for use in subsequent nodes

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 Secret Key: Must be injected into the robot environment
  • Vault Access: User must have read permissions on the specified vault

Error Handling​

Error CodeDescriptionSolution
Core.Vault.GetItem.ErrOnCreateConfiguration parsing failed during node creationCheck node configuration in the flow
Core.Vault.GetItem.ErrOnMessageMessage parsing errorVerify message format is valid JSON
Core.Vault.GetItem.ErrCredentialsInvalid credentials, vault not selected, item not selected, or failed to retrieve/decryptVerify vault ID, item ID, and vault secret key are correct
Core.Vault.GetItem.ErrOutputMarshalFailed to serialize outputCheck output variable configuration

Usage Examples​

Example 1: Retrieve Login Credentials​

// Get login credentials from vault
// Credentials option: Select vault and item from dropdown
// After node execution:
// msg.credentials contains {username: "admin", password: "secretpass", meta: {vaultId, itemId}}

Example 2: Retrieve API Token Dynamically​

// Get API token using IDs from message
msg.vaultCreds = {
  vaultId: "550e8400-e29b-41d4-a716-446655440000",
  itemId: "660e8400-e29b-41d4-a716-446655440001"
};
// Credentials option: Set scope to "Message"
// After node execution:
// msg.apiToken contains the decrypted token data

Example 3: Retrieve Database Credentials for Connection​

// Get database credentials
// Credentials option: Select "Production DB" from vault
// After node execution:
// msg.dbCreds contains {host, port, database, username, password, meta}
// Use these credentials with database nodes

Usage Notes​

  • Vault Secret Required: Vault secret key must be injected before using this node
  • Decryption: Items are automatically decrypted using the vault secret
  • Metadata Included: Output includes vaultId and itemId in the meta object
  • Category Types: Different item categories have different field structures
  • Dynamic Selection: Can select from dropdown or provide IDs via message
  • Read Permissions: User must have read access to the vault
  • Version Compatibility: Handles both legacy and current credential widget formats

Tips​

  • Inject vault secrets during robot initialization or before first use
  • Store retrieved credentials in variables for reuse across multiple nodes
  • Use metadata to track which vault/item was retrieved for logging
  • Combine with HTTP Request or database nodes to use retrieved credentials
  • Handle missing vault secrets with Try-Catch for better error messages
  • Avoid logging decrypted credential values for security
  • Use Get Item early in flows to fail fast if credentials are inaccessible
  • Consider caching credentials in memory rather than repeated vault calls
  • Use different vaults for different environments (dev, staging, production)
  • Regularly rotate vault items and update flows accordingly
  • Add Item - Create new vault items
  • Set Item - Update existing vault items
  • Delete Item - Remove vault items
  • List Items - Find available items in a vault
  • HTTP Request - Use retrieved credentials for API calls
  • Database Nodes - Use retrieved credentials for database connections