Journeys

Variables, secret values, outputs, and files ​

Variables keep changing or sensitive data out of the prose of a check. Files make a reusable upload available to every check on one site. Outputs pass a fresh value from a check to a follower.

Variables ​

Add a variable in the check editor with:

  • a name;
  • an optional default value;
  • a description that tells the agent what the value means;
  • Secret when the value must be protected; and
  • Optional when the run may continue without it.

Reference a variable as in the instructions or start URL. Journeys also provides declared values to the agent as structured inputs, so a useful description still matters when the placeholder is not in the prose.

A secret variable cannot appear in the start URL. URLs are copied into browser and network records where their values cannot be reliably redacted. Use a non-secret host or path variable there and keep credentials in instructions or structured inputs.

Before a manual run, you can override defaults for that attempt. A required variable with no saved, default, or supplied value prevents the run from starting and names what is missing.

Secret variables ​

A secret value is encrypted at rest and is never read back into the interface. After saving, Journeys shows only that a value is set. It redacts the value from run facts, Activity, and reports.

When editing, leaving an existing secret blank keeps the stored value. Enter a new value to replace it, or use the explicit clear control to remove it. Turning off Secret or deleting the variable also removes the protected stored value; Journeys does not reveal it as ordinary text.

Use a dedicated test credential with the least access necessary. Redaction protects Journeys' records, but it cannot prevent the tested application itself from displaying a credential to the browser.

Outputs ​

An output declares a value that a parent check will find during its run and pass to a check configured with Runs after. It has a name, a description of where or how to identify the value, and an optional secret flag. It has no default because the run must produce it.

Outputs have no effect when no check follows the parent. Read Checks that run after another for the execution and failure rules.

Files ​

Open Site settings → Files to upload a file once for the site's checks. In a check's instructions, name it exactly, for example:

Upload sample-cv.pdf to the résumé field, then confirm the filename appears.

Journeys attaches the named site file when the run needs it. The Files screen shows both per-file and total site limits for your account.

Files cannot be renamed. Upload the replacement under the desired name, update the instructions, then remove the old file. Deleting a file does not rewrite checks that mention it, so those checks can fail on their next run.