Your first pipeline

This page walks through the whole first-time flow, from the sign-in dialog to a workspace with a running pipeline. Nothing here needs preparation beyond an email address and an idea of the data you want.

You need

An email address

Rows used

Up to your free 100

Time

Minutes to propose; up to an hour or two to build

Result

A workspace with a verified first dataset

1. Sign in

Go to factory.jsonify.com/setup. You can describe your goal before you sign in; signing in is only required when you press Build my workspace, and your brief and attachments stay saved through it.

The sign-in dialog is titled Sign in or create an account. There is one flow for both: if the address is new, an account is created for you.

1. Enter your email address and press Continue with email. A quick security check may appear; complete it and continue.
2. Enter the six digits from the email you receive. The number expires in 10 minutes. A resend link appears after a 30-second wait, and Change email takes you back a step.
3. Choose your organisation if you belong to more than one. The one you used last is marked Last used.
4. Add your name the first time. First name is required; Last name is optional. If a personal organisation was created for you, you can rename it here (the default is your first name followed by “‘s Organisation”).

Prefer Google or single sign-on? Below the email field, Google and Other options open the hosted secure sign-in page. Organisations that require SSO or multi-factor authentication are sent there automatically with a short explanation.

Sign-in uses a one-time number sent to your inbox. There is no password to set or remember.

2. Describe what you want

The setup page asks What data do you need? with Describe what you want to collect and how you’ll use it. Jason will help you build a pipeline. Type your goal into the box (placeholder e.g. Track prices and availability across competitor websites, up to 2,000 characters). Say what to collect, from where, what a row is, and how often it should refresh. You do not need to explain how any website works; Jason works that out.

Two briefs of different shapes, both of which work:

Track the price, promotion text and stock status of the 120 products in the attached sheet across Tesco, Sainsbury’s and Ocado. One row per product per retailer per day. Refresh every morning at 6am UK time and flag any price change over 5%.

Find every planning application submitted to Manchester City Council in the last 30 days. For each one keep the reference, address, proposal description, applicant, status and decision date. I don’t have a list of sources; the council portal is the obvious one but include anything else that publishes them. Weekly is fine.

The first brief is a closed list with a schedule and a rule; the second is open-ended and asks Jason to propose sources. Either way, Jason comes back with a proposal you can adjust.

Under the box, Try an example offers three starting points (Track competitor prices, Collect news and Monitor reviews). Each one fills the box with a short brief you can edit.

Attach files, at the bottom left of the box, opens a picker with three tabs: File (drop or browse, any file type), URL (paste a Google Sheet or web page address) and Text (paste a list, one item per line). Attachments show as chips beside the button. Limits are 20 files per message, 25 MB each and 100 MB in total.

Advanced, below the examples, opens two more options:

Option	Values	Default	What it does
Use synthetic data	On · Off	Off	Build a dashboard with fictional sample rows. Jason still writes a reviewable brief, but no pipeline is created and nothing is collected. Useful for trying the analytics side before committing sources.
Skip, just make an empty workspace	Button	—	Creates a workspace named “New Workspace” with nothing in it and takes you to its Home page (Creating your workspace… while it works). Use it when you want to upload a dataset or start from a chat instead of a build.

Build it sends the goal to Jason. It is disabled until the goal has text.

While Jason reads the brief the button reads Starting… and the page shows Understanding your goal…, then Preparing your setup…, then Getting Jason ready…. If Jason does not answer, the page says Jason hasn’t replied yet. Please try again. and the button becomes Retry with Jason. If a goal is outside what Jsonify collects, the page explains why and you can rewrite it; Start a new setup clears everything.

Open factory.jsonify.com/setup later and you are offered Resume setup or Start fresh. Starting fresh keeps the earlier conversation saved.

3. Review the proposal

After the dialog closes you are in the setup conversation. Jason’s activity appears as lines you can expand, with Jason is working… and Stop while it works. As Jason inspects the sources, a Live Sample Data card estimates how many rows the pipeline could collect.

