Skip to main content
A task handles one goal on one page. When your automation needs multiple steps, you need a workflow. This page explains how workflows work, walks you through building one from scratch, and covers the editor’s features.

​
How workflows work

A workflow is a sequence of blocks that run one after another. Each block does one thing: navigate to a page, extract data, send an email, run custom code, loop, or branch. You connect blocks on a visual canvas, pass data between them, and run the whole chain with one click. 
[Browser Task] → [Extraction] → [Loop] → [Send Email]
       ↓               ↓            ↓           ↓
  opens the page   JSON output  per-item     digest sent
                                processing

​
How data flows between blocks

Every block produces an output. Downstream blocks reference it using the pattern {{ block_label_output }}. For example, an Extraction block labeled scrape_listings produces output that later blocks access as {{ scrape_listings_output }}. The label is lowercased with spaces replaced by underscores, then _output is appended. This is how you chain steps together. One block’s output becomes the next block’s input.

​
Block categories

CategoryWhat it doesExamples
Browser AutomationInteract with web pages using AIBrowser Task, Browser Action, Extraction, Login, Go to URL, Print Page
Data and ExtractionTransform data without a browserText Prompt, File Parser
Control FlowBranch, loop, validate, or pauseLoop, Conditional, AI Validation, Code, Wait
FilesDownload and upload filesFile Download, Cloud Storage Upload
CommunicationSend data to external services or humansSend Email, HTTP Request, Human Interaction
See Block Reference for every block type and its configuration fields.
If your block needs a browser, pick a browser automation block. If it just needs to process data, use Text Prompt or Code. If you need to repeat or branch, use control flow.

​
Tutorial: Build a job listing tracker

Let’s build a real workflow. You’ll create an automation that finds the top 5 job listings from Hacker News’s monthly “Who is Hiring” thread, summarizes each one, and emails you a digest. This uses 5 blocks across 3 categories: browser automation, data and extraction, and communication.
1

Create a new workflow

Go to Workflows in the left sidebar and click Create → Blank Workflow.Create workflow dropdown showing Blank Workflow and From Template optionsThe editor opens with an empty canvas showing a single start node. Click the workflow title at the top left and rename it to HN Job Tracker.
2

Add a Browser Task block

Hover over the + button on the edge below the start node and select Add Block. A searchable block library opens on the right. Find and select Browser Task Block.The block appears on the canvas with a configuration panel on the right. Fill in:
FieldValue
Labelfind_hiring_thread
URLhttps://news.ycombinator.com
PromptFind and open the latest monthly "Ask HN: Who is hiring?" thread. The task is complete when the thread is open and job listing comments are visible.
The Browser Task block uses AI to navigate the page and accomplish the goal described in your prompt. Include your success criteria directly in the prompt so the AI knows when it’s done.Browser Task block configured with find_hiring_thread label, URL, and prompt
The URL for the latest hiring thread changes every month. The Browser Task block uses AI to find the right link on the page. Use Go to URL when you know the exact destination URL upfront.
3

Add an Extraction block

Hover over the + on the edge after find_hiring_thread, select Add Block, then choose Extraction Block.Configure:
FieldValue
Labelscrape_listings
Data Extraction GoalExtract the top 5 job listings. For each listing, get the company name, role title, and a brief description of the position.
Now enable the Data Schema checkbox to reveal the JSON editor, and paste:
{
  "type": "object",
  "properties": {
    "listings": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "company": { "type": "string" },
          "role": { "type": "string" },
          "description": { "type": "string" }
        }
      }
    }
  }
}
The schema tells Skyvern exactly what structure to return. Without it, the AI picks its own format. You can also click Generate with AI next to the schema field to have Skyvern suggest a schema based on your extraction goal.Extraction block configured with scrape_listings label, extraction goal, Data Schema checkbox enabled, and JSON schema
Label your blocks descriptively. The label determines the output variable name. scrape_listings means downstream blocks reference its data as {{ scrape_listings_output }}.
4

Add a Loop with a Text Prompt inside

