The Viking StackKnowledge Base

Send leads to Salesforce

Connect Salesforce in Settings › Connections, choose which Journeys forms and Foundry requests create Leads, and keep staging traffic out of your production org.

3 min readintermediateUpdated November 8, 2026

Forge can create a Salesforce Lead for each Journeys form submission and each Foundry contact request, RFQ or RFP you choose. Every Lead carries a link back to the Forge record, so your sales team starts in Salesforce and opens the details in Forge when they need them. RFQ and RFP line items, part numbers and request text stay in Forge.

Before you start

You need an account administrator role in Forge, and a Salesforce user who can create Leads. Salesforce connections are being enabled account by account while Forge's Salesforce app is prepared for customer orgs; if the card says setup is not available yet, ask your Forge contact.

Connect your org

  1. Open Settings › Connections and find the Salesforce card.
  2. Select Connect with Salesforce and sign in to the org that should receive leads. Approve the access request.
  3. Back in Forge, the card shows Verifying for up to a minute while Forge confirms the org. When it shows Connected, the org is ready.

Optional: select Connect a Sandbox to add a Salesforce sandbox for test traffic.

Choose what creates a Lead

Select Configure Lead Write-Back. Under Sources, turn on Send for each source you want. Every source starts off. Turn on Review First if someone should approve each lead before it is sent; held leads appear under Recent Deliveries with Approve and Discard.

Save the settings. New submissions from that moment on create Leads; earlier submissions are not sent.

Keep staging out of production

If your website has a staging copy, mark it so its form tests never reach your production org:

  • Under Test Mode, tick the staging Journeys site, or enter the staging host (for example staging.example.com or *.staging.example.com). Tick any Foundry listing used only for testing.
  • Choose where staging traffic goes: Dry run records the exact Lead in Forge without contacting Salesforce, and Sandbox org sends it to your verified sandbox.
  • Account-wide test mode sends nothing to production at all, which is useful while you set things up.

Dry-run leads show as Test only (not sent); open the row to see the Lead Forge would have created. They are deleted after seven days.

Ask your Salesforce admin to add a text field to Lead, marked External ID and Unique, at least 80 characters long (for example Forge_Reference__c). Enter its API name under Retry Safety. With it, Forge can retry after a network problem without ever creating a second Lead.

Without it, Forge checks for an existing unconverted Lead with the same email first. If a send is interrupted and Forge cannot tell whether Salesforce saved the Lead, the row shows Needs review with any matching Leads: choose the match, mark it Not Sent to try again, or Cancel.

Map extra fields

Standard Lead fields are filled automatically: name, company, email, phone, title, website, address, description and email opt-out. Under Field Mapping, enter a custom field's API name to send extra values such as the Forge source label or UTM tags there, and set a Lead Source value that exists in your org's picklist. Forge checks the field names against your org before saving.

If something goes wrong

  • Reconnect with Salesforce: the connection expired or was revoked. Connect again; held leads resume.
  • Failed: Salesforce rejected the Lead, usually a required custom field or validation rule. The row names the field; fix the rule or the mapping.
  • Matched existing lead: a Lead with that email already existed, so Forge linked it instead of creating a duplicate.

Disconnecting stops new leads immediately and revokes Forge's access in Salesforce.