Change or delete a workspace variable

Change a variable's values when an address, channel or rate changes, and every workflow that reads it picks the new value up on its next run. Delete a variable you no longer use; Bizomate shows which workflows read it before you do.

Who can do this

• Workspace role: Admin. Others do not see the edit and delete buttons.
• Plan: Starter and above. On Free, or after a plan has ended, the page is read-only.

Steps

Change a variable

1. Select your avatar at the top right, then Settings.
2. Under Workspace, select Variables.
3. On the variable's row, select the pencil button (Edit). The Edit variable panel opens.
4. Change the Name, Description (optional), the Development value (or Same as Production), or the Production value.
5. To change the Type between Text and Connection, select the other type. A box asks, for example, "Change api_base_url to a Connection?" and says how many workflows using it will need their steps checked. Select Change to Connection (or Change to Text), or Keep it Text to go back. Changing type clears both values.
6. Select Save variable.

The message api_base_url saved says "Workflows read the new value on their next run."

Delete a variable

1. On the variable's row, select the bin button (Delete).
2. A box asks "Delete api_base_url?":
   • "No workflow reads it, so nothing else changes." — or
   • "2 workflows use it, 1 of them published. Their runs will fail at the first step that reads it until you add it back or edit them." It lists each workflow and whether it is Published or a Draft. For a Connection variable it says "Their steps will need a connection chosen."
3. Select Delete variable. (Select Cancel to keep it.)

The message api_base_url deleted repeats what it means for the workflows that used it.

What happens next

• A changed value is used from each workflow's next run, including live versions. Nothing needs publishing.
• Renaming a variable does not change the workflows that read it. A step that reads {{ $vars.old_name }} fails until you edit it.
• After a delete, runs that read the variable stop at that step with "… is not a variable in this workspace. Add it in Settings › Variables, or change the step." Adding a variable with the same name back makes them work again.

Good to know

• Used by on each row counts the workflows that read the variable.
• Updated shows when it last changed and by whom.

If something goes wrong

Related

• Variables and environments
• What each role can do