---
title: "Linkbreakers + Tally: QR forms for privacy-first teams, each answer on the visitor"
description: "Connect Tally with an API key and every Tally form behind your links and QR codes gets a hidden lbid field and a signed webhook, so each response lands on the exact visitor who scanned, with their email, name, phone and answers. Setup, what is matched and synced, and the Assistant and MCP tools."
canonical: "https://linkbreakers.com/help/article/linkbreakers-tally-integration-qr-forms-for-privacy-first-teams"
last-updated: 2026-11-09
---

# Linkbreakers + Tally: QR forms for privacy-first teams, each answer on the visitor

> Connect Tally with an API key and every Tally form behind your links and QR codes gets a hidden lbid field and a signed webhook, so each response lands on the exact visitor who scanned, with their email, name, phone and answers. Setup, what is matched and synced, and the Assistant and MCP tools.

:::try-ai-prompt {"prompt":"Check my Tally forms again and tell me which ones still need something from me","description":"Check your Tally forms with the Assistant.","target":"assistant"}:::

## Short answer

Linkbreakers connects to Tally directly. In the dashboard, open **Integrations**, pick **Tally**, paste a Tally API key and select **Connect Tally**. Linkbreakers then finds every Tally form your links redirect to, adds a hidden field named `lbid` to each one and creates a webhook for it. When someone scans your QR code, the redirect carries their visit ID into the form, and when they submit, the response is added to that exact visitor: email, name, phone and every other answer.

No Zapier, Make or copied webhook is needed. The integration is available on every plan.

## Quick summary

- Connect once per workspace with a Tally API key
- Tally forms behind your links are found automatically from the [redirect steps](/workflow-steps/redirect) of your workflows
- Linkbreakers adds the hidden `lbid` field and a signed webhook to each of those forms
- Each response is matched to the exact visit that opened the form, not guessed from timing
- Email, first name, last name and phone go to the visitor's standard fields; other answers become visitor attributes named after the question
- Responses come in as soon as the form is submitted
- Responses with no visit ID, such as a form opened directly, are skipped and counted
- Also managed from the Assistant, the MCP server or the REST API

## How it works

1. You connect Tally. Linkbreakers looks at the redirect steps of your links' workflows and picks up every destination that is a Tally form: `tally.so/r/<form id>`, `tally.so/forms/<form id>` or `tally.so/embed/<form id>`.
2. For each of those forms, Linkbreakers adds a hidden fields block with a field named `lbid`, unless the form already has one, then creates a webhook for the form's responses. Running it again never adds a second webhook.
3. When someone goes through the link, the redirect adds `lbid=<visit ID>` to the form address, and Tally fills the hidden field from it.
4. When they submit, Tally sends the response to Linkbreakers. The webhook address holds a secret, and the request's `Tally-Signature` is checked too, so anything else is refused.
5. Linkbreakers reads the `lbid` hidden field, finds the visit, and adds the answers to that visitor.

Once a day, Linkbreakers checks the forms again: a hidden field or a webhook removed in Tally is put back, and a form no longer behind a covered link loses its webhook.

## Connect Tally

1. In Tally, open **Settings**, then **API keys**, and select **Create API key**.
2. In Linkbreakers, open **Integrations** in the dashboard and pick **Tally**.
3. Paste the key in **API key** and select **Connect Tally**. Linkbreakers checks the key against Tally before storing it, and the forms behind your links are prepared at once.
4. Check **Forms found**. Each form shows the link it is behind and a green check when it is ready. A form that needs something from you says what.
5. Optionally, set **Where** and **What comes in**, then save.

The key is encrypted when it is stored and never shown again.

To have a new form picked up, add a redirect to it in a link's workflow. Then select **Check forms again** on the Tally page, or wait for the daily check.

## What gets synced

| Tally answer | Linkbreakers visitor |
|---|---|
| Question whose label contains "email", "e-mail" or "courriel" | Email |
| Label containing "first name", "firstname", "prénom", "prenom" or "given name" | First name |
| Label containing "last name", "lastname", "nom de famille", "family name" or "surname" | Last name |
| Label containing "phone", "téléphone", "telephone", "mobile" or "cell" | Phone |
| Any other answered question | A visitor attribute named after the question label |

Choice answers come in as the text of the options chosen, not their IDs. A question labelled only "Name" or "Full name" is not split into first and last name: it is kept as an attribute with that label. Empty answers are left out, and the `lbid` hidden field itself is not stored as an answer.

