Skip to main content
Parameters let you create reusable workflows that accept different input values each time they run. Instead of hardcoding a URL or search term into a block, reference a parameter and fill in the value when you run the workflow.

​
Opening the parameters panel

In the workflow editor, click the Parameters button in the header bar. A panel appears below the header showing all defined parameters and controls to add new ones. Parameters panel

​
Adding a parameter

Click Add Parameter in the panel. Two types are available:
TypeUse for
Input ParameterValues the user provides when running the workflow (text, numbers, JSON, etc.)
Credential ParameterSecurely inject login credentials from a vault (Bitwarden, 1Password, Azure, AWS, or Skyvern)
Each parameter requires a unique key. This is the name you use to reference it in blocks. Keys cannot contain spaces and cannot use reserved names. You can also add an optional description (shown as help text when running) and a default value.

​
Parameter value types

Input parameters support these value types:
TypeInput controlExample
StringText field"https://example.com"
IntegerNumber field10
FloatNumber field19.99
BooleanToggle switchtrue
JSONCode editor{"key": "value"}
File URLText field (paste a URL)"https://example.com/data.csv"
Credential IDDropdown selector (shown at runtime)Selected from stored credentials

​
Referencing parameters in blocks

Use Jinja2 double-brace syntax to reference parameters inside block fields like prompts, URLs, and data schemas. Basic reference: 
{{ url }}
Nested field access (for JSON parameters): 
{{ config.search_term }}
Convert to JSON string: 
{{ my_data | tojson }}
Example in a Navigation block prompt: 
Navigate to {{ url }} and search for {{ search_term }}
Any block field that accepts text supports parameter references.

​
Credential parameters

Credential parameters securely inject login credentials into blocks without exposing them in prompts or logs.
SourceWhat it provides
Skyvern CredentialUsername and password stored on the Skyvern Credentials page
Bitwarden LoginUsername, password, and optional TOTP from your Bitwarden vault
Bitwarden Credit CardCard number, holder name, expiry, and CVV from Bitwarden
Bitwarden Sensitive InformationSensitive data fields from Bitwarden
1PasswordUsername, password, card data, or TOTP from 1Password
Azure Key VaultSecrets stored in Azure Key Vault
AWS SecretSecrets stored in AWS Secrets Manager
Azure SecretSecrets stored in Azure Secret
When you add a credential parameter, you configure the source and connection details (collection ID, vault ID, etc.). At runtime, Skyvern fetches the real credentials from the vault and injects them into the workflow. Credential values are masked in logs and outputs.

​
Output parameters

Every block automatically produces an output parameter containing its results. You can reference a previous block’s output in any downstream block. The syntax uses the block’s label (lowercased, spaces replaced with underscores) followed by _output: 
{{ extraction_block_output.extracted_information }}

{{ login_output.success }}
This is how you chain data between blocks. Extract data in one block, then use it in the next.

​
Reserved variables

These variable names are built-in and cannot be used as parameter keys:
VariableAvailable inDescription
current_valueLoop blocksThe current item being iterated
current_itemLoop blocksAlias for current_value
current_indexLoop blocksZero-based index of the current iteration
workflow_run_idAll blocksUnique ID of the current run
workflow_idAll blocksThe workflow’s ID
workflow_permanent_idAll blocksThe workflow’s permanent ID
workflow_titleAll blocksThe workflow’s title
Example in a loop: 
Process item {{ current_index }}: {{ current_value.name }}

​
What’s next

Block Reference

Configuration fields for every block type

Run Your Workflow

Execute workflows and fill in parameter values