On the right, Your workspace summarises the proposal as it takes shape:

• Sources. URL pills, up to 10. Remove one, or Add a public http or https address and press Apply sources to have Jason re-inspect.
• Columns. Up to 30 chips with their types. Add or remove and press Apply columns.
• Estimated Volume. A range of rows per month with a How this was estimated disclosure.
• Schedule. The proposed cadence, marked “proposed, not yet enabled”. Edit it and press Apply schedule, or leave it for later.
• Row pricing. Your starting allowance and the estimated monthly cost at the proposed volume, with a How does pricing work? slider.

Under the rows: Once built, your pipeline repairs itself when sources change. Enable its schedule after the first result. The panel is hidden when Use synthetic data is on.

You can also just reply in the composer (Reply to Jason…). Anything you type goes to Jason as a follow-up, and Jason may ask questions of its own: a card headed Jason has a question with choices to pick from, or a box to write your own answer.

Keep the retailer list but drop the stock status column, and add the unit price per 100g where the site shows it.

When the brief is ready, the proposal opens by itself as a dialog titled You’re ready to build! A Workspace proposal card stays in the chat (Your proposal is saved here. Review it when you’re ready, or tell Jason what to change.) with Review proposal to open it again. The dialog shows, in order:

Section	What it shows
Name and purpose	The brief’s name and one line on what it is for.
Reading these sources	One pill per source. You can add, remove or change sources later.
Extracting data like this, starting with 7 columns	A live sample table: the proposed columns with their types (price · number) and a few rows Jason collected while inspecting, with Sample data collected live from the sources above, 3 minutes ago. Without sample rows it lists the columns and types instead. You can change the columns and shape of the data later.
Estimated data volume	1,200–1,800 rows per month, or Not estimated yet, with How this is estimated.
Estimated time for Jason to build	Up to 45 min, Up to 1 hr and so on: how long the build and its first real run should take.
Product	Jsonify Radar, linking to the product page.
Starting plan	Free · 100 rows/month. You start on the free plan. Collection stops automatically once you’ve used this month’s rows. Upgrade at any time for more rows.

Tick I accept the Terms, Privacy Policy and Acceptable Use Policy. (unticked by default, and cleared again whenever the proposal changes), then press Build my workspace. Revise with Jason closes the dialog and puts the cursor back in the composer instead. If you have unsent text or files in the composer, the dialog asks you to send them first so they are included. If you are not signed in yet, the sign-in dialog opens now; your reviewed setup and uploaded files stay saved through it.

Collection stops automatically when the monthly quota is exceeded. You can raise the limit at any time; see Usage and Billing.

4. Watch the build

The build runs in the background because it ends with a real first run against your sources. A dialog headed Jason is building your workspace stays on screen: He’s setting up your data pipelines and running them to collect live data.

Part of the dialog	What it shows
Countdown	~35 min remaining until your workspace is live, with a progress bar. It reads Almost there (Taking a little longer than estimated) once the estimate has passed, and Paused (The build is waiting on you) when Jason has stopped to wait for you.
Note	You can close this page now. Jason will email you at maya@example.com when it’s ready to go, or if he has a question.
Build options	A menu with Switch workspace (when you have other workspaces), Stop build (stops Jason straight away, without a confirmation, and pauses the build) and Edit build (hides the dialog and shows the setup chat, so you can message Jason).
Activity	A collapsed footer showing Jason’s latest step, or Preparing your workspace. Expand it for the full list of what Jason is doing: opening pages, working out layouts, testing on a sample, and sending the candidate for independent review. Load earlier activity pages back.

The same activity is available afterwards in the build chat under Conversations.

Two things can interrupt a build:

• A question. If Jason needs a decision, the question card appears in the dialog and the build waits for your answer. Jason also emails you the question; a reply to the email counts as the answer.
• A blocker. The dialog changes to Your build needs attention: Jason couldn’t finish the build. Open the chat to review what happened and help resolve the blocker. Resolve with Jason opens the conversation so you can read what happened and reply. Before giving up, Jason emails you once, saying what is blocking him and the one decision that would unblock it.

