big docs
Forms

Typeform

big connects to Typeform in two ways. You can import a form, which copies its questions into a big form once. And you can receive responses, which sends every new submission on a Typeform form to big as it happens, so you can keep collecting applications in Typeform.

Both use the same Typeform connection.

Connect Typeform

Open Forms → Import and choose Connect Typeform. Typeform asks you to approve big's access, then sends you back. Connecting needs the admin role.

big asks Typeform for permission to:

  • read your account and your forms, to list and import them
  • read responses and manage webhooks, so big can receive new responses for the forms you choose

A Typeform account can be connected to one big workspace at a time. If it's already connected in another workspace, disconnect it there first.

Disconnect Typeform

An admin disconnects Typeform with Disconnect on the Typeform card of the Connect page, or with big typeform:disconnect (it asks before it acts) or the local MCP tool big_typeform_disconnect (it needs confirm: true). big removes the webhooks it added to your Typeform forms and deletes its stored sign-in, so importing stops and new responses stay in Typeform. The forms you already imported, and the responses big already received, stay in big Connecting again is done in the dashboard, under Forms → Import.

Approve once more if you connected before

Connections made before response intake existed only allowed importing. They keep importing exactly as before, but they can't receive responses until Typeform approves the new permissions.

If yours is one of them, Forms → Import and Connect both show a Reconnect Typeform prompt. An admin chooses it, approves in Typeform, and is done. Nothing you already imported changes.

Import a form

Once connected, Forms → Import lists every form on your Typeform account, one card per form. Choose Import → on one to copy its questions into a new draft form in big Importing needs the editor role.

An import is a copy, not a sync. Re-importing the same form later updates the big form and saves a new version.

Re-importing is refused if you've since changed the form's shape in big: added branching or a custom confirmation screen, or added, removed or renamed a page, or added or changed a page's description. Typeform's copy would replace that work, so big says so and leaves the form alone. Edit the form in big instead. Changing questions in big doesn't block a re-import; the re-import replaces them with Typeform's.

Import from the CLI or an agent

Importing works over an API token too, with the editor role, so the CLI and connected agents can do it:

  • big form:import --list lists your Typeform account's forms and the big form each one was imported into. Agents on big's MCP servers use big_typeform_forms_list, or list_typeform_forms on the remote server.
  • big form:import <typeformFormId> imports one as a draft. Agents use big_form_import_typeform, which is on the local server only.

A new import from a token counts against the 100-form ceiling, the same way creating a form over the API does. A re-import works as above, with one more rule: it's refused while the big form is live, because a token never changes what a published form shows. Unpublish it first, or re-import it here on Forms → Import. Connecting Typeform can only be done in the dashboard, so until it's connected the CLI and agents are told to connect it on Forms → Import.

What carries over

An import copies the questions, their order, and whether each one is required. It doesn't copy Typeform's logic jumps, hidden fields, endings, images, or theme.

In TypeformIn big
Short text, Long text, Email, NumberThe same type
Phone numberPhone
WebsiteWebsite
DateDate
Multiple choiceSingle choice, or Multiple choice if it allows several answers, with an Other answer if it has an Other option
DropdownDropdown
Yes/NoSingle choice with Yes and No
LegalSingle choice with I accept and I don't accept
RatingRating, up to 10
Opinion scaleRating with the same range (starting at 0 or 1) and its end labels
Net Promoter Score®Rating from 0 to 10
Picture choiceSingle or Multiple choice with the labels only; the pictures are dropped
Contact infoOne question per part (name, email, phone and so on)
Question groupA page of its own, titled with the group's title and description
StatementThe title and description of the page that starts with the questions after it

Pages. Each question group becomes its own page, and a statement starts a new page. Questions that sit between groups go on a page of their own. A group inside a group is merged into its parent's page, and a form that would need more than 20 pages keeps 20, with the extra questions on the last one. A statement with no question after it is dropped.

Identity. The first email question becomes the form's identity field. If there's no email question, the first phone question does, and big doesn't create clients from a phone identity.

What's skipped. Payment, Calendly, Ranking, Matrix, Multi-format and File upload questions have no big equivalent and aren't imported, nor is any question type big doesn't recognize. A form holds up to 100 questions, so anything past the 100th is dropped too. After an import, the form says how many questions changed shape or couldn't be brought over.

Receive responses from a form

