Formstack · Salesforce · Data Collection

Simplify Data Collection With Formstack Forms: The Complete Guide

Formstack Forms is a no-code form builder for collecting clean, validated data and sending it where your team works. This guide explains what it does, how it differs from Forms for Salesforce, how to connect it to Salesforce without creating duplicates, and what it costs and protects, so you can choose and build with confidence.

Where we sit in this: Twopir Consulting is a Salesforce Partner that implements and integrates Formstack for CRM teams. Formstack (whose company now trades as Intellistack) builds the products described here. Product facts link to Formstack's and Salesforce's own pages, checked in November 2026.

Key Takeaways

  • Formstack Forms is a no-code form builder with conditional logic, built-in field validation, save and resume, payments, approvals and data routing. Submissions are stored in Formstack and can be sent on to Salesforce, HubSpot and other tools.
  • Forms for Salesforce is a different product: a native app where forms are built, and data is processed and stored, inside your Salesforce org, with dynamic prefill from existing records.
  • Choose by where the data must live. Data that belongs 100% in Salesforce suits Forms for Salesforce. Forms owned by marketing or operations, feeding several systems, suit Formstack Forms. Many teams use both.
  • Clean data is a design decision: picklists instead of free text, upsert on a reliable key, a defined record owner, and validation at the point of entry.
  • Compliance is configured, not automatic. HIPAA needs a BAA and an add-on account on the Forms and Suite plans; PCI needs the compliant card fields and processors.
Section 01 · Definition

What Is Formstack Forms?

Formstack Forms is a no-code online form builder for collecting data through web forms and automating what happens after someone submits. You drag fields onto a form, add logic and validation, publish it by link or embed code, and route each submission to people, documents or connected systems such as a CRM, with no developer required.

Formstack describes the product as automating "data collection to data workflows", with form prefill, AI form creation and multi-step workflows as headline features. Typical forms include lead capture, applications, registrations, patient intake, internal requests and feedback surveys.

Two naming points prevent confusion. First, the company rebranded from Formstack to Intellistack in June 2025 and said Formstack products would continue to be sold and supported, so the product is still called Formstack Forms. Second, "Formstack Forms" and "Forms for Salesforce" are separate products with different architectures, covered in section 3.

Build

A drag-and-drop builder with field types, sections, themes and multi-page layouts. No code.

Guide

Conditional logic shows only relevant questions; validation blocks badly formatted entries before submit.

Route

Email logic, approvals, webhooks and integrations send each submission to the right person or system.

Protect

SSL on every form, optional data encryption, PCI card fields, and HIPAA and GDPR options.

Section 02 · Features

Which Formstack Forms Features Improve Data Quality?

The Formstack Forms features that most improve data quality are field validation, conditional logic, save and resume, partial submissions and data routing. Validation stops bad formats at entry, logic hides irrelevant questions, save and resume rescues long forms, partial submissions show where people quit, and routing gets each response to its owner.

Feature lists are long, so the table below groups the ones that change data quality and process speed, with what each is best used for. Availability varies by plan, so confirm your plan's inclusions before you design around a feature.

FeatureWhat it doesUse it for
Field validationEmail, phone, credit card, address and date fields check their format automatically; a badly formatted entry blocks the submission with a messageContact data you will email, call or sync to a CRM
Conditional logicShows or hides fields and sections based on earlier answersOne form serving several request types without irrelevant questions
Save and resumeOn multi-page forms, emails the respondent a personal link and gives them 30 days to finishApplications, onboarding and intake forms that need documents to hand
Partial submissionsCaptures data entered by people who leave before submitting, with notification emails every 6, 12 or 24 hours (part of the Conversion Kit)Finding the field that makes people quit, and following up on abandoned leads
Data routingEmail logic sends submissions to different people; redirects, webhooks and APIs pass data onwardSending each region, product or request type to its owner
ApprovalsApprovers approve or deny from email, in the order you setPTO, purchase, proposal and hiring requests
Payments and calculating fieldsPayPal, Stripe and Authorize.Net; recurring payments, quantities, discounts and automatic totalsRegistrations, orders, fees and donations
File uploadsCollects documents and images, with file-type limits and storage in Formstack or Box, Dropbox, Google Drive, Amazon S3 or OneDriveResumes, IDs, inspection photos and supporting documents
Field prefill (SSO)Prefills fields from a single sign-on provider such as Google SSO, LDAP, Active Directory, SAML 2.0 or CASEmployee and portal forms where people are already logged in

