Config Store icon

Config Store

Store and retrieve global configuration variables across workflows

Delete Variable

AI-generated

Overview

This node manages global configuration variables across workflows by allowing users to set, get, delete, and clear variables stored in a centralized config store. It is useful for storing environment variables, API keys, or any global settings that need to be accessed or modified by multiple workflows. For example, you can store a project ID or API token once and retrieve or delete it as needed in different workflows.

Use Case Examples

  1. Set a variable named APPWRITE_PROJECT_ID with a project ID value.
  2. Get the value of a stored variable to use in subsequent workflow steps.
  3. Delete a variable when it is no longer needed to keep the config store clean.

Properties

Name Meaning
Variable Name The name of the variable to set, get, or delete. Use uppercase for convention.
Options Additional options for the operation.

Output

JSON

  • _configStore
    • operation - The operation performed (set, get, delete, etc.)
    • variable - The name of the variable involved in the operation
    • value - The value of the variable, masked if marked as secure
    • success - Indicates if the operation was successful
    • found - Indicates if the variable was found (for get operation)
    • error - Error message if the variable was not found
    • deleted - Indicates if the variable was deleted (for delete operation)
    • cleared - Number of variables cleared (for clear operation)
    • count - Number of variables affected (for setMultiple and getAll operations)
      - The actual variable value included in the output if not marked as secure

Dependencies

  • No external dependencies; uses an internal Map to store variables in memory.

Troubleshooting

  • If a variable is not found during a get or delete operation, the output will indicate 'Variable not found'. Ensure the variable name is correct and exists in the config store.
  • Secure variables mask their values in logs and output to protect sensitive data; if you see '***SECURE***', it means the value is hidden intentionally.
  • The config store is in-memory and will reset if the node or workflow is restarted, so variables are not persisted permanently.

Links

Discussion