Integrations

Integration: Salesforce

Salesforce integration for Framer, Webflow and Next.js sites

A Salesforce integration sends every demo request and contact form on your website straight into Salesforce as a lead, with the campaign, page and UTM data your sales team needs. We pick the right method for your platform, Web-to-Lead or the API, build forms that convert, and test that nothing gets lost. It's part of our $8,000 website package.

Why Designify

  • Website forms that land in Salesforce as complete, routed leads
  • UTM and page data captured in hidden fields on every submission
  • Spam protection that doesn't block real buyers
  • Forms designed for conversion, then tested end to end before launch
  • ATQLeads
  • Update AI
  • LeanScale
  • CSSinc.ai
  • HeyInterests
  • JuPay
  • PowerPulse
  • WireFox
  • Reactive Growth
  • Minexa.ai
  • SmileJoy
  • LFG Business Group
  • ORBITX
  • Funnels.com
  • Sentipi
  • UNIVIT Research
  • LifeLink
  • Wolf Automation
  • Shaqir Hussyin
  • Q-TARO
  • MainPlume

What does a Salesforce integration do on a marketing site?

On a marketing site, a Salesforce integration turns form submissions into leads in your Salesforce org, so sales can follow up without copying anything by hand. Done well, each lead arrives with its source, the page it came from and the campaign that brought it, and lands with the right owner.

  • Lead capture: demo requests, contact forms and gated content create Lead records with mapped fields.
  • Attribution: UTM parameters, landing page and referrer saved to custom fields on the lead.
  • Campaign membership: leads added to the right Salesforce campaign for reporting.
  • Routing: assignment rules send each lead to the right rep or queue.
  • Follow-up: auto-response rules or a booking step so the buyer knows what happens next.

The website's job is to collect clean data. Lead scoring, routing logic and nurture usually belong in Salesforce or your marketing automation tool. Our guide to connecting website analytics to HubSpot or Salesforce pipeline covers how the pieces fit.

Salesforce Web-to-Lead or the API: which should you use?

Web-to-Lead is Salesforce's built-in way to turn a website form into leads: you generate an HTML form in Setup and it posts to Salesforce with your org ID. It's quick and needs no server. The API route sends submissions from your own server code, which gives you validation, error handling and more control.

Web-to-Lead

API from your server

Setup effort

Low, generated in Salesforce Setup

Higher, needs an integration user and code

Objects

Leads only

Leads, contacts, campaigns, custom objects

Error handling

Little visibility when a submission fails

Errors logged and retried

Volume

Subject to a daily cap set by Salesforce

Subject to your org's API limits

Duplicate checks

Limited

Look up existing records before creating

Best for

Simple contact and demo forms

High-volume or multi-step forms

Salesforce documents a daily limit on Web-to-Lead submissions, and spam counts against it, so check the current limit for your edition in Salesforce's help before launch. If you use Account Engagement (formerly Pardot) or HubSpot synced to Salesforce, the form often goes to that tool first. Our explainer on what Web-to-Lead is goes into the details.

How does Salesforce work with Framer, Webflow and Next.js?

Each platform reaches Salesforce differently. Webflow and Framer forms are built into the visual editor, so getting data out usually means a custom form action, a webhook or an automation tool in between. Next.js lets us post to Salesforce from a server route we control.

Framer

Webflow

Next.js

Common method

Webhook to a small server function, or an embedded form

Custom form action to Web-to-Lead, or a webhook

Server route posting to Web-to-Lead or the API

Hidden UTM fields

Custom code or a code component

Custom code fills hidden inputs

Read in the app and sent with the form

Spam protection

Checks in the server function before Salesforce

Webflow's options or reCAPTCHA

Honeypot, rate limits and server validation

Keeps a copy of submissions

Depends on the method

Not when the action posts to Salesforce

Yes, if we log it

Our view

Works, with a webhook in between

Works for simple forms

Most control

Platform form features change, so we confirm the current options in Framer's and Webflow's docs at build time. Our walkthrough of Webflow and Framer forms to Salesforce shows each setup, and Zapier vs Make for website forms covers the no-code middle layer.

How do we set up Salesforce on your site?

