# Tally Forms integration: every submission checked, routed and recorded.

> SBD connects Tally Forms, the form builder at tally.so, to the CRM, database, messaging and approval workflows that teams of 1 to 1,000 people use, so each submission is validated, deduplicated and routed to the right owner. This page is about tally.so; for the TallyPrime accounting system, see our separate Tally page. Workflow automation builds start at $1,000, with the fixed price set after a $500 Automation Audit that is credited to the build.

- Canonical: https://smallbaydigital.com/integrations/tools/tally-forms/
- Publisher: SmallBay Digital

## What SBD builds with Tally Forms

Tally makes it quick to publish a good-looking form. What happens to the answers is usually less tidy: an email to a shared inbox, a spreadsheet nobody owns, or a native integration that creates a duplicate contact every time the same person fills in a form twice. We build the workflow behind the form.

Typical builds: enquiry forms that find or create the contact in the CRM, attach the answers and assign an owner by region or product; application and onboarding forms that create a record in Airtable or Supabase and open a review queue; quote request forms that start a quotation; and a confirmation sent on WhatsApp or email from the workflow instead of the form, so the message can use data from your own systems. Hidden fields carry the source, campaign or record ID so the workflow knows where each submission came from.

We have not published a case study built on Tally Forms. Similar form-led builds on other tools include a [photo studio project system](https://smallbaydigital.com/case-studies/photo-studio-project-management/) fed by a Fillout enquiry form, and a [lead capture demo](https://smallbaydigital.com/portfolio/demos/agency-lead-capture/) built on Typeform. Tally Forms is a different product from TallyPrime accounting, which has its own [Tally page](https://smallbaydigital.com/integrations/tools/tally/).

## When Tally Forms is the right choice, and when it is not

Tally suits teams that want unlimited forms and submissions on a free plan, with logic and hidden fields, and webhooks included for every user. Tally says it is made and hosted in the EU and stores all form data in Europe, which helps teams with EU data requirements.

We will recommend something else when:

- Respondents must log in and edit their own past submissions; a portal on Softr, Noloco or a custom app fits better.
- The form must write directly into a system with complex validation, such as an ERP; a custom form in your app can enforce the rules before submission.
- You need single sign-on for form editors or an audit trail of form changes; Tally's pricing page does not list these.
- A form already built in your CRM or helpdesk does the job and keeps data in one place.

## Tally webhooks, API limits and plans

Each new submission sends a POST with a JSON body containing the event ID, form details and a fields array with each question's key, label, type and value. A signing secret is optional; when set, a Tally-Signature header carries an HMAC-SHA256 of the payload, base64 encoded. Custom headers can be added. Your endpoint has 10 seconds to return a 2XX. The API uses a Bearer key and allows 100 requests a minute; Tally recommends webhooks over polling, since webhook deliveries do not count against that limit. From Tally's help and pricing pages in October 2026:

- **Retries:** after 5 minutes, 30 minutes, 1 hour, 6 hours and 1 day; if all fail, the form owner and creator get a one-time email.
- **Free:** unlimited forms and submissions within fair use guidelines; webhooks included.
- **Pro:** $24 a month; removes Tally branding; custom domains; partial submissions; unlimited team members in shared workspaces; no upload size limit; 30 days of version history.
- **Business:** $74 a month; adds automatic deletion of submissions after a set period, email verification and 90 days of version history.

## What goes wrong with form integrations, and how we prevent it

Unsigned webhooks are the first risk. A form endpoint is public by nature, so anyone who finds the receiver URL can post fake submissions. We always set the signing secret and verify every request on the raw body.

Duplicates are the second. The same person submits twice, or Tally retries after your endpoint was slow, and two contacts appear. We key on the submission ID to make processing idempotent and match contacts on email and other identifiers before creating anything.

Field drift is the third. Someone edits a question label and an integration that maps by label breaks silently. We map on stable field keys or hidden fields, and alert when a submission arrives with a field the workflow does not recognise. Finally, personal data sent onwards is limited to what the next system needs, and if your policy requires it, Business plan deletion keeps Tally from holding answers longer than necessary.

## What happens to a Tally submission, step by step

Every Tally integration we build follows the same order, so it is easy to check and easy to extend.

- Verify the Tally-Signature header against the signing secret on the raw body.
- Store the submission keyed on its response ID, so a retried delivery is processed once.
- Validate answers against your rules and flag anything that fails for a person to review.
- Match the contact on email and other identifiers, then update or create the record.
- Route to an owner by region, product or answer, and notify them where they work.
- Send the confirmation from the workflow, by email or WhatsApp, using your own data.

## How hiring SBD for a Tally Forms integration works

Every engagement starts with an [Automation Audit](https://smallbaydigital.com/services/audit/) at $500, credited in full to your build. For Tally we list each form, where its answers go today, how duplicates and spam are handled and how long it takes for a submission to reach the right person. You get a ranked list of builds, each with a fixed price.

Workflow automation builds start at $1,000, internal tools at $3,000 and multi-module systems at $5,000. A form integration is often one part of a larger onboarding or sales workflow. Work runs in two-week sprints with sixty days of hypercare, and care plans start at $50 a month. Any Tally subscription is paid by you to Tally.

## What you own when the build is finished

The Tally workspace, forms, API key and signing secrets are in your name. You receive a map of each form's field keys to the records they create, the routing and deduplication rules, and a runbook covering what happens when a delivery fails and how to replay a submission.

Because the logic lives in the workflow rather than in the form, swapping Tally for another form tool later means changing one trigger. Book a discovery call to talk through your forms.

## At enterprise scale

Larger organisations tend to find Tally already in use in marketing, HR, events or product teams, chosen for speed and a free plan, with forms built by many people and answers flowing to many places. The questions that follow are about who owns the data, where it goes and whether anyone would notice if a form stopped delivering.

- **An inventory of forms and destinations** We list every form, its owner, the personal data it collects and every system it sends to, so your data protection team has an accurate record.
- **Verified delivery** Every webhook uses a signing secret and every receiver verifies it. Submissions are logged with their ID so a failed or replayed delivery is handled once.
- **Retention** Where policy limits how long answers are kept, Business plan deletion can clear submissions in Tally after a set period, with the authoritative record kept in your own system.
- **Shared workspaces** Pro and Business allow shared workspaces with unlimited team members. We organise forms by team, document who may publish, and keep integration keys on a shared account rather than a person's.
- **Data location** Tally states that form data is stored in Europe. We document where it then goes, such as a US-hosted CRM, so the full path is visible.
- **Failure alerts** Tally emails the form owner after retries are exhausted. We add our own alert on the first failure to a team channel, so it is seen while there is still time to replay.

### Engagements

- **Already on Tally, answers landing in a shared inbox.** Submissions arrive as emails and someone copies them into the CRM. We route each one to the right record and owner with deduplication and a confirmation.
- **Already on Tally, duplicate contacts everywhere.** Native integrations create a new contact on every submission. We replace them with one workflow that matches existing contacts and updates them.
- **Already on Tally, forms nobody owns.** Dozens of forms send data to old spreadsheets. We inventory them, retire the dead ones and connect the rest with signed webhooks and logs.
- **Already on Tally, applications reviewed by email.** Applications are forwarded around for approval. We create a record and a review queue with clear statuses, and notify applicants from the workflow.

## Related

- [TallyPrime integration](https://smallbaydigital.com/integrations/tools/tally/)
- [Typeform integration](https://smallbaydigital.com/integrations/tools/typeform/)
- [Fillout integration](https://smallbaydigital.com/integrations/tools/fillout/)
- [Airtable consultant](https://smallbaydigital.com/integrations/tools/airtable/)
- [Lead routing](https://smallbaydigital.com/solutions/use-case/lead-routing/)
- [Customer onboarding automation](https://smallbaydigital.com/solutions/use-case/customer-onboarding/)

## Sources

- Tally: Webhooks help page (payload, signing, custom headers, timeout, retries, availability), checked 29 October 2026 <https://tally.so/help/webhooks>
- Tally: API reference introduction (authentication, rate limit), checked 29 October 2026 <https://developers.tally.so/api-reference/introduction>
- Tally: Pricing page (Free, Pro and Business plans, EU hosting), checked 29 October 2026 <https://tally.so/pricing>
