Skip to main content
Describe the data you need in plain language. The agent drafts a plan, you review and approve it, and it builds the dataset and the pipeline for you. Use this when no template matches your job. If you have never run a pipeline before, Get your first labeled dataset walks the same flow on 10 supplied rows, so nothing depends on your own data being right.

Before you start

You need:
  • An account you can sign in to.
  • Full access to the selected team. If you belong to several teams, switch to a writable team before choosing a product. Read-only members cannot create a project.
  • A team with a funded balance, since the deploy at the end is blocked on an empty balance. See Manage your team and balance.

Step 1 — Say what you need done

Sign in. The home screen asks What do you need done? Click Data collection if you want data that does not exist yet — video, audio, images, in-the-field capture. Click Data labeling if you already have data and need it annotated, ranked, transcribed, or moderated. The home screen asking “What do you need done?”, with the Data collection and Data labeling cards. Your choice creates a draft project and opens the Let’s set your task screen. It also tells the assistant which kind of job this is, so the description field asks you for the right things.

Step 2 — Describe what you need

Write what you want in the description field. For a collection job, cover the artifacts you want recorded or sourced, the volume, the format, who may take part, your quality requirements, and how you want the result delivered. For a labeling job, cover your existing data, the label schema, the edge cases, your quality requirements, and the output you need. You can attach files — a dataset, a spec, examples of good and bad answers. The description field with the Data collection placeholder, an “Add datasets, presentations, examples” attachment control, and the Continue button. Then click Continue →. Your description is sent to the assistant as the first message.

Step 3 — Wait for the plan

The agent drafts a plan and shows a Plan card with a step count. When the draft finishes, open the card and review the proposed dataset, fields, and pipeline before clicking Approve. The chat showing a Plan card in the Drafting state, with a step count and “click to open”.

Step 4 — Review and approve the plan

The plan spells out the pipeline it intends to build, the dataset it expects, and the fields on each. Read it against your job — this is the point where a misunderstanding is cheap to fix. To change something, select the text you disagree with, leave a note, and click Send comments. The agent revises and comes back. When the plan is right, click Approve — either here in the panel or on the Plan card in the chat; both do the same thing. Approve is offered only on the plan the assistant drafted last. Open an earlier plan from further up the chat and you can read it, but not approve it. The Plan panel: the pipeline sketch and dataset section, with Send comments and Approve at the bottom.
Nothing is built until you approve.

Step 5 — Answer questions during the build

Once approved, the agent starts building. Where your description left something open, it stops and asks rather than guessing. Questions come with suggested answers and a free-text option, and the plan progress line below shows how far along it is. An assistant question about how audio URLs are served, with three suggested answers, a free-text option, a Submit button, and a plan progress line reading “1 done · 0 abandoned · 6 pending of 7”.

Step 6 — Watch the project take shape

Within a couple of minutes, parts of the project start appearing. You do not have to wait for the agent to finish before looking. The project overview: the sidebar with Pipelines, Datasets and Secrets, one pipeline card, and one dataset row. Under Datasets you can upload a main or golden dataset, review what you already have, and download a dataset. Results from experts appear here too. An example dataset page with Append items, Infer Fields, Export fields to file, and columns for each field. The sample audio URLs are placeholders. Under Pipelines you get the pipeline the agent is building. This is where you inspect what it created, add components, and change settings yourself — price, quality criteria, the interface experts see. The pipeline graph: Start, a routing node, two labeling nodes, a code node and End, with a Cost breakdown control in the top-left.

Step 7 — Read the hand-off

When the agent finishes, review its summary of the dataset, pipeline, and remaining checks. Ask for changes before deploying. For a small pilot, set Max items to launch on Start. After that run, clone the pipeline before changing its item filter or limit; see Label a large dataset in batches.

Step 8 — Review each node

Before launching, open every node and check it: pricing, audience, the labeling interface, the guidelines. The agent’s choices are a draft you own, and after launch the configuration is fixed. A node's Audience & Pricing settings: expert filters, the expert count and recommended rate, time for task, price for task, and the per-expert cap.

Step 9 — Deploy

Click Deploy. The Deploy button. If anything is wrong, an Issues panel opens instead of launching. Errors — in red — block the deploy; warnings, in orange, do not. The Issues panel listing errors and warnings, with the Fix all with agent button. Click Fix all with agent, then go back to Step 8, check what changed, and deploy again. Once no errors remain, you can launch with warnings still open: tick I want to deploy with unresolved warnings, then click Deploy. The Issues panel with only warnings left, the “I want to deploy with unresolved warnings” checkbox, and the Deploy button.
Deployment locks the configuration. Check the labeling interface and quality criteria before launching. If you need changes afterward, clone the pipeline and deploy the copy. Work already recorded on the original run remains billable; see Pipeline pricing.

Step 10 — Confirm the cost

The cost breakdown opens with an expected and a maximum total. Too high, and you can cancel, go back to Step 8, and lower the price per task or the item count. The cost breakdown: one line per cost component with expected and maximum totals, the review checkbox, and the Confirm and deploy button. Tick the review checkbox and click Confirm and deploy.

Step 11 — Wait for the launch

Launching Pipeline tracks the deploy step by step. It usually takes 5–15 minutes, and you can close the window and come back. The Launching Pipeline window: starting deployment, checking balance, connecting dataset, deploying nodes, preparing pipeline items.

What’s next