Tally Forms Salesforce Integration: 3 Ways to Connect (2026)

Noca Forms: AI form builder you can set up from a plain-language prompt, connected to your CRM, ERP and other systems. Free plan available.

Last updated: November 2026

Short answer: Tally Forms has no native Salesforce integration as of November 2026, so a Tally Forms Salesforce setup goes through a connector. The three working options are Zapier (Tally "New Submission" trigger plus Salesforce "Create Record"), Make ("Watch New Responses" plus a Salesforce module), or Tally webhooks posting to your own endpoint or the Salesforce API.

Key Takeaways

  • Tally Forms is not a native Salesforce integration; its help center lists direct integrations such as Google Sheets, Notion, Airtable and Slack, but not Salesforce.
  • Zapier connects Tally to Salesforce with a Tally "New Submission" trigger, but Salesforce is a Premium app on Zapier, so a paid Zapier plan is required.
  • Make offers a Tally "Watch New Responses" trigger with Salesforce modules, and Tally says its Make integration is free for all Tally users.
  • Tally webhooks can post each submission, signed with a secret, to an endpoint that writes to Salesforce, with no per-task automation fees.

Noca is not affiliated with Tally or Salesforce. This guide is based on Tally’s, Zapier’s and Make’s public pages as of November 2026. Menus and plan limits change, so confirm the details in each product before you build.

Tally is a popular free form builder, and Salesforce is where many sales and service teams keep their data. Getting the two to talk takes a few extra pieces. This guide shows each route step by step, what it costs, and the mistakes that make leads go missing.

Tally Forms Salesforce integration: is there a native connector?

No. Tally’s help center lists its direct integrations as tools such as Google Sheets, Notion, Airtable, Slack, Discord, Coda, Linear and Attio, plus analytics tools (Google Analytics 4 and Meta Pixel). Salesforce is not on that list. For everything else, Tally points users to automation platforms (Zapier, Make, n8n and Integrately) or to its webhooks and API. You can see the current list on Tally’s integrations page.

That isn’t unusual for a lightweight form builder, but it matters for planning. Every Tally-to-Salesforce flow has three parts: the Tally form, a middle layer that moves the data, and the Salesforce object that receives it. The middle layer is where most of the cost and most of the problems live.

MethodWhat you needBest forMain trade-off
ZapierTally (any plan), a Zapier plan that includes premium apps, Salesforce loginNon-technical teams, simple lead captureSalesforce is a Premium app on Zapier, so the free Zapier tier isn’t enough
MakeTally (any plan), a Make account, Salesforce loginMulti-step logic on a tighter budgetScenario builder takes longer to learn
Webhooks or APITally webhooks, a developer, an endpoint (Apex REST, middleware or serverless function)Teams with engineering help and strict data rulesYou own the code, error handling and monitoring

How do you prepare Tally and Salesforce before connecting them?

Decide the target Salesforce object, list its required fields and match field types before you build anything. A few minutes of prep saves hours of debugging later.

  1. Decide the target object. Most teams create a Lead. Customer forms (renewals, support requests, onboarding) usually create or update a Contact, Case or a custom object.
  2. List the required fields. Salesforce rejects records with missing required fields. For Leads, Last Name and Company are required by default, so make sure your Tally form collects both or that you set a fallback value.
  3. Match field types. Picklists in Salesforce only accept values that exist in the picklist. Use Tally multiple-choice options that match those values exactly.
  4. Add hidden fields for tracking. Tally supports hidden fields filled from URL parameters, which is a clean way to carry UTM source, campaign or a record ID into Salesforce.
  5. Check API access. Integrations write to Salesforce through its API. Ask your Salesforce admin to confirm your edition and the integration user’s profile allow API access, and use a dedicated integration user if your company requires one.

Method 1: How do you connect Tally to Salesforce with Zapier?

