Fixes a mapping row being silently dropped on save when its Salesforce field was not in the cached field list, and Record Type being ignored on Web-to-Lead forms. If a Record Type or Owner row went missing from a form, re-add it after updating.<\/p>","1.6.1":"
Security hardening: Web-to-Lead feeds take their org id from the connection, and changing a connection's address discards its stored credentials. Existing feeds keep working; a Web-to-Lead feed that names a connection with no org id will ask you to set one on the connection.<\/p>","1.6.0":"
Adds "fields combined" as a mapping source, so Company can be built from a person's name with fallbacks. Nothing changes for existing feeds.<\/p>","1.5.0":"
Upload Salesforce's Web-to-Lead form to get a fully paired mapping CSV; Web-to-Lead feeds now accept Lead API names, and an unconfirmed post can no longer be read as delivered. Nothing changes for existing feeds.<\/p>","1.4.0":"
Adds Start from a live form on the Forms screen, and fixes mapping of Formidable Name fields part by part. Nothing changes for existing feeds.<\/p>","1.3.0":"
Generate a key now writes wp-config.php for you where the server allows it. Nothing changes for sites that already have a key.<\/p>","1.2.0":"
Adds Formidable Forms support and a Generate a key button for sites without shell access. Nothing changes for existing feeds.<\/p>","1.1.0":"
Adds custom form support. Nothing changes for existing Contact Form 7 feeds.<\/p>","1.0.0":"
First stable release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3679892,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3679892,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3679892,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3679892,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0","1.2.0","1.3.0","1.4.0","1.5.0","1.6.0","1.6.1","1.6.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3679892,"resolution":"1","location":"assets","locale":"","width":1280,"height":950},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3679892,"resolution":"2","location":"assets","locale":"","width":1280,"height":900},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3679892,"resolution":"3","location":"assets","locale":"","width":1280,"height":900},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3679892,"resolution":"4","location":"assets","locale":"","width":1280,"height":2259},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3679892,"resolution":"5","location":"assets","locale":"","width":1280,"height":900},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3679892,"resolution":"6","location":"assets","locale":"","width":1280,"height":900}},"screenshots":{"1":"The dashboard answers \"is it working\" before it offers anything to configure: one plain sentence about the last seven days, then any problem with the fix beside it, then the latest submissions and what became of each.","2":"Activity, with a status in words for every submission. A delivered lead carries the Salesforce record id it created; anything else says plainly what it is, and nothing is coloured without also being labelled.","3":"A failure explains itself in terms you can act on. Salesforce's own validation message is quoted, the cause is attributed to the org rather than to the plugin, and the record can be sent again once the cause is fixed.","4":"Field mapping built on your org. The destination list comes from the object itself, required fields come first and are flagged, and fields Salesforce would never accept on create are not offered at all.","5":"Connection health, one row per thing that can be wrong. An expired token reads OK because it renews itself; an unrecorded app type reads Unknown rather than being guessed. The retirement panel links to this org's own schedule instead of printing a date it cannot know.","6":"Choosing how to connect, framed by outcome rather than by protocol. The basic method says before you pick it that Salesforce will not confirm delivery."}},"plugin_section":[262246],"plugin_tags":[1152,1150,601,335,9220],"plugin_category":[42,58],"plugin_contributors":[279035],"plugin_business_model":[],"class_list":["post-358650","plugin","type-plugin","status-publish","hentry","plugin_section-dashboard-widgets","plugin_tags-contact-form-7","plugin_tags-crm","plugin_tags-forms","plugin_tags-leads","plugin_tags-salesforce","plugin_category-contact-forms","plugin_category-user-management","plugin_contributors-oddeveninfotech","plugin_committers-oddeveninfotech"],"banners":{"banner":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/banner-772x250.png?rev=3679892","banner_2x":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/banner-1544x500.png?rev=3679892","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/icon-128x128.png?rev=3679892","icon_2x":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/icon-256x256.png?rev=3679892","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/screenshot-1.png?rev=3679892","caption":"The dashboard answers \"is it working\" before it offers anything to configure: one plain sentence about the last seven days, then any problem with the fix beside it, then the latest submissions and what became of each."},{"src":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/screenshot-2.png?rev=3679892","caption":"Activity, with a status in words for every submission. A delivered lead carries the Salesforce record id it created; anything else says plainly what it is, and nothing is coloured without also being labelled."},{"src":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/screenshot-3.png?rev=3679892","caption":"A failure explains itself in terms you can act on. Salesforce's own validation message is quoted, the cause is attributed to the org rather than to the plugin, and the record can be sent again once the cause is fixed."},{"src":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/screenshot-4.png?rev=3679892","caption":"Field mapping built on your org. The destination list comes from the object itself, required fields come first and are flagged, and fields Salesforce would never accept on create are not offered at all."},{"src":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/screenshot-5.png?rev=3679892","caption":"Connection health, one row per thing that can be wrong. An expired token reads OK because it renews itself; an unrecorded app type reads Unknown rather than being guessed. The retirement panel links to this org's own schedule instead of printing a date it cannot know."},{"src":"https:\/\/ps.w.org\/oddeven-lead-routing-for-salesforce\/assets\/screenshot-6.png?rev=3679892","caption":"Choosing how to connect, framed by outcome rather than by protocol. The basic method says before you pick it that Salesforce will not confirm delivery."}],"raw_content":"\n
Oddeven Lead Routing connects your WordPress forms to Salesforce and keeps the connection\nworking through the 2026 and 2027 authentication changes.<\/p>\n\n
Built for the auth Salesforce actually supports.<\/strong> Salesforce restricted new\nConnected App creation in Spring '26 and retires the OAuth username-password flow in\nWinter '27. Oddeven Lead Routing is built on External Client Apps with the client credentials\nflow, so a connection you set up today is still a supported configuration afterwards.\nThe username-password flow is not implemented, and never will be.<\/p>\n\n A submission is saved before it is sent.<\/strong> Every submission is written to the\ndatabase with a pending status before any outbound call, then delivered by a\nbackground worker through Action Scheduler. A Salesforce outage, a slow API or a\nvalidation error cannot break your form or lose the lead. Failed deliveries are\nretried with backoff and, if they keep failing, land in a dead letter list you can\ninspect and requeue.<\/p>\n\n Credentials are encrypted at rest.<\/strong> Client secrets and tokens are protected with\nlibsodium authenticated encryption, keyed from a constant you define in\nwp-config.php.<\/p>\n\n No phoning home.<\/strong> The plugin talks to your Salesforce org and nothing else. No\ntelemetry, no analytics, no licensing service.<\/p>\n\n A mapping row can send several fields as one value, with fallbacks: A Formidable form connects the same way a Contact Form 7 one does: choose Formidable\nForms as the source, enter the form's ID from its Forms list, and map its fields. Fields\nare identified by Formidable's field ID \u2014 the number the form itself posts \u2014 with the\nfield's label shown beside it, so nobody has to remember that \"Last name\" is field 7.\nA Name field is offered part by part \u2014 Paste the address of a page that shows a form and the plugin reads the form from it,\ntells you whether it can deliver from that form plugin, and hands you a mapping CSV\nwith the form id and every field already filled in \u2014 the obvious Lead fields\nsuggested, the rest left for you. Complete the Salesforce column and import it. No\nviewing page source, no typing field ids.<\/p>\n\n Using Web-to-Lead? Upload the form Salesforce generated under Setup \u2192 Web-to-Lead as\nwell, and the CSV comes back with both sides filled in: each Salesforce field \u2014\nincluding custom fields by their 00N\u2026 id \u2014 paired with the matching form field by\nlabel, the org id set, and hidden values such as the record type carried as fixed\nvalues.<\/p>\n\n A form the plugin has never heard of can still reach Salesforce. From inside the code\nthat already handles the submission, after it has decided the submission is good:<\/p>\n\n Everything after that is identical to a Contact Form 7 lead: saved first, queued,\nretried, and visible in Activity. Declare the form and its fields under Forms \u2192 Custom\nforms so the mapping can be built before the form has ever been submitted. Fields that\nturn up in real submissions are recorded and offered there too, so a field added in code\nand forgotten in configuration shows up as something to click rather than as silence.<\/p>\n\n It is a hook rather than an address the browser posts to, deliberately: your form keeps\nits own nonce, spam handling and redirect, and this plugin adds nothing new that faces\nthe public internet.<\/p>\n\n This plugin connects to Salesforce, and to nothing else. It contacts no service\noperated by us, sends no telemetry, and transmits nothing at all until you have\nconfigured a connection and connected a form to it. A visitor loading a page never\ncauses an outbound request.<\/p>\n\n The Salesforce org you connect, at the My Domain address you supply, for example\nhttps:\/\/yourcompany.my.salesforce.com. It is used to obtain an OAuth access token, to\nread the object and field list so you can map fields to it, and to create records from\nform submissions.<\/p>\n\n What is sent, and when:<\/p>\n\n Used only if you choose that delivery method for a form, instead of the API.<\/p>\n\n Your Salesforce organisation id and the mapped form field values are sent when a\nqueued submission is dispatched.<\/p>\n\n Used only if you choose the browser sign-in method when creating a connection. Your\nbrowser is sent to https:\/\/login.salesforce.com, https:\/\/test.salesforce.com or your\nown My Domain address to authorise the plugin, and the resulting authorization code is\nexchanged there for an access token.<\/p>\n\n All three are provided by Salesforce, Inc. Terms of service:\nhttps:\/\/www.salesforce.com\/company\/legal\/agreements\/ . Privacy policy:\nhttps:\/\/www.salesforce.com\/company\/legal\/privacy\/ .<\/p>\n\n\n It is the key your Salesforce credentials are encrypted with, and it is required.\nUntil it is defined the plugin stores no credential at all and tells you so.<\/p>\n\n It does not invent a key of its own, and it never borrows one from WordPress. A key\ntaken from your site's authentication salts would look convenient right up to the day\nsomething rotated that salt -- several security plugins do, on a schedule -- at which\npoint every stored Salesforce credential would become permanently unreadable, with no\nway to recover it. Being asked for one line in wp-config.php is the cheaper end of\nthat trade.<\/p>\n\n Click the Generate a key<\/strong> button the plugin shows while the key is missing. It\nadds the line to wp-config.php for you when the web server can write that file, and\nshows the key once so you can back it up; it is never kept in the database. If the file\ncannot be written \u2014 it is read-only, the host needs FTP credentials, or the site sets\nDISALLOW_FILE_MODS \u2014 you are shown the line to add yourself, with the reason. WP-CLI\nusers can run No, deliberately. Salesforce retires it in Winter '27 and it requires storing a\nuser's password. Use the client credentials flow with an External Client App.<\/p><\/dd>\n Nothing visible to the visitor. The submission is already saved, and the delivery is\nretried in the background.<\/p><\/dd>\n No. There is no telemetry and no phone-home of any kind.<\/p><\/dd>\n\n<\/dl>\n\n\n A mapping row could be lost on save, and a record type set through Web-to-Lead was ignored.<\/p>\n\n Two hardenings from a whole-plugin security review. Neither was exploitable by a visitor or by any role short of a permission only administrators hold; both are closed so the plugin's guarantees hold without qualification.<\/p>\n\n Combine fields in one mapping row, with fallbacks.<\/p>\n\n Pair a live form with Salesforce's own Web-to-Lead form, and Web-to-Lead fixes learned from a real cutover.<\/p>\n\n Start a mapping from a live form's page, and map Formidable Name and Address fields part by part.<\/p>\n\n Generate a key now adds it to wp-config.php for you.<\/p>\n\n Formidable Forms support, and an encryption key you can generate without a shell.<\/p>\n\n Custom forms: deliver to Salesforce from a form this plugin does not know.<\/p>\n\n First stable release.<\/p>\n\nFeatures<\/h4>\n\n
\n
Combining fields<\/h4>\n\n
{first} {last}<\/code>\nsends the name; {company}||{first} {last}||Individual<\/code> sends the company when the\nform has one, the person's name when it does not, and a fixed word when it has\nneither. That is what Salesforce's mandatory Company field needs from a form most\npeople fill in as individuals.<\/p>\n\nSupported forms<\/h4>\n\n
\n
Formidable Forms<\/h4>\n\n
82.first<\/code>, 82.last<\/code> \u2014 and so is an Address\nfield, because Salesforce wants FirstName and LastName apart; the field itself is\nstill available as one value. Entries are captured the moment Formidable saves them,\nbefore its own actions run, so a\nform whose email action is switched off still delivers. The free plugin is enough;\nrepeater sections from Formidable Pro are handled as one submission, not one per row.<\/p>\n\nStart from a live form<\/h4>\n\n
Custom forms<\/h4>\n\n
do_action( 'lbsf_custom_form', 'quote-request', array( 'first_name' => $first_name, 'email' => $email ) );\n<\/code><\/pre>\n\nRequirements<\/h4>\n\n
\n
wp-config.php<\/code>, which holds the encryption key<\/li>\nExternal services<\/h3>\n\n
Your Salesforce org<\/h4>\n\n
\n
Salesforce Web-to-Lead and Web-to-Case<\/h4>\n\n
\n
Salesforce sign-in<\/h4>\n\n
\n
\/wp-content\/plugins\/oddeven-lead-routing-for-salesforce<\/code> and activate\nit.<\/li>\nwp-config.php<\/code>. This step is required: until it is done\nthe plugin stores no Salesforce credential at all, and says so on screen. Click\nGenerate a key<\/strong> on that screen: the key is added to wp-config.php<\/code> for you\nwhen the web server can write that file, and shown once so you can keep a copy\nsomewhere safe. If the file cannot be written, you are shown the line to add\nyourself \u2014 a hosting file manager or SFTP is enough \u2014 or run\n wp oddeven-lead-routing key:generate:\n define( 'LBSF_ENCRYPTION_KEY', 'base64 of exactly 32 bytes' );<\/li>\n\n
Why do I need to define LBSF_ENCRYPTION_KEY?<\/h3><\/dt>\n
wp oddeven-lead-routing key:generate<\/code> instead.<\/p><\/dd>\nDoes this support the username-password OAuth flow?<\/h3><\/dt>\n
What happens if Salesforce is down when someone submits a form?<\/h3><\/dt>\n
Does the plugin send any data anywhere else?<\/h3><\/dt>\n
1.6.2<\/h4>\n\n
\n
1.6.1<\/h4>\n\n
\n
1.6.0<\/h4>\n\n
\n
1.5.0<\/h4>\n\n
\n
1.4.0<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n