How every part of Papias works.

Type the questions as you would ask them, open the form, share the link.

What each kind asks for, what it checks, and what it stores.

Describe the form in a sentence; then say what to change.

Photograph the paper form with your phone, or scan it, and the builder reads it into questions you can edit.

Build first, sign up when you open the form; email or Google.

People answer the form in a chat instead of boxes: your questions in your words, every answer checked.

Conditions on questions, and which kinds they can look at.

Split a long form into pages, or show one question per screen.

A set of questions asked once per attendee, child or item.

A number behind each option, a Calculation that adds up as people type.

A message or a redirect, and different ones for different answers.

A question, help text or ending that repeats what the person said.

Make the form look like yours.

The rest of the Settings tab.

The link, its preview, four ways to embed, and your own domain.

Summary, table, filters, stars and notes, one response at a time, where people stop.

What the spreadsheet contains, and one row per group item.

Who gets told, and the limits.

Each response sent on as JSON, or as a message in a channel.

A spreadsheet per form in your own Drive, a row per response.

A Payment question, paid on Stripe Checkout into your own Stripe account.

Who is in a workspace, what each plan allows, and billing.

Google Analytics or Meta Pixel on a form; every saved version, restorable.

What the Ask Nell button can do and cannot do, on the site and when you are signed in.

How bots are caught without a CAPTCHA, what we store and where.