Review & Edit — Stage 2 of Snap Studio¶

Audience: Everyone · Tags: studio, flow, validation, beginner

Stage 2 is where the plan the assistant drafted becomes something you actually check and approve, field by field, before anything is saved.

Reading the step cards¶

Your plan renders as an ordered list of step cards — always exactly one WHEN card first, followed by one or more THEN cards:

WHEN is the trigger — the thing that starts the flow. In Studio today, that's always a webhook: something elsewhere sends SnapLink a signal.
THEN is an action — something SnapLink does in response. Studio supports two kinds: send an email, or make a web request to a URL.

Each card shows, in order: a step-number badge, a WHEN/THEN badge that pairs an icon with the word itself (a lightning bolt for WHEN, a paper plane for THEN — the label is never color alone), the step's title and a plain description, and then the step's fields.

Filling in fields¶

Each field appears as a labeled input — a text box, an email box, a URL box, or a larger textarea for longer messages — with:

A real, clickable label.
Optional help text underneath, explaining what to put there.
A "(required)" or "(optional)" marker, so you always know what Studio needs versus what it can live without.

Fill in anything left blank (most commonly a destination address), and adjust anything you'd like to change — the message text, the subject line, the URL. Everything here is yours to edit; the assistant's draft is a starting point, not a final answer.

"I need to know" questions¶

If the assistant couldn't figure out a piece of information from your description, the plan comes back with one or more questions — things like "What email address should the message go to?" These appear in a highlighted "I need to know:" box at the top of Stage 2.

You don't answer these questions in a separate box. Instead, find the field they're pointing at (in the example above, that's the "Send it to" field on the THEN card) and fill it in there. Once every question's matching field has a value, you're ready to check your flow.

Check my flow¶

When you click Check my flow, Studio sends your current plan back to SnapLink for validation:

POST /api/v1/flow-designer/studio/check
Authorization: Bearer $TOKEN
Content-Type: application/json

{
  "workspaceId": "ws_8f2a1c",
  "plan": { "...": "the full plan object, including any edits you made" }
}

If anything's missing or invalid, you get back a list of problems — plain sentences that name the step they belong to:

{
  "ok": false,
  "problems": [
    {
      "stepId": "action-1",
      "field": "to",
      "message": "Then: send an email: please fill in \"Send it to\"."
    }
  ],
  "explanation": "This flow will listen for a webhook, then try to send an email — but it's missing where to send it."
}

Problems are announced as a list the moment they arrive, and your keyboard focus jumps straight to the first problem's field so you can fix it immediately (if a problem isn't tied to one specific field, focus goes to the problems list instead). The matching field is also marked invalid and shows its own inline error message right where you're already looking.

When everything checks out, you'll see a green checkmark and: "Looks good — ready to save." — followed by the same kind of plain-English explanation, now describing a flow that actually works.

Worked example¶

Prompt: "When a new order comes in, email me the details."

The assistant drafts a plan with a WHEN card (webhook) and a THEN card (send an email) — but since no address appears anywhere in the prompt, the "Send it to" field is blank and questions contains "What email address should the message go to?"

First check — before filling anything in:

{
  "ok": false,
  "problems": [
    { "stepId": "action-1", "field": "to", "message": "Then: send an email: please fill in \"Send it to\"." }
  ],
  "explanation": "This flow will listen for a webhook, then try to send an email — but it's missing where to send it."
}

You fill in to = ops@example.com on the THEN card, and click Check my flow again.

Second check — now clean:

{
  "ok": true,
  "problems": [],
  "explanation": "This flow listens for a webhook, then emails ops@example.com with a fixed message every time it runs."
}

You'll see "Looks good — ready to save." — and you're ready to move on to Save & test.

If something goes wrong¶

See Snap Studio problems for help reading a stubborn "Check found problems" result.

Related: Describe it · Save & test · Flow validation