5. Your workspace is ready

When the first run has been verified the dialog reads Your workspace is ready, with Jason’s summary (or Your first results have been verified.) and a card for each thing built:

• A Dataset card: the dataset’s name and 1,240 verified rows · Updated 2 minutes ago. Click it to preview the rows.
• A Pipeline card for each pipeline, Data extraction pipeline. Click it to preview the pipeline.

Go to workspace takes you to Home.

Jason also sends you a handoff email from Jason at Jsonify: what the first run collected and which checks passed, the first five rows as a table with the full dataset attached as a spreadsheet, any column he could not collect and why, and a choice of schedules with the rows and monthly cost of each. Reply with your choice and the reply goes to the build chat. Open your dataset in the email opens the workspace.

Before you look at anything else, open the dataset and read the rows:

1. Check the columns match the brief. Every field you asked for should be there with the right type. Numbers should be numbers, dates should be dates.
2. Open a few rows. Click a row, then Origin, to see the page each value came from and a screenshot of it as collected. See Row detail and provenance.
3. Read the statement of work. Open the pipeline. The Statement of Work says what is in scope and, just as important, what is not. See Statement of work and steps.
4. Look at the run. Runs on the pipeline page shows pages fetched, rows collected and duration. See Run detail.

The first run is real data, not a preview. It counts towards your monthly rows, and it is the first dataset version.

6. Refine the brief

Anything that is not right is a message to Jason, either from the pipeline page (Edit pipeline) or from a new chat with the pipeline mentioned. Jason makes the change as a new pipeline version, verifies it, and activates it. The full flow is on Changing a pipeline.

The promotion text column is picking up the “Clubcard price” badge as well as the offer. Keep only the offer wording, and add a separate true/false column for whether a Clubcard price applies.

Turn the schedule on: every day at 06:00 Europe/London.

The build leaves the schedule off until you have seen the first results; the handoff email asks which schedule you want. Turn it on by asking Jason, or in the pipeline’s Settings. See Scheduling.

The Home page

Home is the overview of one workspace. It refreshes itself every few seconds, so a running pipeline or a working chat updates without a reload. A workspace with no pipelines opens with Suggested tasks of two cards, Build your first pipeline and Chat with Jason, and a Welcome to Jsonify dialog (To get started, build your first data pipeline with Jason!, with Later and Continue). Once populated, Home shows these sections in order.

Needs attention

Shown only when there is something to act on:

• Active chats. Chats where Jason is working, queued, or monitoring a run, with the elapsed time. Click to open.
• Pipeline warnings. Up to five pipelines whose last run failed or whose health is degraded in the last seven days, as Failure 2 hours ago · Last run failed. Click to open the pipeline; the X dismisses the warning until the next failure.

Pipelines

Every pipeline as a status card, up to six at first with Show <n> more pipelines (and Show fewer). Each card has the name, cadence, the number of rows in its outputs, a status line and when it last ran. Card colour follows health: white before the first run, green when healthy, blue while running, amber for a warning, red after a failure, and purple when an automatic repair fixed the last failure. A degraded pipeline shows This pipeline is degraded and needs healing to resume. instead of its status line. Next run shows the scheduled time. Once every card is showing, an Add new pipeline tile at the end opens the new-pipeline composer. View all opens the pipelines list.

Status lines you will see: Not run yet, Running, Finished successfully, Repaired, Synced, Awaiting publication, Needs attention, Last run cancelled and No recent successful run. The card menu has Pin to sidebar.

Scheduled

The next five things due to happen: scheduled pipeline runs and any follow-ups Jason has scheduled in a chat (tagged Jason task). Each shows the time and a live countdown (Running in 0:42:10, Run due). Empty text: No scheduled pipeline runs or Jason tasks.

Datasets and Deliverables

