CRM integration · Updated November 15, 2026

Salesforce integration

We connect Salesforce to WordPress, Webflow, Astro or Next.js sites and custom software, from a simple Web-to-Lead form to live Salesforce records on public pages. Leads arrive with their consent, and the site shows only the records you choose to publish.

Rated 5.0 out of 5,72 Google reviews

Salesforce at a glance

Connects
Web-to-Lead, Web-to-Case, the REST and Composite APIs, Change Data Capture through the Pub/Sub API, and Account Engagement form handlers.
WordPress
The Gravity Forms Salesforce add-on, or a small plugin of ours that calls the REST API.
Webflow
A native form posting to Web-to-Lead, or a function we host that calls the API.
Astro or Next.js with Sanity
Server routes call the REST API as an integration user; public records are cached and refreshed when they change.
Custom software
The REST and Composite APIs, with Change Data Capture to keep a copy in sync.
Complexity
Medium to high. Web-to-Lead is quick; live data needs the API, caching and a security review.
Typical setup
1 to 3 days for Web-to-Lead, 5 to 20 days for API forms or live data.

How we connect Salesforce

  • WordPress

    Salesforce makes no WordPress plugin. The Gravity Forms Salesforce add-on is built by Gravity Forms and comes with its Elite and Nonprofit licences; version 2.0 installs an OAuth app in your org. The Object Sync for Salesforce plugin was closed on WordPress.org on July 28, 2026 for a security issue, so we don't use it. For live records, we write a small plugin that calls the REST API and caches the results.

  • Webflow

    Webflow says Salesforce offers no official app. A native Webflow form can post to Web-to-Lead, but the visitor is sent to your return URL and errors never come back to the page. For contacts, custom objects or a proper error message, we send the form to the API through a function we host.

  • Astro or Next.js with Sanity

    Sanity holds the pages and Salesforce holds the records. A server route creates leads, contacts or custom records through the REST API, as a dedicated integration user signed in with OAuth client credentials. For public pages built from Salesforce data, such as a directory or a map, the server fetches only the published fields, caches them and refreshes when Change Data Capture reports an edit.

  • Custom software

    Portals and internal tools use the REST and Composite APIs. Since Spring '26, Salesforce turns off creating new connected apps by default, so new integrations use External Client Apps. Experience Cloud is Salesforce's hosted portal option. After attacks on loose guest-user settings, Salesforce told customers in March 2026 to start guest profiles from zero access, and we do.

What organizations use Salesforce for

  • Programs and members for nonprofits

    Program sign-ups, volunteer forms and member updates go into Salesforce, and a member directory can show on the public site. Salesforce's Power of Us program donates 10 Enterprise Edition licences to eligible nonprofits.

  • Public directories for member and public-sector bodies

    Lists of members, facilities or funded projects come from Salesforce records, so staff update them in one place.

  • Sales and service for enterprises

    Website enquiries become leads routed by assignment rules, and support forms create cases through Web-to-Case, which takes up to 5,000 cases a day.

What to watch out for

  • Web-to-Lead limits

    Web-to-Lead takes 500 leads a day. Extra ones wait in a queue shared with Web-to-Case and capped at 50,000; past that, new submissions are lost, and the admin hears about only the first five. It creates leads only, takes no attachments and can't tell the visitor when something fails. Past a few hundred a day, or for anything but leads, we use the API.

  • Consent and privacy

    Salesforce keeps consent in its own objects (Individual and Contact Point Type Consent), with an opt-in or opt-out status per channel. Under CASL we store the opt-in wording and date there, not in a checkbox field that gets overwritten. Salesforce runs Hyperforce in Canada and keeps data at rest in the country, but some Einstein AI features may process data elsewhere, which a Quebec Law 25 assessment should cover.

  • API limits and security

    As of November 15, 2026, Enterprise orgs get 100,000 API requests per rolling 24 hours plus 1,000 per licence. A page that called Salesforce on every view would burn through that and expose the org, so the site reads from a cache and the integration user sees only the fields it needs.

Sources

Checked against Salesforce's docs on November 15, 2026.

  1. Set up Web-to-Lead Editions and reCAPTCHA.
  2. How many leads can Web-to-Lead capture? 500 a day.
  3. What if we get more than 500 leads a day? The pending queue and its 50,000 cap.
  4. Web-to-Case limits 5,000 cases a day.
  5. API request limits Daily limits by edition and licence.
  6. Connected app creation disabled by default From Spring '26.
  7. Integration user and OAuth client credentials
  8. Subscribe to Change Data Capture with the Pub/Sub API
  9. Secure Experience Cloud guest user access March 2026.
  10. Hyperforce in Canada Data at rest stays in Canada.
  11. Consent data model
  12. Power of Us program 10 donated licences for eligible nonprofits.
  13. Gravity Forms Salesforce add-on Built by Gravity Forms.
  14. Object Sync for Salesforce Closed on WordPress.org July 28, 2026.
  15. Webflow and Salesforce No official Salesforce app.

Questions about Salesforce

Can our website show live data from Salesforce?

Yes. A server reads the records you choose to publish, caches them and refreshes them when they change. Visitors never touch Salesforce, and the integration user can read only those fields.

Is Web-to-Lead enough?

For a contact form taking a few hundred leads a day, often yes. Past 500 a day, or for anything but leads, we use the REST API.

Can Salesforce store our data in Canada?

Yes. Salesforce runs Hyperforce in Canada and keeps data at rest in the country, except for some AI features. Confirm with Salesforce that your org is on the Canadian instance.

Do we need a Salesforce developer as well?

Not always. We build the website side. If your org needs new fields, objects or flows, we'll say so early and work with whoever looks after it.

Related integrations

Want your website connected to Salesforce?

Tell us which records should reach the site and which forms should feed it. We'll say whether Web-to-Lead or the API fits, and what your Salesforce admin will need to do.

Book a call