SF-Salesforce.WebToLead is a focused integration library that connects Sitefinity Forms to Salesforce Web-to-Lead without depending on the deprecated Sitefinity Salesforce connector.
SF-Salesforce.WebToLead gives Sitefinity teams a practical way to keep lead capture moving on Sitefinity 14 and 15 projects, without adding unnecessary middleware, API complexity, or extra infrastructure.
Package is currently working and tested on Sitefinity 14/15.
When a visitor submits a Sitefinity form, SF-Salesforce.WebToLead captures the submission and sends it directly to Salesforce through the supported Web-to-Lead endpoint. The result is a lean, dependable integration path built around native form events and standard form-encoded posting.
The project is intentionally simple by design. Instead of introducing a custom service layer, OAuth setup, or a separate field-mapping system, it lets Sitefinity field names map directly to Salesforce Web-to-Lead field names. That keeps implementation easier to understand, faster to deploy, and simpler to maintain over time.
It also gives administrators control where it matters. Teams can limit which forms are allowed to submit leads, validate approved lead sources, optionally restrict company values, and support Salesforce custom fields using a Sitefinity-safe naming pattern.
– Replaces the deprecated Sitefinity Salesforce connector with a clean Web-to-Lead integration path.
– Sends data directly to Salesforce using standard `application/x-www-form-urlencoded` requests.
– Hooks into Sitefinity form submission events with minimal setup in the host application.
– Keeps field mapping straightforward by using Sitefinity form field names that match Salesforce Web-to-Lead field names.
– Supports Salesforce custom lead field IDs such as `00N…` through a configurable prefix strategy for Sitefinity-safe field names.
– Includes startup validation for required configuration values so configuration issues surface early.
– Supports form-level whitelists so only approved Sitefinity forms can submit leads.
– Supports whitelists for `lead_source` values and optional `company` values.
– Uses asynchronous, non-blocking submission behavior so the form experience is not held up by Salesforce calls.
– Logs failures for troubleshooting without interrupting the visitor submission flow.
– Supports both standard Sitefinity form posts and AJAX-based form submissions.
Download the package from Nuget here –
https://www.nuget.org/packages/SF-Salesforce.WebToLead/
Or run this command in the Visual Studio Package Manager Console, for your Sitefinity project
NuGet\Install-Package SF-Salesforce.WebToLead -Version 0.0.5.5Version `0.0.5.5` updates the release workflow so published NuGet packages remain listed instead of being immediately unlisted after push.
The `0.0.5.x` release line also includes support for Salesforce custom field IDs through a configurable Sitefinity field prefix, clearer installation guidance, stronger package metadata, bundled documentation and licensing files, and recent documentation improvements.
= 0.0.5.5 =
– Disabled the GitHub Actions step that unlisted package versions immediately after publishing to NuGet.org.
– Prepared the next listed NuGet release after the `0.0.5.4` publish/unlist issue.
= 0.0.5.4 =
– Improved project documentation and README content.
– Updated the website-facing and technical readmes for clearer installation, release history, and project positioning.
= 0.0.5.3 =
– Added support for Salesforce custom Web-to-Lead field IDs using a configurable prefix such as `sf_00N…`, with automatic prefix stripping before submission.
– Updated documentation for the custom field prefix workflow.
= 0.0.5.2 =
– Improved README installation instructions for package consumers.
– No library code changes in the tagged diff beyond the release version update.
= 0.0.5.1 =
– Added `LICENSE.txt` and `README.md` to the NuGet package.
– Refined package metadata and publish workflow for package consumers.
= 0.0.5.0 =
– Updated the NuGet publish workflow for the `0.0.5.x` release line.
– No library code changes in the tagged diff beyond the release version update.
= 0.0.4.9 =
– Updated the NuGet package identity in the `.nuspec`.
– Expanded README guidance related to package installation and usage.
= 0.0.4.8 =
– Simplified the NuGet publish workflow configuration.
– No library code changes in the tagged diff beyond the release version update.
= 0.0.4.7 =
– Refined the NuGet publish workflow again as part of release automation hardening.
– No library code changes in the tagged diff beyond the release version update.
= 0.0.4.6 =
– Continued refining the NuGet publish workflow.
– No library code changes in the tagged diff beyond the release version update.
= 0.0.4.2 =
– Refined the publish workflow for NuGet automation.
– No library code changes in the tagged diff beyond the release version update.
= 0.0.4.1 =
– Expanded the GitHub Actions publish workflow for NuGet packaging.
– No library code changes in the tagged diff beyond the release version update.
= 0.0.4 =
– Updated the project for NuGet builds.
– Added `NuGet.config` and `packages.config` to support packaging workflows.
– Refined the `.csproj` DLL referencing strategy for Sitefinity builds.
= 0.0.3 =
– Initial tagged release of the Sitefinity Forms to Salesforce Web-to-Lead integration.
– Included the core hook logic, README updates, NuGet `.nuspec`, and publish workflow groundwork.
Project documentation starts in the repository README.md, which covers installation, configuration, required fields, custom field naming, and Sitefinity initialization.
For implementation questions, issue reporting, or enhancement requests, use the GitHub issue tracker:
– GitHub: https://github.com/compkick/sf-salesforce-webtolead/issues
For production deployments, it is also a good idea to document your local web.config values, allowed form slugs, and Salesforce field naming conventions so future maintenance stays predictable.
Also, you can use our contact form.