Skip to content

Node Configuration Details

Using Jinja2 Templates

Many node fields support dynamic templating using the ${{var}}:

Text Only
# Reference another node's output
${{ node_name.output_field }}

# Access variables
${{ variables.my_variable }}

# Access webhook payload data
${{ webhook_trigger.data.event_type }}

Note: The older {{var}} Jinja2 syntax is still supported for backward compatibility, but the new ${{var}} syntax is recommended to avoid conflicts with JSON schemas.

Code Execution & Monaco Editor

Code nodes (Python and JavaScript) feature a built-in Monaco Editor. This provides: - Syntax highlighting and intelligent auto-completion - Built-in functions and common module suggestions - Version-specific syntax diagnostics (e.g., Python 3.6-3.12 warnings) - Safe execution sandbox with strict module restrictions

Node Naming (Alias)

Each node can have a custom alias for easier referencing:

  • Must start with a letter
  • Can contain letters, numbers, and underscores
  • No spaces or special characters
  • Used in Jinja2 templates to access node outputs

Credential Selection

For nodes requiring API keys or connections:

  1. First create the credential in Credentials page
  2. Select from dropdown in node configuration
  3. Credentials are encrypted at rest using CREDENTIAL_MASTER_KEY
  4. They are decrypted securely only during active workflow execution