EdgazeDocsEdgaze Docs
DocumentationAPI Reference
Home
Core
Workflow InputWorkflow FormWorkflow OutputMergeMerge ObjectsTemplateMap
AI
LLM ChatLLM ImageLLM Embeddings
Logic & integration
HTTP RequestWeb ScrapeYouTube TranscriptJSON ParseConditionDelayLoopRun Another Workflow (Remix)

Platform status

Checking platform status
Block reference

Condition

Choose a true or false branch with deterministic comparisons or an explicitly enabled AI rule.

Audience

Creators building and publishing workflows.

Overview#

Condition evaluates incoming data and continues on exactly one path: True Branch or False Branch. Basic operators are deterministic in current workflows. Adding a human-language rule explicitly switches the block to AI evaluation, which adds model latency, provider usage, and credential requirements.

Use it to gate steps, skip work when input fails a rule, or split products into different outcomes.

Condition

Press enter or space to select a node. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

Ports#

  • Input: Value: The data to evaluate.
  • Output: True Branch: Taken when the condition passes.
  • Output: False Branch: Taken when the condition fails. Only one branch runs.

Inspector#

  • AI rule (optional): Plain-English judgment such as "The user clearly wants to proceed." Leave this empty for deterministic evaluation. Entering a rule invokes an AI model.
  • Condition Type: Truthy, Falsy, Equals, Not Equals, Greater Than, or Less Than. These operators run deterministically when the AI rule is empty.
  • Compare Value: Required for equals, not equals, greater than, and less than checks.

Tips#

  • Keep branch labels obvious on the canvas so the graph reads left to right.
  • Prefer a deterministic operator when an exact comparison is sufficient.
  • When an AI rule is present, credential requirements follow the listing mode: hosted uses Edgaze credentials, creator-connected uses the creator's Vault key, and buyer-BYOK uses the buyer's Vault key and requires Plus.
  • Test both branches with representative input before publishing.

Related#

  • Workflow Studio

Was this useful?

Your response helps us improve the documentation.

More blocks

Workflow Input

Ask the customer one clear question and turn their answer into data your workflow can use.

Workflow Form

Collect several run-modal fields in one grouped form, each with a stable key for downstream steps.

Workflow Output

Define what the customer receives when the workflow finishes.

On this page
OverviewPortsInspectorTipsRelated
© 2026 Edge Platforms, Inc. All rights reserved.