Skip to main content
Go to the Studio
Robot settings

Robot parameters

Robot parameters

Parameters are configurable variables attached to a robot — passwords, access keys, folder paths, or anything else that can change without you having to edit the robot's flow. They matter most for sensitive information that should not be visible in the Designer.

Why use parameters?​

Picture a robot that signs into a system with a username and a password. Type the password straight into an action and it is visible to anyone who opens the Designer. As a parameter, it is stored securely and kept apart from the flow — and when it changes, it changes in one place.

Other common uses:

  • Credentials for email, databases or internal systems
  • Folder paths that differ between environments
  • API keys or access tokens
  • Settings that change often

Reaching the parameters​

  1. Open the robot's Designer.
  2. Click the tag icon 🏷️ in the sidebar to open the parameters screen.

Creating a parameter​

  1. Click Create parameter (or the + button).
  2. Fill in the fields:
FieldRequiredWhat it is
NameYesThe parameter's identifier. Use descriptive names, no spaces (system_password, folder_path).
ValueYesThe value the robot will use.
DescriptionNoAn explanation so other people know what the parameter is for.
Treat as a secret (password)NoWith this on, the value is hidden and nobody can read it back.
  1. Click Save.

Password parameters​

Turning Treat as a secret (password) on stores the value completely hidden — not even you can read it back once it is saved. You can only overwrite it with a new value.

Password parameters and linked devices

Password parameters are stored locally on the device. If the device is unlinked from the robot, those values are lost and have to be entered again when a new device is linked.

Using a parameter in an action​

Parameters you create are available in any dynamic field in the Designer. To use one:

  1. In an action's settings field, switch the input mode to Parameters.
  2. Pick the parameter from the list.

The robot substitutes its real value at run time, without exposing it in the flow.

Using parameters in expressions (text fields)​

Besides picking a parameter through the Parameters mode, you can embed one inside a text field with this syntax:

{{PARAMETROS.parameter_name}}

That helps when the parameter is part of a larger value, such as a URL or a message:

ExampleResult at run time
https://api.example.com/{{PARAMETROS.client_id}}/datahttps://api.example.com/abc123/data
Hello, {{PARAMETROS.user_name}}!Hello, Brendon!
Bearer {{PARAMETROS.api_token}}Bearer eyJhbGc...

For secrets (parameters marked as passwords), use:

{{SEGREDOS.secret_name}}
info

The name must match the one registered on the parameter exactly (no spaces). Capitalisation makes no difference.

The PARAMETROS and SEGREDOS prefixes are the syntax itself and stay in Portuguese in every language.

caution

The {{PARAMETROS.X}} syntax in text fields is resolved at compile time — the value is not visible in the Designer, but it is included in the compiled code. For values that must truly stay hidden, use {{SEGREDOS.X}} (parameters marked as passwords) instead.

Using parameters in code fields​

In a Code field you can reference parameters and secrets inside template literals with the same syntax:

typescript
// A plain parameter
const user = `{{PARAMETROS.user}}`

// A secret
const password = `{{SEGREDOS.system_password}}`

// Interpolated into a larger string
const url = `https://{{PARAMETROS.server}}/api/login`

return user

At run time the robot replaces {{PARAMETROS.X}} with the parameter's real value.

Editing and removing parameters​

  • To edit a parameter, click it in the list of saved parameters.
  • To remove one, click the delete icon next to it.
Updates do not break the flow

Changing a parameter's value requires no change to the robot's flow. The robot simply uses the new value on its next run.

Next​