## Which visitors and which links

The Tally page has the settings Linkbreakers integrations share, adapted to answers coming in:

- **Where**: **All links**, or **Selected links**, directories and tags. Only the forms of the links you choose are prepared, and only their responses are added to visitors.
- **When**: as soon as someone submits the form. There is nothing to choose.
- **What comes in**: **Every answer**, or **Only some answers**, where you pick the fields to keep, such as Email and Phone. Choosing only some answers is how you keep personal data you do not need out of Linkbreakers.

A response is skipped, and counted under **Skipped** on the page, when it has no visit ID (the form was opened directly, not through your link), when the visit belongs to another workspace, when it came through a link outside **Where**, or when none of its answers are among those you chose to keep.

The **Activity** section shows **Responses**, **Visitors enriched**, **Skipped** and **Last response**.

## Pause and disconnect

**Pause** stops responses from coming in: links stop adding the visit ID, and responses that arrive are ignored. **Activate** turns it back on.

**Disconnect** stops responses and deletes the Linkbreakers webhooks from your Tally forms. The hidden `lbid` field stays in the forms, and answers already added to visitors stay on them.

In a link's workflow, a redirect to a Tally form shows the Tally logo when its responses are coming in, or a card that says **Not connected** or **Not syncing** with a button to fix it.

## Manage it from the Assistant, MCP or the API

Connecting needs you in the app, to paste the API key. Everything after that can be done by an agent.

**Assistant**: in the dashboard, ask "Which of my Tally forms are ready to match responses?" or "Only bring in email from Tally".

**MCP server**: an agent connected to the [Linkbreakers MCP server](/help/article/mcp-server-setup) has `form_integrations_list`, `form_integration_get`, `form_integration_forms_list`, `form_integration_forms_prepare`, `form_integration_update` and `form_integration_disconnect`, with the tool `TALLY`.

**REST API**, with a token that has the `integrations:write` scope:

```bash
curl -X POST https://api.linkbreakers.com/v1/form-integrations/FORM_TOOL_TALLY/connect \
  -H "Authorization: Bearer $LINKBREAKERS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"apiKey": "your-tally-api-key"}'

curl -X PATCH https://api.linkbreakers.com/v1/form-integrations/FORM_TOOL_TALLY \
  -H "Authorization: Bearer $LINKBREAKERS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"delivery": {"visitorData": "INTEGRATION_VISITOR_DATA_SELECTED", "visitorAttributeKeys": ["$email"]}}'
```

## Limits and caveats

- **One Tally account per workspace**
- **Only forms behind a redirect step** in a link's workflow are prepared. A form you share by other means brings nothing in
- **Only `tally.so` addresses** are recognized. Tally forms on a custom domain are not
- **Responses without a visit ID are skipped**, for example when someone opens the form from a bookmark or a forwarded address
- **If Tally refuses the hidden field**, the form shows "Add a hidden field named lbid to this form in Tally." Add it, then select **Check forms again**
- **Linkbreakers edits your forms**: it adds the `lbid` hidden field and a webhook. Disconnecting removes the webhook, not the field
- **One way.** Responses come into Linkbreakers; nothing is written back to Tally except the hidden field and the webhook
- **Retargeting pixels** of your workspace fire on every link, including those that open a Tally form. Keep them off if your respondents should not be tracked by ad platforms; see [retargeting pixels](/help/article/retargeting-pixels-meta-google-tiktok-linkedin-and-google-tag-manager)

## Frequently asked questions

### Do I still need Zapier or a Tally webhook of my own?

No. Linkbreakers creates its own webhook on each form through Tally's API and adds the responses to the visitor who scanned.

### How does Linkbreakers know which visitor filled the form?

The redirect puts the visit ID in the form's `lbid` hidden field. Tally sends it back with the response, so the match is exact, even when many people scan at the same time.

### Can I keep only the email and leave the other answers in Tally?

Yes. Under **What comes in**, choose **Only some answers** and keep Email. The other answers stay in Tally only.

### Do I have to add the hidden field myself?

No. Linkbreakers adds it through Tally's API. Only if Tally refuses does the page ask you to add it.

### What happens when I disconnect Tally?

Responses stop coming in and the Linkbreakers webhooks are deleted from your forms. Answers already on visitors stay.

## Sources

- Linkbreakers Tally integration page, API and MCP tools, checked in the product on 2026-11-09.
- Tally API documentation: https://developers.tally.so

## Last reviewed

2026-11-09 by Laurent Schaffner.