Two lists side by side, each with a count. Datasets lists the most recently updated datasets with row counts and the producing pipeline. Deliverables lists files a pipeline produced; open one for a preview. View all on either side opens a searchable list, 20 per page. Empty: No published datasets yet or No deliverables yet, each with Start with Jason.

Analytics

Appears once the workspace has had a run. Tiles for Rows processed, Pipeline runs, Failed runs, Success rate, Average rows / run and Cancelled runs, each with a small trend chart and the change against the previous period. The two filter buttons open Analytics filters, where you choose a Pipeline (default All pipelines) and a Date range (Last 24 hours, Last 7 days, Last 30 days — the default — or Last 90 days), then Apply.

Suggested tasks

Jason proposes next steps grounded in your goal, your pipelines and their recent runs. Two cards show at a time; Show <n> more suggestions reveals the rest and Refresh asks again. Click a card to read the detail (Suggested: …), then Send to Jason puts the task into the Jason panel for you to edit and send (nothing is sent automatically) or No thanks dismisses it for everyone in the workspace. With nothing to suggest: Nothing suggested right now. Refresh to ask again.

Help and community

Invitations from the Jsonify team, each opening a short dialog:

• Set up a shared Slack Connect channel with the Jsonify team. Email me a Slack Connect invitation sends the invitation to your account email; Check connection confirms it once accepted. Hidden once the channel is connected.
• Get free rows by reviewing us on G2 and Get free rows by saying hi on Reddit. The reward details are not live yet, and no rows are awarded for them today.

The X on each hides it for the workspace; the section disappears when all are hidden.

Recent chats

Chats are not a Home section, but they are one hover away. Rest the pointer on Conversations in the sidebar and a panel lists New chat and your eight most recent conversations. Chats where Jason is still working also appear under Needs attention.

The sidebar

The left rail is present on every workspace page. It is pinned open by default; the pin button next to the wordmark (Unpin sidebar — allow auto-collapse) lets it collapse to icons and expand on hover. What it lists can be arranged for the whole workspace, and pipelines, datasets and dashboards can be pinned to it from their card menus; see The sidebar.

Item	Where it goes	Notes
Home	/	The overview described above.
Conversations	The Chats page	Badge counts chats where Jason is working. Hover for recent chats.
Pipelines	Pipelines list	Under Data collection. Hover for the first ten pipelines, View all and View runs.
Latest runs	All runs across pipelines	Badge counts active runs.
Analytics	Dashboards	Under Connections. Hover for every dashboard.
Integrations	Integrations	Inputs, outputs, and the alert rules that send to them.
Pinned items	The pinned pipeline, dataset, dashboard or file	Added from a card’s Pin to sidebar, under the section they belong to.
rows left	Monthly usage dialog	See below.
Search	Workspace search	Also ⌘K (Ctrl+K on Windows and Linux).
Settings	Workspace settings	Signed-in users only. A red ! appears when billing needs attention.
Your name	Account menu	Signed in as and Log out.

Alert rules have no sidebar entry of their own; they live on the Integrations page and on each pipeline’s Integrations page.

The rows-left meter. The grey card near the bottom reads N rows left with a thin progress bar for the month. It turns amber at 80% of your monthly cap and red when the cap is reached. Click it for the Monthly usage dialog: rows collected, the monthly cap, any once-off row grants, the reset date, and Manage usage →. The full picture is on Usage.

Search (⌘K). Type two or more characters to search datasets, dashboards, pipelines, runs, chats, alerts, integrations and run outputs by name. With three or more characters you can also Search dataset rows for “…” across the active version of every dataset. When nothing matches, Ask Jason about “…” starts a chat with the question. Arrow keys move, Enter opens, Escape closes.

Jason (⌘J). On every page except a chat page, a Jason button floats bottom-right. ⌘J (Ctrl+J) toggles it. The panel is a compact chat scoped to the page you are on; Open full page moves the same conversation to a chat page. Details on Chatting with Jason.

Above the content, every page has a breadcrumb bar with the workspace name in the centre (click it to switch workspace), and on the right the theme toggle, Share workspace and the notifications bell.

What’s next