Connect Salesforce Web-to-Lead
Submit accepted leads through a customer-owned Salesforce Web-to-Lead form.
Submit selected accepted-lead fields through Salesforce's public Web-to-Lead form contract.
Why it matters
The preset uses Salesforce's native intake path without requiring a custom OAuth integration. The company controls its Web-to-Lead organization and enabled fields, while HoneyFalcon records the outbound HTTP result.
Where to work
Prepare Web-to-Lead in the target Salesforce organization. Then open Company -> Connectors, select New connector, choose Salesforce Web-to-Lead, and select Load preset.
Steps
- Enable Web-to-Lead in the target Salesforce organization.
- Generate or inspect the Web-to-Lead form, copy its oid value, and confirm which form fields are enabled.
- Use a Web-to-Lead configuration that does not require interactive reCAPTCHA for this server-to-server submission.
- Load the Salesforce Web-to-Lead preset and keep the fixed webto.salesforce.com endpoint and form-encoded payload.
- Replace REPLACE_WITH_SALESFORCE_ORG_ID with the exact oid and align the template fields with the generated Salesforce form.
- Review Payload fields and Successful HTTP statuses 200 and 302, then run Test draft with a unique synthetic identity.
- Look for the synthetic Lead in Salesforce, then Create connector or Save changes, Activate the saved revision, and verify a separate accepted synthetic lead.
See it in HoneyFalcon
Step 1 of 5: Salesforce preset selected in the connector editor.
Step 2 of 5: Salesforce destination and protected credential controls.
Step 3 of 5: Salesforce payload fields and request template.
Step 4 of 5: Salesforce request template and destination field mapping.
Step 5 of 5: Salesforce endpoint and Successful HTTP statuses to review before creation.
Use the public Web-to-Lead boundary accurately
Prepare the Salesforce form contract
Web-to-Lead must be enabled in the intended Salesforce organization. The generated form supplies the organization ID and the field names accepted by that destination.
This server-to-server preset cannot complete an interactive reCAPTCHA challenge. Use only an approved Web-to-Lead configuration that does not require one.
Preserve the fixed destination
The released preset posts form data to webto.salesforce.com/servlet/servlet.WebToLead with UTF-8 encoding. Keep that host and do not replace it with an unreviewed endpoint.
This recipe does not implement Salesforce OAuth, token exchange, bidirectional sync, or a multi-step API workflow.
Replace the organization marker
Replace REPLACE_WITH_SALESFORCE_ORG_ID in oid with the exact value from the generated form. Review first name, last name, email, phone, address, company, description, and any additional provider-owned form field.
Keep every HoneyFalcon placeholder selected under Payload fields and remove fields the Salesforce form does not accept.
Do not infer synchronous Lead creation
The preset accepts HTTP 200 or 302. Destination accepted the test and Delivered describe the HTTP response, not a synchronous Salesforce read-back.
Search Salesforce for the unique synthetic identity and confirm the Lead and its values separately.
Use the fixed Web-to-Lead host, exact oid, and enabled form fields. HTTP 200 or 302 does not synchronously prove that Salesforce created the intended Lead.
The Salesforce handoff is ready when
- Web-to-Lead is enabled without a mandatory interactive reCAPTCHA for this server request.
- The fixed host, exact oid, form fields, selected fields, and 200/302 status contract remain aligned.
- The connector is saved and activated only after the visible draft is reviewed.
- A unique synthetic submission is traceable in HoneyFalcon and verified separately as a Lead in Salesforce.