Build a Quest in the Dashboard

Open a project and click Quests in its header. The page lists every quest with a Draft or Published badge, its slug and its response count. Each row links to Responses and Analytics.

Members can do everything on these pages except archive a quest.

Start from a template

The Quests page has no blank “new quest” button. Every quest starts from a card under Start a new quest, the grid below the list.

Template	Steps
Untitled quest	One empty text question
NPS survey	A 0 to 10 range and a follow-up text box
Customer feedback	A five-way choice, then two text boxes
Lead qualification	Name, email, budget, timeline and notes
Event RSVP	Attendance, headcount, dietary needs and notes
Bug report	Severity, what happened, steps and when it started

Templates you saved yourself are listed first. Click a card and the editor opens on a new draft copy of it.

Add and edit questions

The left side is the Visual editor; the right side is a Live preview of the quest. The preview jumps to whichever question you open.

1. Set the shared header

   The Shared Header card at the top holds the form’s Heading and Subheading, Hide Header, Hide Progress and the progress bar’s Position (Top or Bottom). It also holds the Thank you screen Title and Message.

2. Add a question

   In the Add question row, click Text, Currency, Range, Date or Choice. The new question opens at the end of the list.

3. Fill it in

   Give it a Label and optional Helper text. Type settings change with the type: a text box can be multi-line, a range has Min, Max, Step, Default and a Unit suffix, and a choice has options you add with + Add option.

4. Order the list

   The arrows move a question up or down. The × deletes it after a “Delete question?” check that lists any later questions whose rules point at it; those rules are removed.

Each question has an ID, set when you add it. Answers are saved under it, and only the JSON tab can change it. In the visual editor, an option’s saved value is its label, so renaming an option changes the value that rules and analytics match.

Show a question only when an earlier answer says so

Every question after the first has a Visibility section.

1. Turn the rule on

   Click Show only if…. It starts with one condition on the question just before.

2. Pick the question and the test

   Choose the earlier question in When question, then an Operator: is, is not, is one of (choices only), is answered or is not answered.

3. Set the value

   For a choice, pick an option, or tick several for is one of. For a range or currency, type a number. For text, type the exact answer; for a date, pick the day.

4. Add more conditions

   + Add condition adds another. With two or more, Match switches between All (AND) and Any (OR).

The question’s card then shows a Conditional badge. Always visible removes the rule.

A rule that nests AND inside OR shows as Complex condition. Edit it on the JSON tab, or click Clear condition. Every operator and its edge cases are in Branching with visibleIf.

Edit the JSON

The JSON tab shows the whole quest as text. A few settings live only there:

1. required on a question.
2. minLength and maxLength on text, min, max and locale on currency, min and max on a date.
3. An option’s description and image, and imageAlignment.
4. submitLabel, nextLabel and backLabel.
5. Nested show-if rules.

A green “Valid” beside the tabs means the JSON passes. Otherwise the error shows there, the Save buttons turn off, and the visual editor waits until you fix it. The field list and what each type accepts are in Getting started with quests.

You can paste a whole quest here. A top-level id in pasted JSON is harmless: the embed always receives the quest’s own ID.

Save a draft or go live

Button	Does
Save (or Cmd/Ctrl+S)	Saves the draft. Your site keeps serving the live version
Save as new version	Saves the draft, snapshots it as the next version and makes that version live at once
Refresh preview	Rebuilds the preview from the draft on screen

Once a version is live, the Versions button reads Live · v1 and a strip reads “Embed loads from” with the quest’s definition URL. The definition is cached for up to 60 seconds.

The Theme menu over the preview only changes the preview, and only in your browser. To style the quest on your site, see Design and publish a quest theme.

Roll back or unpublish

Click Live · vN, or Versions before the first publish. The list shows each version’s number, date and note, with Live on the one being served.

1. Make live on an older row serves that version again. Your draft does not change.
2. Make this a draft (unpublish) stops serving the quest. The embed then shows “Couldn’t load form”, and new responses are refused.

Each response is tied to the version that was live when it started.

Save it as a template

Save as template asks for a Name and an optional Description and saves the current draft. Templates are private to you and show first in every project’s template grid. The dashboard cannot rename or delete one.

Archive a quest

On the Quests page, the owner clicks Archive on the row and confirms. The quest is unpublished, stops serving and refuses new responses. It moves to Archived, a folded list at the bottom of the Quests page, newest first. Each row there shows the archive date and the response count, with links to Responses and Analytics. Both still work, and so does the Platform API. The editor does not open an archived quest.