Features as described on formstack.com feature pages in November 2026. Some, such as partial submissions and field prefill, depend on your plan or an add-on.

For developers, the Formstack API exposes forms, fields, submissions and prefill endpoints, which is the route for custom integrations the standard connectors do not cover.

Section 03 · Comparison

Formstack Forms Or Forms For Salesforce: Which Should You Use?

Use Forms for Salesforce when the data belongs entirely in Salesforce and you need to prefill or update existing records. Use Formstack Forms when marketing or operations own the forms, the data feeds several systems, or Salesforce is only one destination. Formstack's own comparison says it need not be either/or: many customers run both.

The difference is architectural. Formstack Forms stores each submission in Formstack and syncs it to Salesforce through an integration. Forms for Salesforce is built inside your org, so submissions are processed and stored there under Salesforce's security model. The table follows Formstack's comparative guide and Forms for Salesforce product page.

QuestionFormstack FormsForms for Salesforce
Where are forms built?In Formstack; no Salesforce login neededInside Salesforce; a Salesforce login is needed
Where does submission data live?In Formstack, then synced to SalesforceOnly in your Salesforce org
Who usually owns the forms?Marketing and business usersSalesforce admins and power users
Update existing records with prefilled data?No dynamic Salesforce prefill (upsert can update matched records)Yes: dynamic prefill through encrypted links, plus upsert
Experience Cloud formsNoYes
File uploads go toFormstack storage or a cloud storage integrationSalesforce Files, Chatter or Attachments, plus Dropbox, AWS S3 or Azure
Other destinations300+ integrations, webhooks and APISalesforce first; payment and storage integrations
How you buy itPublished plans, starting with FormsSalesforce Solutions plan with custom pricing, via a sales order

Choose Forms for Salesforce if every answer ends up on a Salesforce record, you send forms to known customers who should confirm rather than retype what you hold, you need forms in an Experience Cloud site, or your policy is that this data must never be stored outside the org.

Choose Formstack Forms if non-Salesforce users build and change the forms, submissions also go to email, storage, marketing or payment tools, or the form is public and only some answers should reach Salesforce. You can still upsert into Salesforce through the integration.

Section 04 · Integration

How Do You Connect Formstack Forms To Salesforce?

You connect Formstack Forms to Salesforce from the form's Settings, under Integrations. Add the Salesforce integration, sign in with a Salesforce user and security token, choose the objects to create, map each form field to a Salesforce field, and tick Upsert on a matching field such as Email so returning people update their record instead of duplicating it.

Formstack positions this integration as a replacement for Salesforce Web-to-Lead and Web-to-Case forms, with more control, spam prevention and client-side validation. The steps below follow Formstack's Salesforce integration setup guide.

1. Check API access first.
The integration uses the Salesforce API, so the org needs an edition with API access (Enterprise, Unlimited, Performance, Developer, or Professional with API access added). Formstack recommends a dedicated API-only user with a security token rather than a person's login.
2. Add the integration and sign in.
In the form's Settings, open Integrations, find Salesforce under CRM, and enter the integration user's username, password and security token.
3. Choose objects and map fields.
Pick each Salesforce object the form should write to, then map form fields to object fields. You can add several objects and link them, for example a Case that links to the Contact created or matched by the same submission.
4. Set upsert on a reliable key.
Tick Upsert on a qualifying field, most often Email. Without it, every submission creates a new record. Salesforce decides which fields are upsert-enabled; Formstack cannot force one.
5. Test failures, not just successes.
Submit a duplicate, an oversized file and a bad value. Failed submissions can be re-run from the submission's Integration Status with "Run Again" once the cause is fixed.

Know the limits before go-live. If more than one Salesforce record matches the upsert field, Salesforce returns an error, so clean duplicates first. Files only transfer if they are stored in the Formstack database, and Formstack notes that attachments over 5MB fail because of the Salesforce API file cap. Heavy volumes can hit the org's daily API request limit, and an expired password on the integration user stops the sync until someone signs in again, per Formstack's common errors article.

If you are comparing form tools for Salesforce more broadly, our Formstack Salesforce integration page covers native and standalone set-ups, and our Formstack integration services page compares connector, webhook, API and middleware patterns.

Section 05 · Setup

How Do You Build Your First Form In Forms For Salesforce?

