Step reference

Logic

Condition splits a workflow in two: matching runs continue down the ✓ branch, the rest down the ✗ branch. A condition can test several things at once with ALL (and) or ANY (or), and compares with equals, contains, starts with, ends with, matches a regular expression, is one of a list, greater/less than, or date before/after.

Switch is for more than two outcomes. Give it one value and a list of cases; the first case that matches wins, and anything unmatched takes the default branch. Each case gets its own numbered output on the canvas.

For each repeats the following steps once per item in a list. Set variables builds named values (the usual place to apply filters). Delay waits — anything over five seconds parks the run durably, so restarts and deploys don't lose it.

Wait for approval

Pauses the run and emails the people you name an approve/reject link. The run continues down the ✓ or ✗ branch depending on what they choose, and their decision and any note are available to later steps. You choose how long to wait and what happens if nobody answers.

A parked run doesn't consume a concurrency slot, so a workflow waiting a day on a person costs you nothing while it waits. Pending requests are also listed under Approvals, where a teammate can decide without the email.

Storage

Remembers values between runs: get, set, increment, append to a list, or delete, with an optional expiry. The usual uses are remembering the last id you processed (so duplicates get skipped) and counting things across runs. Increments and appends are atomic, so two runs at the same time can't lose an update.

Digest

Collects items now and releases them later, so a hundred events become one summary instead of a hundred emails. One workflow appends to the digest; a scheduled workflow releases it and does something with {{step.items}}. A digest can also release itself once it reaches a count you set.

Actions

Send email emails someone directly — no Gmail or SMTP account to connect. HTTP request calls an operation on a connected app. Notify posts to a URL. AI transform extracts, classifies, or summarises text.

Subflows

Call workflow runs another workflow and waits for its result, so shared logic lives in one place. The callee declares what it needs with Subflow entry and hands values back with Return output. Calls pin a published version, so improving a shared workflow can't silently change its callers.

When a step fails

Every step has a failure policy: fail the run, carry on anyway, or take a separate error branch. You can also set retries — they back off between attempts, and cover rate-limit and server-error responses, honouring the app's own Retry-After. A per-step timeout stops a hung request holding a run open.

Still stuck? Email support@yakware.com and include the run id — it tells us exactly which step failed and why.