Create a Zap with Tally as the trigger and a Salesforce "Create Record" action. Zapier has a ready-made Salesforce + Tally integration page with templates such as "Create leads in Salesforce from new Tally form responses."

  1. In Zapier, create a new Zap and choose Tally as the trigger app.
  2. Select the New Submission trigger, connect your Tally account, and pick the form. The trigger is instant, so submissions arrive within seconds rather than on a polling schedule.
  3. Submit a test response in Tally so Zapier has sample data to map.
  4. Add an action step, choose Salesforce, and connect your Salesforce account through the OAuth sign-in.
  5. Pick an action. Create Record (with the Lead object) is the usual choice. Zapier also offers Create Lead, Create Contact, Update Record, Add Lead to Campaign, Find Record and Find or Create Record.
  6. Map each Tally answer to a Salesforce field. Set defaults for required fields you don’t ask for, such as Lead Source = "Tally form".
  7. Test the step, check that the record appears in Salesforce with the right owner and values, then turn the Zap on.

Cost note: Zapier lists Salesforce in its Premium category. Zapier’s free tier covers core features, and premium apps need a paid plan (Zapier offers a trial of premium features). Check Zapier’s pricing page for current plan limits, because each Zap run uses tasks.

Tip: to avoid duplicates, add a Find Record step on email before creating anything, or use Find or Create Record. Without it, every resubmission creates a new Lead.

Method 2: Connect Tally to Salesforce with Make

Make suits branching flows: use the Tally "Watch New Responses" module followed by a Salesforce module. Make lists a Tally and Salesforce integration. Tally says its Make integration is free for all Tally users.

  1. In Make, create a new scenario and add the Tally module Watch New Responses.
  2. Connect your Tally account and pick the form. Make creates the link to Tally for you.
  3. Add a Salesforce module. Useful ones include Create a record, Create or update a record, Get a record, Update a record and Make an API call for anything not covered.
  4. Map the Tally fields to Salesforce fields. Make’s mapping panel shows each answer from your sample submission.
  5. Add a router or filter if different answers should go to different objects, for example "Request type = Support" creates a Case while everything else creates a Lead.
  6. Run the scenario once, submit a test response, check Salesforce, then schedule or activate it.

Make is often chosen when the flow branches or needs data clean-up before it reaches Salesforce. The visual scenario builder handles that well, at the cost of a steeper learning curve than Zapier.

Method 3: Use Tally webhooks or the Tally API

Webhooks give full control and no per-task fees, but a developer must build and maintain the endpoint. Tally can send every new submission as an HTTP request to a URL you choose, and it can sign requests with a secret so your endpoint can verify they really came from Tally. Tally also has an API for creating forms and syncing submissions from code. Both are described on Tally’s webhooks help page.

A typical developer setup looks like this:

  1. Create an endpoint that can receive Tally’s JSON payload: an Apex REST class in Salesforce, a serverless function, or your existing middleware.
  2. In the Tally form, open Integrations, add a webhook, paste the endpoint URL and set a signing secret.
  3. In the endpoint, verify the signature, map the payload’s fields to Salesforce fields, and create or upsert the record (upserting on an external ID or email prevents duplicates).
  4. Log failures and alert someone. Salesforce validation rules, duplicate rules and required fields will reject some records, and without logging those leads disappear quietly.

This route has no per-task fees and gives full control over security and data handling. The trade-off is that someone has to build it and keep it running.

Why is my Tally to Salesforce connection failing?

Most failures come from missing required fields, picklist mismatches, duplicates or a disabled Zap. The table lists the usual causes and fixes.

ProblemLikely causeFix
"Required fields are missing" errorSalesforce needs Last Name or Company and the form didn’t supply themMake the fields required in Tally or set a default value in the mapping
Picklist value rejectedTally option text doesn’t match a Salesforce picklist valueEdit the Tally options or add a lookup/formatter step
Duplicate LeadsEvery submission creates a new recordUse Find or Create Record (Zapier), Create or update (Make) or an upsert
Zap won’t let you add SalesforceSalesforce is a Premium app on ZapierUpgrade the Zapier plan or use Make or webhooks
Connection fails after a password change or user deactivationThe OAuth connection belonged to that userReconnect with a dedicated integration user
Nothing arrives, no errorZap or scenario turned off, or webhook URL wrongCheck the run history in Zapier/Make or the webhook logs in Tally

Limits worth knowing before you commit