To build a form in Forms for Salesforce, install the app from AppExchange, open Formstack from the App Launcher and authorise it, create a form and choose its primary object and any related objects, drag in fields, add rules, then publish. Fields that Salesforce requires are added to the form automatically and cannot be removed.

The steps below are a refreshed version of the walkthrough in our original post. The screenshots come from an earlier release of the app, so labels and styling in your org may differ slightly.

1. Install and connect.
Install Forms for Salesforce from AppExchange into a sandbox or production org, choose which profiles get access, then find Formstack in the App Launcher. On first visit you authorise Formstack to use your Salesforce data. Existing customers should also check they are on managed package 4.162.1 or later and have completed the one-time External Client App migration.
Salesforce App Launcher with Formstack typed in the search box and the Formstack item highlighted
Finding Formstack in the Salesforce App Launcher.
2. Define the data structure.
Create a form, name it and choose the primary object, then add related objects. One form can write to several objects at once: with Opportunity as the primary object, for example, the same submission can also update the related Account.
Forms for Salesforce Create Data Structure screen with Opportunity as the primary object and Account and Price Book added as related objects
Choosing a primary object and related objects before building the form.
3. Add fields from objects and general fields.
Open each object in the Objects panel and drag fields onto the form, or search for them by name or type. General Fields add items that are not stored on an object, such as a captcha, image, file upload, payment or signature. You can relabel a field on the form without changing it in Salesforce.
Forms for Salesforce builder with Account fields such as Account Name, Billing Street and Industry on the form and the Account field list in the side panel
Account fields dragged onto a form from the Objects panel.
General Fields panel listing Text, Captcha, File Upload, Image, Payment and Signature
General Fields: inputs that are not tied to a Salesforce object.
A Contact Us form in the Forms for Salesforce builder with Contact as the primary object and Account as a related object, showing Last Name and Account Name fields
A Contact form that also writes to the related Account.
Objects panel showing Contact, Account and General Fields, with Draft Saved and Publish Draft buttons
The Objects panel, with draft and publish controls above it.
4. Add rules for conditional behaviour.
Rules apply to fields or sections and can use answers or data from the primary and related objects, combined with AND/OR conditions. A simple example: if Industry equals Consulting, make Company required.
Forms for Salesforce rule editor: if Industry is equal to Consulting, then make Company required
A rule that makes Company required when Industry is Consulting.
5. Prefill what you already know.
For forms sent to known contacts, use upsert, dynamic prefill or advanced prefill. Dynamic prefill loads live data from the record and its related records through an encrypted link, so people confirm details instead of retyping them.
A Customer Update Form in Forms for Salesforce with Contact as the primary object and related Asset, Account and Contact objects listed
A customer update form built on Contact with several related objects, a common prefill pattern.
6. Publish, then manage from the form list.
Each form in the list has Edit, Duplicate, Preview and Delete actions, an active/inactive toggle, a draft indicator, Migrate (to move a form between sandbox and production), Submissions and Publish Options. The Submissions view shows overall, successful, pending and failed counts.
Forms for Salesforce form list showing a test form with Edit, Duplicate, Preview and Delete links, the Form active toggle, and Migrate, Submissions and Publish Options buttons highlighted
Form actions: edit, duplicate, preview, activate, migrate and publish.
Submissions dropdown on a form showing overall, successful, pending and failed submission counts and a View Submissions button
The submissions summary: successful, pending and failed.
Section 06 · Security

Is Formstack Forms Secure And Compliant For Sensitive Data?

Formstack Forms supports HIPAA, PCI and GDPR requirements, but compliance depends on configuration and plan, not the product alone. Every form uses 256-bit SSL. For sensitive data you turn on database encryption, sign a Business Associate Agreement for health data, and use the PCI-compliant card fields and processors for payments.

The old version of this post said Formstack "ensures compliance" with HIPAA and GDPR. That overstated it. A vendor can support your obligations; your configuration, your agreements and your processes decide whether you meet them.

RequirementWhat Formstack providesWhat you still have to do
HIPAAA standard or custom BAA, and a dedicated or converted account with data encryption, SMTP options, field and folder security, audit logging and user permissionsSign the BAA, buy the HIPAA add-on on Forms or Suite plans, and keep health data out of plain email notifications
PCIPCI-compliant credit card fields paired with processor integrations such as Stripe and PayPalUse those fields only; never collect card numbers in a text field
GDPRUnchecked opt-in checkboxes, privacy policy text on the form, and workflow forms for erasure requestsRecord what each person consented to and when, and set retention for partial and saved submissions
General security256-bit SSL on all forms, optional data encryption, PGP email encryption, Invisible reCAPTCHA, password-protected formsEnable encryption, require strong passwords and multi-factor authentication, shorten timeouts

