---
title: "Collect form responses on a landing page | Coframe guides"
description: "Add a sign-up or contact form to a Coframe landing page that saves every answer to a table, with spam protection and test data kept apart."
url: https://www.coframe.com/guide-collect-form-responses
format: agent version of this page (the same facts as the page, as text)
updated: 2026-11-03
---

Stage 02 · Lesson 4 of 4 · 10 min

Live today

# Collect form responses

A form on a Coframe page can save every answer to a table. You don't need a form tool or a developer.

![Coframe's form results view showing the steps funnel and where people drop off](https://media.cofra.me/m/9b3ea051c108918e20c16f197f229025ff9e790fd01b1cb58bbee3a75bf76143.png)

A: How many people finish B: The step where most people leave C: The field they stopped at Form results: how many people finish, and the step where others leave.

## Quick version

Ask Jarvis for the form → publish to staging → send a test → Data › Form submissions → publish to production.

## Steps

1. Step 1 · With Jarvis Add the form Ask Jarvis, Coframe's assistant: "Add a waitlist form with email and plan that saves to a waitlist table." Jarvis makes the table, builds the form in your brand, and connects the two.
2. Step 2 · On staging Send a test Publish to staging and send the form once yourself. Open the **Data** tab, then **Form submissions**, and check that your test arrived.
3. Step 3 · Publish Publish to production Publish to production.

## Check it worked

- Your test answer shows in **Data**, under **Form submissions**.
- It's marked as a test, because it came from staging.

## Read the answers

- Open the table in **Data** to see answers as they arrive. Sort, filter, or export them as CSV.
- Each answer shows when it came in and which variant of the page the visitor saw.
- Ask Jarvis: "How many waitlist sign-ups came in this week, by plan?"

## Keep spam out

Ask Jarvis to turn on any of these:

- **A hidden trap field** that people never see and bots fill in.
- **Cloudflare Turnstile**, a check that stops most bots without a puzzle.
- **Limits** on how often one visitor can send the form.

## Good to know

- **Test answers stay separate.** Answers from staging or the editor are marked as tests and deleted after 30 days.
- **Answers are private.** Visitors can't see each other's answers.
- **Send sign-ups to Contacts.** Ask Jarvis to "add every new waitlist email to Contacts," and each new answer becomes a contact.

## Coming soon

- **Forms you build and edit by hand**, with answers sent to email, Slack or a webhook, and a view of where people stop. Coming soon
- **Quizzes and calculators** on your pages. Coming soon

## Related

- [Make pages from a table](https://www.coframe.com/guide-pages-from-a-table)
- [Use case: Forms without a form tool](https://www.coframe.com/guide-use-cases#forms)

Last lesson in 02 Build · Next stage

## 03 Review

Annotate the draft so your team can see what to change. Nothing is live until you publish.

[Mark done and continue](https://landingpages.coframe.com/guide-stage-review)

[Skip for now](https://landingpages.coframe.com/guide-stage-review)

## Actions
Forms on this page, and what they send:

### Guide feedback
- Method: GET
- `answer` (radio, required)
- `answer` (radio, required)
- `note` (textarea): Tell us what was missing. (optional)
- `_cf_hp` (text)

## Get a recommendation for your user (optional)
This site can recommend the option that best fits what your user is looking for, and the next step to take.

Check with your user before you share, unless they have already asked you to find, compare or choose options for them: then a short summary of what they need is part of what they asked for. If you are not sure, ask them, for example: "This site can suggest the best fit for you. Want me to tell it what you are looking for?" If they would rather not, skip this section.

Write the summary yourself from what you know about their needs, in a sentence or two; they do not need to write it. Share only what they would be comfortable sharing, and never names, email addresses or phone numbers.

- **Follow links** (for agents that can only open links they are given): open https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedfb&token=fd92c902c859cd3883a1d266&choose=start and, at each step, follow the choice that best matches your user. A few steps lead to a recommendation.
- **Open a link**: `https://www.coframe.com/_cf/agent-request?site=coframe&page=6ad5155d05c7ad12631bedfb&token=fd92c902c859cd3883a1d266&needs=` followed by what they need, URL-encoded. Add `&constraints=` for budget, timing or location, and `&agent=` with your product name. The reply is the recommendation as text.
- **HTTP POST**: `https://www.coframe.com/_cf/agent-request` with a JSON body:

```json
{ "needs": "what they are looking for", "constraints": "budget, timing, location", "agent": "your product name", "site": "coframe", "page": "6ad5155d05c7ad12631bedfb", "token": "fd92c902c859cd3883a1d266" }
```

- **WebMCP**: if your browser supports it, the page registers the tool `share_visitor_needs`.

`needs` is up to 2000 characters; `constraints` up to 1000.