On Forms → Import, an admin sees four numbered steps under each form's title, in the order you set them up:

  1. Receive responses: a switch that brings the form's new Typeform submissions into big as responses.
  2. Back-fill past responses: copies in what the form collected before it was receiving.
  3. Who fills it in: Anyone, or Existing clients for a form only your clients get.
  4. What goes to Notion: the answers the form's Notion pages may show.

Steps 2 to 4 are shown on every form, so you can see what each one does before you need it. On a form that isn't receiving they are locked and say Turn on Receive responses first. Steps 3 and 4 also need the form imported into big, and say Import this form first. until it is. A step whose settings couldn't be read says Couldn't load this step. Refresh to try again. big loads these settings for your 200 newest imported forms, so on an older form steps 3 and 4 say This page loads settings for your 200 newest imported forms, and this form isn't one of them. Refreshing doesn't change that.

The first time you open Forms → Import, Dot walks you through the page, including each step an admin sees. Press Show me around in the corner to take the tour again.

Turn on Receive responses for every form whose submissions you want in big, such as your client application. You don't need to import the form first: turning it on imports the form as a draft if big doesn't have it yet. The switch flips straight away and says Connecting to Typeform… until Typeform has accepted the change. If Typeform refuses, the switch turns back off and says why.

Choosing forms for intake, and the other three steps, need the admin role, and they can only be done in the dashboard. Editors and viewers don't see the steps. Each form shows them one status line instead: Receiving responses, with when the last response arrived, or Not receiving responses. API tokens, the CLI and connected agents can't turn it on or off.

What happens when you turn it on:

  • big creates a private signing secret for that form and registers a webhook on the form in your Typeform account. You'll see it under the form's Connect → Webhooks in Typeform.
  • Each new submission is sent to big, stored, then checked against that secret before it is used. Anything that isn't signed with the secret is discarded and never becomes a response.
  • If Typeform delivers the same submission twice, big keeps one copy.

Usually within moments, and at most about five minutes later, each received response becomes a response on the imported big form, so you'll find it on that form's Responses tab next to responses from big's own form page. Receiving responses works alongside an import: if the imported big form is deleted later, big holds the form's responses for up to a week and adds them once you import it again.

Each form that is receiving responses shows, under the switch, when its last response arrived, such as Last response received 5m ago, or No responses received from Typeform yet. before the first one. If you've submitted a test response and the line hasn't changed after a minute, check the form's webhook in Typeform.

To stop, turn the switch off and confirm. big removes the webhook from Typeform and stops accepting deliveries for that form. Responses big is still holding for the form, such as ones waiting for you to import it, are dropped, and new responses stay in Typeform. Disconnecting Typeform stops intake for every form.

A workspace can receive responses from up to 50 Typeform forms. A form that another big workspace already receives responses from can't be turned on here, because Typeform lets big register only one webhook on a form; big says so instead of taking the form over. Turning a form off in one workspace never removes the webhook another workspace relies on.

Turning intake on sends submissions made from then on. To bring in the responses a form collected before that, use Back-fill past responses.

Answers big can't store. A received answer that doesn't fit its big question is left out, and the rest of the response is still saved. An Other answer is kept when the big question takes an Other answer, which an import sets up for every Typeform question with an Other option. On a form imported before that, re-import it to pick up the Other answers, or, if the re-import is refused, tick Allow an Other answer on the question in big: until then, a Multiple choice question keeps the options the person ticked and drops only their Other text, and a Single choice question answered with Other is left blank.

Back-fill past responses

Once a form is receiving responses, an admin can bring in the responses it collected before intake was turned on. On Forms → Import, go to step 2, Back-fill past responses, and choose Start back-fill.

big reads the form's completed responses from Typeform, newest first, up to the moment you start the back-fill, and adds each one to the imported big form's Responses tab. It works in the background, about 200 responses every five minutes, so a form with thousands of responses takes a few hours. The line under the button shows how far it has got, with a bar when Typeform has said how many responses there are, such as Back-filling: 120 of 340 stored, 3 skipped., and Back-fill done once it has read the whole history.

  • Each response is stored once. A response big already has, from the webhook or an earlier back-fill, is skipped. That also means a back-fill catches any response the webhook missed. Back-filling the same form again adds nothing new.
  • Only finished responses. A response someone started and didn't submit is skipped.
  • Back-filled responses don't count toward your plan. They never count against the weekly usage cap and are never locked.
  • No action items. A back-filled response doesn't add an intake card to your Action items board, so a long history doesn't fill it with cards.
  • Clients. On a form that creates clients from responses, back-filled responses are matched to clients by email and can add applicants, the same as new responses.
  • Erased clients stay erased. A response submitted on or before a client was erased is never brought back.