For Salesforce-heavy organisations, Forms for Salesforce takes a different route: data never leaves the org, it follows Salesforce's security model, and Formstack lists the Native Professional plan as compatible with Salesforce Shield. That makes it the simpler answer when policy says customer data must stay in Salesforce.

Section 07 · Pricing

How Much Does Formstack Forms Cost?

Formstack Forms starts at $83 per month, paid annually, for one builder user, 25 forms, 1,000 submissions per form and 2GB of storage. The Suite, which adds Documents and Sign, starts at $250 per month. Salesforce Solutions and Enterprise plans have custom pricing, and HIPAA compliance is an add-on on the Forms and Suite plans.

PlanStarting priceWhat's includedBest for
Forms$83/month, paid annually1 builder user, 25 forms, 1,000 submissions per form, 2GB storage, 300+ integrationsOne team replacing paper or basic web forms
Suite (Forms + Documents + Sign)$250/month, paid annually3 builder users, 100 forms, 5,000 submissions per form, 10GB, 250 document deliveries a month, unlimited e-signaturesProcesses that end in a generated, signed document
Salesforce SolutionsCustomSalesforce-native forms, documents from Salesforce data, Experience Cloud integration, Shield compatibility, dynamic prefillData that must live in Salesforce
EnterpriseCustomSSO and advanced security, unlimited users and submissions, API access, custom SLAsMany teams, high volume, strict security

From formstack.com/pricing on November 6, 2026. Formstack says annual plans save two months against monthly billing. Prices and limits change, so confirm them with Formstack before you budget.

There is also a free edition of Forms for Salesforce, limited to two forms that write to Accounts, Leads, Contacts or Cases. According to Formstack's Forms for Salesforce FAQ, it excludes related objects, lookups, prefill, upsert, the rule editor, payments and file uploads, so treat it as a trial rather than a production option.

Section 08 · Use Cases

What Can Teams Collect With Formstack Forms?

Teams use Formstack Forms wherever information arrives from people outside the CRM: lead and enquiry forms, applications, registrations with payment, patient and client intake, customer detail updates and internal requests. The right setup depends on who fills in the form and where the answer must end up, not on the industry.

Use caseFeature set that fitsWhere the data should land
Website lead and enquiry formsFormstack Forms with validation, reCAPTCHA, email routing and Salesforce upsert on EmailLead or Contact, owned by the right rep from the first minute
Patient or client intakeHIPAA-enabled account with encryption, save and resume, file uploads; or Forms for Salesforce if the data must stay in the orgThe patient or client record, never an inbox
Applications and admissionsMulti-page form, save and resume, file uploads, approvalsAn application record with documents attached
Event registrations and feesPayment processor, calculating fields, discount codes, confirmation emailsContact plus a payment or registration record
Customer detail updates and renewalsForms for Salesforce with dynamic prefillThe existing Account, Contact or custom record, updated in place
Internal requests (PTO, purchases, access)SSO field prefill, approvals, data routingThe approving manager, then the system that acts on it

The earlier version of this post quoted two percentage results for unnamed healthcare and manufacturing clients. We could not trace either figure to a source, so we removed them rather than repeat numbers nobody can verify.

Section 09 · Pitfalls

Which Data Quality Mistakes Should You Avoid With Formstack Forms?

The most common Formstack Forms mistakes are design choices, not product gaps: free-text fields that should be picklists, no upsert key so every submission duplicates a record, records owned by whoever installed the app, and files or picklists that silently fail to sync. Each one is cheap to prevent at build time and expensive to clean up later.

