Skip to main content
Workflow settings are available to workspace administrators. These controls help you manage security across all workflows in your workspace.
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.

​
Accessing Workflow Settings

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.

​
Code Node Toggle

The Code node allows users to execute custom code within workflows for data transformation and custom logic. When enabled:
  • Users can add Code nodes to their workflows
  • Custom code 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
For supported languages and examples, see the Code node page.

​
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 or JavaScript Code nodes for external connectivity
Disabling HTTP Request nodes prevents workflows from making external API calls through the HTTP Request node. JavaScript Code nodes can still call external APIs with ld.request() while Code nodes remain enabled. To restrict outbound requests from workflows, disable both HTTP Request and Code nodes.
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

​
Web Search Node Toggle

The Web search node allows users to search the web from a workflow step. The switch is on by default. Turning it off applies to workspace administrators as well. When enabled:
  • Users can add Web search nodes to their workflows
  • Workflows can look up current information on the web
  • Workflow agents can search the web when web search is enabled on the agent
When disabled:
  • Web search nodes cannot be added to new workflows
  • Existing workflows with Web search nodes will fail at that step
  • Workflow agents cannot search the web, even when web search is enabled on the agent
Disabling the Web search node affects all workflows in the workspace, including workflows that administrators run. Review existing workflows before making changes. A Web search node shows the error “Web search is disabled in this workspace”. You cannot publish the workflow until you remove that step.
When to disable:
  • Your security policy prohibits searching the web from workflows
  • Workflow steps should not send queries to the public web
  • You want external lookups to go through vetted native connectors