WPForms Salesforce Integration for Free: Send Form Entries to Salesforce Without Elite

WPForms ships a native Salesforce add-on, but it sits behind the Elite license. On Lite, Basic, Plus, or Pro, the Salesforce option is simply not in the builder.

There is another affordable solution named Bit Integrations. Using the Bit Integrations automation plugin, you can connect WPForms to Salesforce even with the free version. Bit Integrations treats a WPForms submission as a trigger and a Salesforce record as the action.

Both halves are in the free version, so the WPForms to Salesforce connection works on any WPForms plan, Lite included.

Here is the relationship in one sentence: WPForms captures the submission, Bit Integrations reads the mapped fields and calls the Salesforce REST API from your own WordPress site, and Salesforce creates the record.

No automation subscription sits in the middle, and the form data does not pass through a third-party cloud.

This guide covers the full setup, from installing the plugin to watching the first record land in Salesforce, then the configuration details and errors that catch people out.

What you need before you start

Two systems have to be ready before the plugin can do anything. Most failed setups trace back to something missing on this list rather than to a wrong click later on.

On the WordPress side

• WPForms installed with at least one published form. Any version works, Lite included.
• Bit Integrations installed and activated. The WPForms trigger is available in the free version, so you don’t need a paid licence to follow along.
• Your site is loading over HTTPS. The Salesforce authorization sends the user back to a callback URL on your domain, and Salesforce will not redirect to an insecure one.
• Administrator access to the WordPress dashboard. 

On the Salesforce side

• A Salesforce org with API access enabled.
• Permission to create an app in Salesforce Setup, which is where the Client ID and Client Secret come from.
• A clear idea of which object the form should write to. Contact and lead behave very differently once the record exists, and switching later means rebuilding the field map.

How to Create WPForms Salesforce Integration with Bit Integrations

Here is the complete setup. Each step has a screenshot, so you can check your screen against the one below it.

Step 1. Install and activate the Bit Integrations plugin.

In your WordPress dashboard, go to Plugins, then Add New, and search for Bit Integrations. Install it, then click Activate. The free version is all you need for this workflow.

Step 2. Click Create Integration

Open Bit Integrations from the WordPress menu and click the Create Integration button. This starts the two-part setup: first the trigger, then the action.

Step 3. Search for WPForms and select it as your trigger.

You land on the trigger selection screen. Type WPForms into the search box and click the WPForms card. Cards marked Pro need a license, but WPForms is not one of them.

Step 4. Choose the form you want to connect.

Pick the form whose entries should reach Salesforce from the Select a Form dropdown, then click Next. If you run several forms, build a separate integration for each one rather than trying to cover them all with a single setup.

Step 5. Search for Salesforce and select it as your action.

You are now on the action screen. Search for Salesforce and click the card. The action is the destination, which is where your form data ends up.

Step 6. Authorize your Salesforce account.

Give the integration a name you will recognise later, then click Add new connection. The screen shows a Homepage URL and a Callback URL generated for your site, plus empty Client ID and Client Secret fields.

Copy the Callback URL into the app you create in Salesforce, then paste the app credentials back here. Salesforce calls them Consumer Key and Consumer Secret; the plugin calls them Client ID and Client Secret. They are the same two values.

To create a Salesforce Client ID and Client Secret, follow our Salesforce integration documentation, which walks through the app setup screen by screen, including the OAuth scopes and the settings that keep the connection alive.

Click Authorize. Salesforce asks you to allow access, then returns you to the plugin. Once the connection name appears in the Salesforce Connections dropdown, the credentials are stored, and the Next button becomes available.

Step 7. Choose the Salesforce action event.

Open the Action dropdown and pick the record you want each submission to create. The available events are:

• Create Contact
• Create Lead
• Create Account
• Create Campaign
• Add Campaign Member
• Create Task
• Create Opportunity
• Create Event
• Create Case

Choose based on what the form actually is. The next section covers how to decide if you are unsure.