We start with your sales process, not the form, and end with a test lead your team has seen arrive.

  1. Map the fields

    We agree which website fields map to which Salesforce fields with your Salesforce admin, including picklist values and required fields.

  2. Design the form

    Only the fields sales actually uses, clear labels and errors, and a confirmation that says what happens next.

  3. Capture attribution

    Hidden fields store UTM parameters, landing page and referrer, carried across pages until the visitor submits.

  4. Connect and protect

    Web-to-Lead or the API depending on platform and volume, with spam checks that run before anything reaches Salesforce.

  5. Test end to end

    Test leads from each form and campaign link, checked in Salesforce for field values, owner and campaign.

  6. Track the conversion

    A named conversion event in your analytics, so marketing reports match the leads in Salesforce.

Our guides to capturing UTM parameters in forms and demo request form fields explain the two steps that most affect lead quality.

What are the common Salesforce form mistakes?

  • Picklist mismatches: a website value that doesn't match the Salesforce picklist exactly gets dropped or rejected.
  • No attribution: leads arrive with no source, so marketing can't show which campaigns work.
  • Spam filling the cap: bot submissions use up Web-to-Lead capacity and bury real leads.
  • Silent failures: a changed field or expired credential stops leads arriving, and nobody notices for weeks.
  • Too many fields: asking for everything sales might want, when enrichment or the first call can fill gaps.
  • Testing in production only: test leads mixed into real pipeline reports.

What does a Salesforce integration cost with us?

Salesforce form setup is part of our website package: $8,000 fixed for up to six pages, then $500 per extra page, including copy, custom design, the build, animation and tested lead capture. Your Salesforce licenses and any automation tools are billed by those vendors.

Moving forms from an old site is scoped on the intro call, and our guide to migrating forms without losing leads covers what to check. If your team uses HubSpot alongside Salesforce, see our HubSpot integration. For demo routing after the form, see Chili Piper. The next step is a free 30-minute call.

What our clients had to say

Pricing

Fixed prices for fixed scopes, agreed before we start, or a monthly retainer when you need a team on call. All prices in USD.

Website

A multi-page marketing site, written and designed by us, developed in Next.js and animated.

What’s included

  • Up to 6 pages, written, designed and developed
  • Custom design, never a template
  • Built in Next.js, fully responsive
  • Animations and interactions
One-time, up to 6 pages

$8,000

+$500 for each extra page
Book a call
4.92 on Contra · 11 reviews

Free 30-minute intro call, no commitment

Not sure yet? Try a week together.

One week of design and development, so you can see how we work before you commit.

$1,000Book a trial week

Frequently asked questions

Do we need a Salesforce admin for the integration?
It helps a lot. Someone with admin access needs to create custom fields for attribution, confirm picklist values, set assignment rules and, for the API route, create an integration user with the right permissions. We work with your admin or a Salesforce consultant on that side, and we handle the website, forms and testing. If you have no admin yet, Web-to-Lead keeps the Salesforce side simplest.
Can website forms update existing contacts instead of creating duplicate leads?
Web-to-Lead always creates new leads, so duplicates are handled by Salesforce's duplicate and matching rules or by your marketing automation tool. If updating existing contacts matters, the API route can look up a record by email first and then update it or create a new one. Which approach fits depends on your volume and how sales works your leads.
Is Salesforce Web-to-Lead secure enough?
Web-to-Lead forms expose your org ID in the page source, which is expected and isn't a credential, but they have little built-in protection against bots. Salesforce lets you add reCAPTCHA to Web-to-Lead, and posting through a server route lets you add honeypots, rate limits and validation. Never put API credentials in browser code; they belong only on the server.
Can we keep HubSpot forms and still use Salesforce?
Yes. Many startups run HubSpot for marketing and Salesforce for sales, with HubSpot's Salesforce connector syncing contacts into Salesforce. In that setup the website form sends to HubSpot, and the sync creates or updates the Salesforce record. It adds a layer to debug, but gives marketing email and nurture tools. We'll recommend one path on the intro call.
How do we know the integration is working after launch?
Compare form submissions on the site with new leads in Salesforce for the same period; the numbers should match closely. We also set up a conversion event in analytics, a test submission routine after any form change and, where possible, an alert when no leads arrive in a day. Those three checks catch nearly every silent failure.

Ready to qualify better leads and boost brand perception?

We take craft seriously over at Designify Studio. We do deep research and do what we do best - pay attention to the smallest details and make sure we speak to the right audience.

Schedule Call