Skip to content
  • There are no suggestions because the search field is empty.

Variables

Variables store configuration values — like API keys or environment‐specific flags — that workflows can reference at runtime.

📋 Variables

The Variables page provides a full list of defined values with the following columns:

  • Name: Unique identifier for the variable
  • Value: The actual stored data
    • For secure variables, the value is masked (******)
  • Secure: Indicates whether the variable is Secure (encrypted) or Unsecure (plain text)
  • Actions:
    • Delete (variables cannot be edited after creation)

You can reach this page from Administration → Variables.


➕ Creating a New Variable

To add a new variable:

  1. Click + New Variable
  2. Fill in the following fields:
    • Name – must be unique and descriptive
    • Value – this is the string your workflow will access
    • Secure – optional checkbox:
      • If checked, the value is encrypted and cannot be viewed again after saving
      • Use this for passwords, secrets, or tokens
  3. Click Save

💡 Secure values cannot be read again after saving. Make sure you store the original somewhere safe.


🔁 Using Variables in Workflows

Variables can be used in task inputs or expressions using the following syntax:



Example:

To access a variable called API_KEY, use:



Both Secure and Unsecure variables are referenced the same way.


✅ Best Practices

✅ Do this... 🚫 Avoid this...
Use Secure for all credentials Storing passwords as Unsecure values
Prefix names like M3_, CRM_ Using generic names like token
Keep a team-wide variable register Relying on memory for what’s configured
Rotate secrets regularly Leaving old credentials indefinitely

🛠 Troubleshooting

Problem Solution
Workflow fails due to missing variable Check the spelling — names are case-sensitive
Need to update a variable’s value Delete the old variable and create a new one
Unsure what a value resolves to Test with an Unsecure version in a non-prod environment