Step 8. Map your WPForms fields to Salesforce fields.

Once the action is selected, the field map appears. WPForms fields sit on the left, and Salesforce fields on the right. Pair them up and use the plus icon to add more rows.

The first row is the field Salesforce requires for that record type, and it cannot be removed. For a contact, that is, Last Name. In the example below, First Name, Last Name, Email, and Comment or Message from a contact form are mapped to their matching Salesforce fields.

Utilities change with the record type

Below the field map is a utilities row. Which options appear depends on the action you picked, which surprises people who set up one integration and expect the next to look the same.

On Create Contact, you get Update Record, which needs the Pro version, and Record Owner, which does not. Record Owner assigns the new record to a specific Salesforce user instead of the default owner.

On Create Lead, the same row carries more options: Update Record, Lead Source, Lead Status, Rating, and Industry all require Pro, while Record Owner stays available on the free version.

Add conditional logic if only some entries should go through.

Switch on Conditional Logic and build a rule if you want to filter submissions, such as sending an entry to Salesforce only when a dropdown matches a certain value. Leave it off, and every submission goes through. Conditional logic is available on the free version.

Click Next to save and finish the integration.

Step 9. Send a test submission.

Do not skip this. Fill in your form on the front end and submit it, then open the matching tab in Salesforce. The entry should appear as a new record with each mapped field in place.

Then check the integration timeline in the plugin. Every run is listed with a status and the API response. A working integration shows a success status and the created record.

If a run fails, the response names the cause, and the re-execute button sends it again once you have fixed it.

Which Salesforce record should your form create?

This is the decision that matters most, and it is easy to get wrong because contact and lead look interchangeable from the WordPress side. They are not. A lead lives in the pipeline until someone qualifies and converts it. 

A contact is already attached to an account and belongs in the customer record. Picking the wrong one puts your form entries in a part of Salesforce nobody on the team is watching.

Required fields by record type

Each record type has fields Salesforce will not accept a record without. The plugin marks them and locks them into the first mapping rows. Check this list against your form before you start, because a missing required field is the single most common reason a run fails.

Configuration details worth knowing

A handful of behaviors are worth understanding up front. None of them are difficult, but each one has caught someone out.

Dates have to be ISO 8601

Salesforce expects dates as YYYY-MM-DD and datetimes as YYYY-MM-DDThh:mm:ssZ, where Z means UTC. A WPForms date field set to the default m/d/Y format will be rejected by any date field on the Salesforce side, which affects Create Opportunity and Create Event in particular. Change the format on the form field rather than trying to fix it in the mapping.

Every submission creates a new record on the free version.

The integration creates rather than updates. If the same person submits twice, Salesforce gets two records. The Update Record utility, which matches an existing record instead, requires the Pro version. If deduplication matters to your workflow, plan for it now rather than discovering the duplicates in a report three weeks later.

One form can feed several destinations.

The same WPForms form can act as the trigger for more than one integration, so a single submission can create a Salesforce record and also reach a spreadsheet or an email tool. Each destination is its own integration built on the same trigger, which is also how free WPForms email marketing integrations are set up alongside a CRM.

Failure alerts have to be enabled before you create the integration.

Bit Integrations can email you when a run fails, but the setting has to be switched on beforehand. It cannot be applied retroactively to an integration that already exists. On a form that generates real leads, turn it on from Settings. 

The integration runs synchronously.

Because the API call happens on the same request as the submission, a slow response from Salesforce is felt at submit time. On a high-traffic form, keep the field map lean and map only what you actually need in the CRM.

Wrapping up

Once WPForms is set as a trigger, Salesforce does not have to be the end of it. The same submission can feed a spreadsheet, an email platform, or a project tool through additional integrations on the same form.

There is a broader walkthrough on automating WPForms entries if you want to build on this one.

If you are still weighing which CRM to point your forms at, the overview of WPForms CRM integration options compares the routes across plans, and the wider WPForms integrations guide covers what else a form submission can reach.

You may ask this question