Skip to main content
Workflow settings are available to workspace administrators. These controls help you manage security and costs across all workflows in your workspace.

​
Accessing Workflow Settings

Administrators can configure workflow settings through the workspace admin panel.
1

Open Workspace Settings

Navigate to your workspace settings from the main menu.
2

Go to Workflows Section

Select the Workflows section to view security and spending controls.

​
Security Controls

Workflow security settings let you control which node types are available to users when building workflows. Disabling certain nodes can help enforce security policies and prevent unauthorized external access.

​
Code Node Toggle

The Code node allows users to execute custom JavaScript within workflows for data transformation and custom logic. When enabled:
  • Users can add Code nodes to their workflows
  • Custom JavaScript execution is permitted
  • Data transformations, calculations, and complex business logic are possible
When disabled:
  • Code nodes cannot be added to new workflows
  • Existing workflows with Code nodes will fail at the Code node step
  • Users must use other nodes (Agent, Condition, etc.) for data processing
Disabling Code nodes affects all workflows in the workspace. Review existing workflows before making changes, as workflows containing Code nodes will no longer function correctly.
When to disable:
  • Your security policy prohibits custom code execution
  • You want to restrict workflow capabilities to pre-built nodes only
  • Compliance requirements mandate limited scripting capabilities

​
HTTP Node Toggle

The HTTP Request node allows workflows to make external API calls to any endpoint. When enabled:
  • Users can add HTTP Request nodes to their workflows
  • Workflows can call external APIs, webhooks, and services
  • Custom integrations with third-party systems are possible
When disabled:
  • HTTP Request nodes cannot be added to new workflows
  • Existing workflows with HTTP Request nodes will fail at that step
  • Users must rely on native integrations for external connectivity
Disabling HTTP nodes prevents workflows from making external API calls. This may break workflows that rely on custom API integrations not available through native connectors.
When to disable:
  • Your security policy restricts outbound network requests
  • Data exfiltration concerns require limiting external connectivity
  • You want to ensure all integrations go through vetted native connectors

​
Spend Limits

Spend limits help you control costs across all workflows in your workspace. These settings work alongside individual workflow limits to provide organization-wide cost governance.

​
Workspace Spend Limit

Set a maximum monthly spending cap for all workflow AI model usage across the entire workspace.
SettingRangeDefault
Monthly spend limit0 - 100,000 EUR500 EUR
How it works:
  • Tracks cumulative AI model costs across all workflows
  • When the limit is reached, workflow executions that require AI models will pause
  • Resets at the beginning of each month
Set this limit based on your expected workflow volume. Monitor usage during the first few weeks to establish a baseline, then adjust accordingly.

​
Default Monthly Limit per Workflow

Set the default spending limit applied to new workflows when they are created.
SettingRangeDefault
Default monthly limit1 - 10,000 USD25 USD
How it works:
  • Every new workflow is created with this limit
  • Workflow owners can adjust their individual limits up to the maximum allowed
  • Prevents runaway costs from newly created workflows

​
Maximum Monthly Limit per Workflow

Set the ceiling for individual workflow spending limits. This prevents any single workflow from exceeding a certain cost threshold.
SettingRangeDefault
Maximum monthly limit1 - 10,000 USDNo limit
How it works:
  • Workflow owners cannot set limits higher than this value
  • Existing workflows with limits above this threshold are automatically adjusted down
  • Admin-set override limits are not affected by this cap
When you lower the maximum limit, all non-admin-overridden workflow limits that exceed the new maximum are automatically reduced to match. The system provides a summary of affected workflows.

​
Execution Step Limit

Each workflow execution is limited to a maximum of 2,000 steps. This prevents runaway workflows from consuming excessive resources.

​
Best Practices

​
Security Configuration

  • Start restrictive: Begin with Code and HTTP nodes disabled, then enable as needs arise
  • Document exceptions: If you enable these nodes, document which workflows use them and why
  • Regular audits: Periodically review workflows using Code and HTTP nodes for security compliance

​
Cost Management

  • Set reasonable defaults: A $25 default limit works well for most use cases
  • Use maximum limits: Set a maximum to prevent any single workflow from becoming unexpectedly expensive
  • Monitor workspace spending: Review the workspace spend limit monthly and adjust based on usage patterns
  • Communicate limits: Let workflow creators know about spending limits so they can design efficient workflows

Cost Management

Learn strategies to optimize workflow spending

Code Node

Understand Code node capabilities and use cases

HTTP Request Node

Learn about HTTP Request node configuration

Workflow Introduction

Get started with workflows