Skip to main content
The Pipeline tab in the workflow sidebar shows a workflow’s three steps:
  • Extract: how the source is fetched, such as a direct API call or a browser scrape.
  • Transform: which fields Kadoa computes, and how.
  • Deliver: where each run’s results go. Downloads, API and SDK access, and the destinations Kadoa delivers to.

Extract

The Extract section describes how the source is fetched: the strategy, the approach (direct API or browser), the URL, the request shape, and the selectors the workflow relies on. Pipeline panel on the Extract tab showing strategy, approach, URL, request and selectors

Source code

In Pipeline → Extract, click the Code preview to open the extraction source in the center of the workflow. Select a version to inspect it, or choose Diff to compare it with the preceding version. Diffs support unified and split layouts; expand unchanged lines for more context. Select Back to data to return to your results. Extraction source and a version diff alongside the Pipeline panel The viewer is read-only. It shows the workflow’s control flow and extraction logic, including calls to Kadoa’s shared libraries. The libraries’ internal implementations are not included.

Transform

The Transform section lists the workflow’s fields in two groups:
  • Computed fields: fields Kadoa computes with a built-in function or a transformation step. A Code or AI badge says how each value is made.
  • Source fields: fields extracted as-is, each with its description.
A field added or changed since the last run shows Not built yet until a run produces it. Select a field to see its description and the fields its value is made from. Edit in schema opens the field in the Schema panel. A field only the transformation makes has Ask the agent instead, which opens the workflow’s agent. Pipeline panel on the Transform tab: computed fields marked Code or AI, one expanded to show what it is made from, and source fields below

Deliver

The Deliver section answers one question: where does this workflow’s data go?
  • Download the latest published run as CSV or JSON.
  • API endpoint shows this workflow’s data path. Expand it for the full URL, a copy button, and links to the REST API, SDK, and MCP server.
  • Destinations lists the data destinations that deliver this workflow after each run. Destinations belong to your workspace, not to one workflow: set one up once and any workflow can deliver to it. Expand a destination for its share or bucket, file formats, timing, and a Change button. Click Add to open the catalog: Amazon S3, Google Cloud Storage, SFTP, Snowflake, Databricks, and Azure Blob Storage. Set up opens a Support Center request prefilled with the workflow, the destination, and the details we need.
  • Notifications links to the Notifications panel for Slack, email, and webhooks.
Pipeline panel on the Deliver tab with download buttons, API endpoint, an expanded Snowflake destination, and notifications

API