Forms

A form is a public page at /f/:slug that collects structured responses from anyone with the link. No Instagram connection, no code.

What a form is

Each form lives at its own itsjustbig.com/f/<slug> address. Visitors fill it out and submit — you see the responses in your dashboard. That's the whole loop.

Create a form

Open Forms in big and click New form.
Give it a title.
Add your fields — see Field types for what's available.
Set status to active when you're ready to accept submissions.

Already have a form in Typeform? You can import it instead of rebuilding it: open Forms → Import, connect your Typeform account, and pick a form to bring over. You can also keep a form in Typeform and have its new responses sent to big See Typeform for both.

Form settings

Title — shown at the top of the public form.
Status — draft, active, or closed. Only active forms accept submissions; draft and closed forms still exist and can be viewed in your dashboard, but visitors can't submit to them.
Slug — auto-generated from the title when you create the form. There's no way to change it afterward, so don't rely on the slug spelling out something you might want to edit later.

Delete a form

Deleting a form takes everything attached to it: every saved version of its schema, every response it has collected, and its whole view and funnel history. Its /f/<slug> address stops resolving. There is no undo and no trash — rebuilding the form gets you the questions back, never the answers.

You need the editor role or higher, the same floor as deleting an automation. The control is on the form row's overflow menu and in the builder's header, and the confirmation names how many responses go with it, so you see the cost before you agree to it.

If you only want to stop accepting submissions, set the status to closed instead. That keeps the form, its responses and its public page; it just stops taking new answers. Delete is for a form you want gone.

Deleting is on the developer surface too, mirroring automation delete exactly:

CLI — big form:delete <id>, scope forms:write. Like big rule:delete, it takes no confirmation flag — it deletes as soon as you press enter. See the command reference.
Local MCP (big mcp) — the big_form_delete tool, scope forms:write, editor+. Like big_rule_delete it is confirm-gated: the call refuses without confirm: true, so a model can't delete a form on the strength of something it read in a DM.
REST — DELETE /api/forms/:id, scope forms:write, editor+. See the API reference.
Remote MCP — not offered, like every other delete. The hosted server carries no destructive verbs.

An example form left over from onboarding deletes exactly like any other, and nothing puts it back.

Pages and logic

A form isn't limited to a single screen. You can split it into multiple pages (up to 20) — use + Add page at the top of the canvas — and add conditional logic:

Show a field only when it's relevant — a field can be set to appear based on an earlier answer.
Branch between pages — at the end of a page, send the respondent to a different page (or straight to submit) depending on what they answered.

This lets one form ask follow-up questions that only apply to some people. You build it visually in the form editor — there's nothing to write. Conditional logic covers the rules in detail.

Each page can carry an optional title and description, set in the page editor; the description shows under the title as plain text (up to 1000 characters). On a one-page form it shows under the form's title.

The confirmation screen

You can customize what a respondent sees after they submit:

A custom heading and message (your own thank-you text).
An optional button, with your own label, that sends them somewhere next.

Leave these blank and big shows a standard thank-you.

Where the button sends people

In the form editor, open the submit step at the end of the flow and pick one of three destinations:

Nothing — no button at all, just your thank-you text.
A link — any http(s) address you paste. Your shop, your newsletter, a booking page: anything outside big
One of my link pages — pick one of your workspace's link pages from a list, instead of pasting its address.

Whichever you pick, you give the button its own label — "See everything else", "Book a call". The button opens in the same tab: this is the end of your funnel, so the visitor moves on rather than leaving a dead thank-you screen stacked behind them.

The setup this exists for: one link in your Instagram bio points at the form, so the bio link captures a lead, and the thank-you offers your link page — everything else you sell — to the person who wanted more than one thing.

Picking a link page instead of pasting its URL

Two things change when you pick a page rather than typing its itsjustbig.com/t/<handle> address into A link:

Renaming the handle doesn't break the button. big stores which page you picked, not its address, and looks the current address up each time the thank-you renders. A pasted URL would break the moment you rename: the old handle stops working immediately, with no redirect, and can be claimed by someone else — see Renaming a handle.
Only a published page shows a button. You can pick a draft — the picker says so when you do — but the button stays hidden on the live thank-you until you publish that page. The same goes for a page you later unpublish or delete: the button disappears rather than dead-ending, and visitors are never told why something is missing.

What's not there yet

To set expectations up front, a form today does not support:

A description for the form as a whole (each page has its own optional title and description instead)
An automatic redirect after submit — the confirmation button is always something the visitor taps, including when it points at one of your link pages; the page never forwards on its own
A count of taps on that button. A link page records the visit as a page view, but nothing splits those views by where they came from (see Link page stats), and a tap on an external link isn't recorded at all
Logo, color, or other branding configuration

If you need any of these, they're not available yet — don't build a workflow that depends on them.

Fields

Forms support 13 field types, each with its own validation. See Field types for the full list.

Once a form is active, share the public link or turn it into a trackable short link. See Share your form.

Limits

1–100 fields per form, across 1–20 pages.
Each field needs a unique field ID.
Submitted answers are capped at 16KB total per submission.
There's no plan-based cap on the number of forms or fields — every plan gets the same limits above.
Submissions count against your plan's weekly cap, which they share with automation steps. Views don't count; only a stored submission does.
A submission is never refused for being over the cap. Going over the cap never costs you a response: every submission is accepted and stored, on every plan, at any usage level. The visitor sees the same thank-you screen either way, and only ever sees it once the response is saved. See Anti-spam for the rate limits, which are separate from the cap.
Over the cap, a response is stored locked. You still see that it arrived, when it arrived, and it still counts in your totals and conversion rate. You don't see the answers, who submitted it, or which link or campaign it came from, until it unlocks.
A coaching practice's Client check-in form is different. It stores no response, never counts against the cap, and drops a submission that has no valid link code from a client's update link. See The client check-in form.
Locked responses unlock at the weekly reset, oldest first, as far as the new week's budget stretches. Upgrading unlocks all of them immediately.
The unlocked backlog is served before your automations. Releasing locked responses draws on the new week's budget first, so DM and comment automations only start firing again once the backlog has been cleared. A backlog bigger than your weekly cap drains over several weeks, and your automations stay quiet the whole time. See Plans.

Forms

On this page