Do your application form first. Back-fill the form that creates your clients before any form set to Who fills it in → Existing clients, so their past responses can match the clients the application form creates. Step 2 shows this reminder on a form until it has been back-filled.

If it pauses or stops. Typeform limits how fast big can read responses. When big hits that limit, the line says Paused by Typeform's rate limit, and big carries on from where it stopped about five minutes later. If Typeform asks big to reconnect, the form stops receiving responses or is removed from big, or another big workspace starts receiving the form's responses, the back-fill stops and says why. Reconnect or fix the form, then choose Start back-fill again. Responses already stored are skipped.

Back-filling needs the admin role, and it can only be done in the dashboard. API tokens, the CLI and connected agents can read back-filled responses like any other response, but can't start a back-fill. A form that is your client check-in form can't be back-filled.

Create clients from responses

If your workspace keeps client records, each form has a Create clients from responses switch at the top of the form's page. It works the same for Typeform forms you receive responses from and for big's own forms. Changing it needs the editor role, and it can only be done in the dashboard.

  • On: every response is matched to a client by email. If there's no match, big adds a new applicant with that email.
  • Off: a response is still linked to an existing client with the same email, but big doesn't add new clients.

The CLI and connected agents can read whether a form creates clients (big form:intake <id>), along with the same warning the dashboard shows when the form has no email question, but they can't change it. In a workspace that doesn't keep client records, they're told so instead.

The form needs an email question

Clients are matched and created by email only. If big can't find an email in a response, nothing is matched or created: the response is saved without a client.

  • A Typeform form gives big an email from its first Email question, or from a hidden field named email (for example on a pre-filled link). Either one is enough, and big checks for both each time you import the form.
  • A form built in big needs a question set as the form's identity. An Email question always works. A Short text identity only creates a client when the respondent types an email address, so big tells you to change it to an Email question. A phone number can't stand in for an email, so a form whose identity is a phone question can't create clients.

When Create clients from responses is on and big can't get an email from the form, it shows a warning beside the switch and on Forms → Import: No email question, so no clients will be created. When the switch is off, the same place shows a quieter note, No email question, so responses can't be linked to clients., because linking to an existing client needs an email too.

  • A Typeform form: add a required Email question in Typeform (or a hidden field named email), then choose Import again on Forms → Import. The warning goes away after that import.
  • A form built in big: add an email question and set it as the form's identity. For a Short text identity, the warning reads Only answers typed as an email will create a client.; change that question to an Email question.

Responses that arrived before you fixed the form stay without a client.

Matching runs within moments of each received response, and about every five minutes as a backup. On Forms → Import, a Typeform form that is receiving responses shows a Create clients from responses → link under its title that takes you to the switch on its imported big form.

Forms your existing clients fill in

Some forms are filled in by people who are already your clients, such as a revamp or re-onboarding form. On Forms → Import, an admin sets step 3, Who fills it in, to Existing clients on a form that is receiving responses and is imported into big Anyone, the default, means a response can add a new applicant when Create clients from responses is on.

  • Never creates clients. Each response is matched to a client by email, as usual, but big never adds a new client from it. Choosing Existing clients turns the form's Create clients from responses switch off, and the switch can't be turned back on until you choose Anyone again.
  • Marked as unverified in Notion. A matched response's page in the Form responses database says Unverified (matched by email), because an email alone doesn't prove the response came from that client. That is true of a response matched by email on any form; only a response that created its client, or was sent through the client's own link, says Verified. Needs work asks you to check it.
  • Never changes the client's chart. A matched response is linked to the client and nothing else about the client changes.

For ongoing revamps, use the client's update link instead. Matching by email is the best big can do for past responses. For new ones, add the big_update hidden field to the form and send each client their own link, as in Use a Typeform form for client check-ins: every submission is then tied to the right client by their link, not by the email they type. That is a change you make to the form in Typeform; big doesn't make it for you.

Choose which answers reach Notion

If your workspace has Notion connected, each response matched to a client gets a page in the Form responses database. By default that page shows no answers. On Forms → Import, step 4, What goes to Notion, lists the questions whose answers are shared, such as 5 of 27: followed by their labels, or No answers go to Notion. when none are, so you can check what reaches Notion without opening anything.