1. Free text where a choice belongs. A typed "Industry" or "Country" field produces dozens of spellings that break reports and routing. Use dropdowns, radio buttons or Salesforce picklists, and keep shared option lists consistent across forms.
2. No upsert key. Without upsert on Email or another unique field, each submission creates a new record. With Forms for Salesforce, Salesforce duplicate rules can also block submissions: Formstack's upsert guide suggests allowing duplicates with upsert, or narrowing your matching rules.
3. Every record owned by the installer. In Forms for Salesforce, records created by submissions belong to the user who installed and authorised Formstack, unless you add the Owner field with a default. Set ownership deliberately, or use assignment rules after creation.
4. New picklist values that never appear. Values added in Salesforce do not show on a Forms for Salesforce form until you refresh that field's configuration in Formstack. Add the refresh to your change checklist.
5. Files that never reach Salesforce. With the Formstack Forms integration, uploads transfer only if stored in the Formstack database, and attachments over 5MB fail. Limit file types and sizes on the field, and tell people the limit.
6. A sandbox refresh that breaks forms. Forms for Salesforce prefill links point to one org and one form, and forms must be republished in a refreshed sandbox, per Formstack's sandbox guide. Test in the sandbox, then use Migrate to promote.
Section 10 · AI

Can AI Build A Formstack Form For You?

Yes, as a first draft. Formstack's AI form creation builds a form from a written prompt once an org admin enables it. It cannot yet add show/hide logic, change field settings, update emails or set up integrations, so a person still finishes, connects and tests the form before it goes live.

According to Formstack's AI form creation article, the feature uses Anthropic's Claude in AWS Bedrock, and Formstack says it does not train AI on the forms you create. The older version of this post promised "AI-driven workflows"; today the AI helps you build forms faster, while routing and logic remain rules you design.

Section 11 · Delivery

How Twopir Helps You Get Clean Data From Formstack

We implement, rescue, optimize, and integrate complex CRM and revenue systems. For Formstack Forms, that starts with the data, not the layout: which object owns each answer, which field is the matching key, who owns the record, and what happens when a submission matches nothing. Then we build the form, the logic and the integration around those decisions.

We help growing and mid-market companies, as well as enterprise teams, with this work. Typical starting points:

Ready to Start

Review Your Forms With A Salesforce Architect

In a 30-minute discovery call we look at one of your forms, where its data goes and where it duplicates or gets lost, and tell you whether Formstack Forms, Forms for Salesforce or both fit, and what to fix first.

Schedule a Discovery Call
Section 12 · Bottom Line

The Bottom Line

Formstack Forms makes collecting data simple: a no-code builder, validation and logic that keep answers clean, and routing that gets them to the right place. The quality of what lands in your CRM still depends on choices you make: which product, which matching key, which owner, and how you test.

  1. 1

    Use Formstack Forms for forms owned outside Salesforce or feeding several systems, and Forms for Salesforce when the data must live and update in the org.

  2. 2

    Design for clean data at entry: picklists, validation, an upsert key and a defined record owner.

  3. 3

    Treat HIPAA, PCI and GDPR as configuration work, with the right plan, agreements and fields.

  4. 4

    Test duplicates, large files, sandbox refreshes and package upgrades before they happen in production.


FAQ

Frequently Asked Questions

Formstack Forms is used to build online forms without code and automate what happens after submission. Common uses are lead capture, applications, event registrations with payment, patient and client intake, surveys and internal requests such as approvals, with the data routed to people, documents or connected systems like Salesforce.

Formstack Forms stores submissions in Formstack and sends them to Salesforce through an integration. Forms for Salesforce is a native app: forms are built inside Salesforce and data is processed and stored only in your org, with dynamic prefill from existing records. Many organizations use both.

Yes. The Salesforce integration maps form fields to one or more Salesforce objects and can upsert on a matching field such as Email, so returning people update their record. It needs a Salesforce edition with API access, and Formstack recommends a dedicated integration user with a security token.

Formstack offers HIPAA-supporting accounts with a Business Associate Agreement, data encryption, field and folder security and audit logging. On the Forms and Suite plans this is an add-on. Compliance also depends on how you configure forms, notifications and access, so it is not automatic.

Formstack's pricing page lists the Forms plan from $83 per month paid annually, with one builder user, 25 forms and 1,000 submissions per form. The Suite starts at $250 per month. Salesforce Solutions and Enterprise plans are custom-priced. Confirm current prices with Formstack.

Yes, in two ways. Save and Resume lets a respondent save a multi-page form and finish within 30 days from an emailed link. Partial Submissions, part of the Conversion Kit, captures what people typed before abandoning a form. Forms for Salesforce stores partial submissions in your org.

The company rebranded from Formstack to Intellistack in June 2025. It stated that Formstack products continue to be sold and supported, so Formstack Forms and Forms for Salesforce keep their names, and the AppExchange listing now shows Intellistack as the provider.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. Our team of 40+ consultants and architects designs and builds Salesforce, HubSpot and Formstack solutions, from forms and data capture to integrations and automation.