Hover over the + after scrape_listings, select Add Block, then choose Loop Block.Configure the loop:
FieldValue
Labelprocess_each
Loop Value{{ scrape_listings_output.listings }}
This iterates over the 5 listings extracted in the previous step. Now add a block inside the loop. Hover over the + inside the loop body, select Add Block, and choose Text Prompt Block.Configure the Text Prompt:
FieldValue
Labelsummarize
PromptSummarize this job listing in one sentence. Company: {{ current_value.company }}, Role: {{ current_value.role }}, Description: {{ current_value.description }}
Enable the Data Schema checkbox and paste:
{
  "type": "object",
  "properties": {
    "summary": { "type": "string" }
  }
}
The Text Prompt block sends text to the LLM without opening a browser. It processes data only. Each iteration produces a one-line summary of that job listing.Loop block with process_each label containing a summarize Text Prompt block inside
Inside a loop, two reserved variables are available:
  • {{ current_value }}: the current item from the list being iterated
  • {{ current_index }}: the item’s position, starting from 0
These only exist inside loop blocks. In this example, {{ current_value.company }} gives you the company name for the current listing.
5

Add a Send Email block

Hover over the + on the edge after the loop (back on the main flow, not inside it), select Add Block, then choose Send Email Block.Configure:
FieldValue
Labelsend_digest
RecipientsYour email address
SubjectHN Job Digest - Top 5 Listings
BodyHere are today's top job listings from Hacker News:\n\n{{ process_each_output }}
The {{ process_each_output }} reference pulls in the collected summaries from every loop iteration.
6

Save and run

Workflows are not auto-saved. Click the Save button (disk icon) in the header bar before navigating away or you’ll lose your work.
Click Save, then click Run in the top right. A parameters page opens where you can review and confirm the workflow’s settings. Click Run Workflow to start execution.The live execution view opens. Watch as Skyvern navigates Hacker News, extracts listings, summarizes each one, and sends your email.

​
What you built

Five blocks, three categories, zero code. You can now re-run this workflow anytime, tweak the extraction schema to pull different fields, swap the email for an HTTP Request to post to Slack, or add a Conditional block to only email when listings match certain criteria.

​
Editor reference

​
Layout

Workflow editor overview
AreaWhat it shows
Header bar (top)Workflow title (click to rename), Parameters button, Save button, Template toggle, History button, Run button
Canvas (center)Visual graph of blocks connected in sequence. Zoom with the scroll wheel, pan by dragging the background.
Configuration panel (right)Opens when you click a block. Shows that block’s settings form.

​
Adding blocks

Hover over the + button on any edge (the connecting line between blocks) to reveal the menu. Select Add Block to open the block library, a searchable list of all available block types. Click a block to insert it at that position. The menu also offers Record Browser (record actions in a live browser to generate blocks) and Upload SOP (upload a PDF procedure to auto-generate a workflow). When you create a blank workflow, hover over the + on the start edge to add your first block. Add block panel

​
Configuring blocks

Click any block on the canvas to open its configuration panel on the right. Each block has a Label field (which determines its output variable name) and block-specific settings. Browser-based blocks share additional fields like URL, Engine, and Max Retries. See Block Reference for the full list of fields on each block type.

​
Connecting and reordering blocks

Blocks auto-connect when you insert them via the + button. They execute top to bottom in the order shown on the canvas. Conditional blocks create branches. Each branch connects to a different sequence of blocks and merges back at a common point. Loop blocks contain child blocks that repeat for each item in the loop’s list. To reorder blocks, delete the block you want to move and re-add it at the desired position using the + button.

​
Deleting blocks

Click the three-dot menu on a block’s header and select Delete Block. Downstream blocks reconnect to the previous block automatically.

​
Saving

Workflows are not auto-saved. Click the Save button (disk icon) in the header bar to persist your changes. The editor warns you if you try to navigate away with unsaved work.
The Run button also saves before starting execution.

​
Header bar actions

ButtonDescription
Save (disk icon)Save the current workflow definition
Template (bookmark icon)Toggle whether this workflow is saved as an organization template
History (clock icon)View past runs of this workflow
ParametersOpen the parameters panel (see Workflow Parameters)
Run (play icon)Save and start a new execution (see Running Workflows)

​
What’s next

Block Reference

Configuration fields for every block type

Add Parameters

Pass dynamic values into your workflows

Run Your Workflow

Execute workflows and track results