To change it, an admin chooses Choose answers on a form that is receiving responses and is imported into big A dialog opens with every question on the form, under a reminder that nothing reaches Notion until you tick it:

  • Tick the questions whose answers the page may show. The count at the top, such as 3 of 27 selected, follows your ticks, and Select all and Select none tick or clear the whole list.
  • Choose Save answers to keep the change. Nothing changes in Notion until you save.
  • Cancel, the close button or Escape with unsaved ticks asks Discard unsaved changes? first. Choose Keep editing to go back, or Discard to close, and Notion keeps the answers it had.

What the choice means:

  • Only the ticked answers appear, in the page's body. Every other answer stays in big, on the form's Responses tab.
  • Leave out anything medical or private. Everyone who can open the Form responses database in Notion can read the answers you tick.
  • Unticking a question removes its answer from every page of that form on the next syncs.
  • If a ticked question is renamed or changes type, in big or by re-importing the form, its answers stop going to Notion. Step 4 shows a badge such as 2 need re-approval. In the dialog, the question is listed under 2 answers need re-approval and marked Changed. Tick it again and save to share it.
  • Answers can be chosen on up to 200 forms. Clear the answers of a form you no longer use to choose them on another.
  • File uploads are never imported, so a file never reaches Notion.

Setting who fills a form in and choosing its answers need the admin role and can only be done in the dashboard. API tokens, the CLI and connected agents can't change them.

Use a Typeform form for client check-ins

A coaching practice can collect client check-ins with its own Typeform form instead of big's ready-made Client check-in form. Each client's link in the Update link column of your Clients board in Notion then opens your Typeform form, and every submission adds a client update to that client, the same as a check-in through big's form. There's no switch to flip in big: big finds the form by a hidden field.

Set up the form

  1. Connect Typeform if you haven't (see above). The connection needs the response and webhook permissions, so approve once more if Typeform asks.

  2. In Typeform, open the form's Logic → Hidden fields and add a hidden field named exactly big_update. It tells big that the form is your check-in form, and it ties each submission to the right client.

  3. Give each number question one of these question references (in Typeform, the question's Question reference under its settings):

    Question referenceRecords
    weight_kgWeight, answered in kilograms
    weight_lbWeight, answered in pounds (big stores it in kilograms)
    body_fat_pctBody fat, 2 to 75 %
    sleep_hoursAverage sleep per night, 0 to 24 hours
    daily_stepsAverage daily steps, up to 100,000
    adherence_pctHow closely the client followed the plan, 0 to 100 %

    Use a Number or Opinion scale question for these. Ask for weight with only one of weight_kg or weight_lb: the unit comes from the reference, so the client doesn't pick one. A number from any other kind of question, or under any other reference, goes into the client update note as text and is never recorded as a metric.

  4. Add any text questions you like, such as How did the week go?, Wins and Struggles (references week_summary, wins and struggles are a good choice). Their answers go into the client update note.

  5. Publish the form.

big checks your Typeform forms about every 15 minutes. Once it finds the form, it registers a webhook on it, and on its next run each client's Update link cell changes to a link that opens your Typeform form. Clients who already have big's link get the new one in that run too, so send them the new link.

How it behaves

  • One check-in form per workspace. If several forms declare big_update, big uses the most recently updated one. A newer form replaces the current one when you add the hidden field to it.
  • A form you already receive responses from becomes your check-in form when you add big_update to it: from then on its submissions are client check-ins, and it stops storing responses and creating applicants. Remove the hidden field and it goes back to being an ordinary form you receive responses from, on big's next check.
  • The form is never imported. A check-in form big found by itself doesn't appear on your Forms list, and its submissions never become responses.
  • On Forms → Import the check-in form's Receive responses switch is on. Turning it off turns Typeform check-ins off and big goes back to its own form. To use the Typeform form again, edit and republish it so big finds it on its next check.
  • Each check-in counts once. If Typeform sends the same submission twice, big records it once.
  • Removing the form. Remove the hidden field, delete the form or disconnect Typeform, and big goes back to its own check-in form: every Update link cell changes to big's form on its next run.
  • A form another big workspace already uses is skipped: big never moves its webhook, so that workspace keeps receiving its submissions, and your current check-in form stays in place.
  • A submission without the client's link code (someone opening the form's plain address) is discarded and stores nothing in big It still counts as a response in Typeform.

Typeform response limits

Typeform plans limit how many responses a form can collect, and every submission counts, including ones big discards because they came without a valid link code. So a link that gets passed around can use up your Typeform responses. See Typeform's pricing page for your plan's limit. big's own check-in form has no response limit, which is why big uses it unless you set up a Typeform form.

Typeform | itsjustbig