A Tally-to-Salesforce setup is one-way by default and means paying for and monitoring two vendors.

  • Two vendors to pay and monitor. Tally’s free plan is generous, but the Salesforce connection usually needs a paid automation plan, and you watch two systems for failures.
  • One-way by default. These flows push form data into Salesforce. Pre-filling a Tally form with Salesforce data needs hidden fields or URL parameters that you generate yourself.
  • No document or signature step in Salesforce. If the process continues after the form (a quote, a contract, an approval), you’ll add more tools and more steps.
  • Data location. Tally says it is EU-based and stores data in Europe. If your Salesforce org has data residency rules, check that the middle layer meets them too.

For a straightforward "web form creates a Lead" use case, Tally plus Zapier or Make works well and is quick to set up. It gets harder when the form is the first step of a longer process.

How Noca handles forms that feed Salesforce

Noca builds the form and the Salesforce connection in one platform. If your Tally-to-Salesforce flow keeps growing, it may be worth looking at a tool that builds the form and the Salesforce integration in one place. Noca is an AI business process automation platform: you describe the process in plain language and it builds the form, the workflow and the Salesforce connection together.

What that means in practice, based on Noca’s published capabilities:

  • Bi-directional Salesforce field mapping, so data can flow into the form as well as out of it.
  • Forms with conditional logic, validation and built-in signature capture.
  • Approval steps, routing and notifications after submission.
  • PDF or Word documents generated from your own templates and attached back to the Salesforce record.
  • 60+ integrations plus REST API and webhooks when you need something custom.

Tally is the better choice if you want a free, fast form and only need a Lead created. Noca fits when the form is the start of a process that runs through Salesforce. You can compare the approaches on our integration automation page.

Start free with Noca or book a demo.

Sources

Frequently Asked Questions

Does Tally integrate with Salesforce?

Not natively. As of November 2026, Salesforce isn’t among Tally’s direct integrations. You connect the two through Zapier, Make or another automation tool, or by sending Tally webhooks to your own endpoint that writes to the Salesforce API. All three approaches can create Leads, Contacts or other records from new submissions.

Can I use Tally’s free plan with Salesforce?

Yes on the Tally side. Tally’s free plan includes integrations with Zapier and Make plus webhooks, so you don’t need Tally Pro to send data out. The cost usually sits in the middle layer: Salesforce is a Premium app on Zapier, so you’ll need a paid Zapier plan, or you can use Make or a custom webhook instead.

How do I create a Salesforce lead from a Tally form?

Build a Zap with the Tally "New Submission" trigger and a Salesforce "Create Record" action using the Lead object, or use a Make scenario with "Watch New Responses" and "Create a record." Map the form answers to Lead fields, make sure Last Name and Company are filled, test it, then switch it on.

How do I stop Tally creating duplicate Salesforce records?

Look the person up before creating anything. In Zapier, use "Find Record" or "Find or Create Record" on email. In Make, use "Create or update a record." In a custom webhook, upsert on an external ID or email. Salesforce duplicate rules add a second safety net.

Can Tally update existing Salesforce records?

Yes, through the connector. Zapier offers Update Record, Update Lead and Update Contact actions, and Make has an Update a record module. You need a way to identify the record, usually an email lookup or a Salesforce ID passed into the form as a hidden field from the URL.

Is Tally secure enough to send data to Salesforce?

Tally says it is EU-based, GDPR compliant, stores data in Europe and encrypts data in transit and at rest. Your data also passes through whichever connector you use, so review that vendor’s security terms as well, and connect with a dedicated Salesforce integration user that has only the permissions it needs.

Can Tally pull data from Salesforce to pre-fill a form?

Not directly. Tally can pre-fill fields from URL parameters and hidden fields, so you can generate a link containing Salesforce values (for example from a Salesforce email template or a Flow) and send it to the person. A live, two-way lookup needs custom work or a platform with bi-directional Salesforce mapping.

What is the easiest way to connect a form to Salesforce?

For a simple lead form, Tally plus a Zapier template is usually the fastest to set up. If the form is part of a bigger process with approvals, documents or signatures, a platform that builds the form and Salesforce integration together, such as Noca, removes the extra connector to maintain.

Back to top