Overview
The workflow builder is a canvas-based editor under Workflows. Each workflow starts with Start and End, and you add the steps in between with the+ connector.
You can add a step, edit its settings, add Start inputs, run a single step, duplicate a step, remove a step, and disable or enable a step while you iterate.
How do I create a workflow?
Open Workflows in the sidebar. Click Add Workflow. Enter a name for the workflow. If your workspace uses categories, you can also choose a category. Click Save to open the workflow editor.How do I add a step on the canvas?
Open the workflow in the editor. Start from the default canvas with Start at the top and End at the bottom. Click the+ connector between two nodes. This opens Search steps….
Choose the step you want to insert. The current picker groups steps under categories such as AI, Research, Microsoft, Generation, Utilities, and Integrations.
After you select a step, Fetch Hive inserts it into the workflow and opens Step settings for that new step.
How do I configure start inputs and step settings?
Click Start to open the start step settings. Use Add Input to define the variables your workflow run should accept. For each input, set the display name, variable name, input type, and whether it is required. Start inputs can be Text or Array. Use Text for a single value. Use Array when the caller should pass a JSON array, such as["one", "two"] or [{"url":"https://example.com"}].
Start inputs can also include an optional Example value. Examples are design-time only: they help the editor preview variables and wire later steps before any workflow run exists, but they are not default run values and do not spend tasks.
Use the sample input actions beside Example value to load a saved example or save the current example for reuse.
For array inputs, use an example JSON array that matches the shape callers will provide. For example, [{"name":"Fetch Hive","url":"https://fetchhive.com"}] lets an Iteration step use {{companies}} as its iterator and lets steps inside the iteration reference fields such as {{company_loop.item.url}} before the workflow has run.
Click any non-terminal step on the canvas to open Step settings for that step.
The exact settings depend on the step type. For example, AI Prompt exposes its prompt messages, model parameters, response format options, and failure behavior in the same sheet. When an AI Prompt step uses an Anthropic Claude model, its model parameters also include Prompt Cache with Disabled, 5 minutes, and 1 hour options.
If an AI-backed workflow step uses a retired model, the step settings show a warning and step tests or workflow runs are blocked with model_deprecated. Choose an active model on the step before running the workflow.
Some read-only steps can run multiple versions at the same time: Google Search, Google News, Google AI Mode, Google AI Overview, Bing Search, Exa Search, Exa Similar, Copilot Search, Website Scrape, and RSS Feed. Turn on Parallelization in the step settings, add the versions you want to run, and set only the fields that should differ between versions.
When the workflow runs, Fetch Hive waits for every version to finish and stores the step output as an array in version order. Later steps can reference that array with the same variable pattern as other step outputs, for example {{step_2.output}}.
Parallelization is not available for steps inside an Iteration body. If you need multiple search or fetch versions, run that parallelized step before the iteration and iterate over its output, or keep the steps inside the loop non-parallel.
Your plan controls how many versions a single step can run in parallel. If a version fails and the step is set to Continue, Fetch Hive omits that failed version from the output array and keeps successful versions in order. If no versions succeed, the output is an empty array. If the step is set to Terminate Workflow, the workflow stops.
For Iteration steps, the iteration’s own failure behavior controls the loop body. If the iteration is set to Continue, a failed body step stops that item and leaves null for that item in the iteration output, even if the body step is set to Terminate Workflow. If the iteration is set to Terminate Workflow, any failed body step stops the workflow.
Use When the step fails when you need to decide whether the workflow should stop or continue after a step error.