Feature snapshot
Summary:
Salesforce integration is a pre‑built connection within LeadConduit that securely delivers and updates lead data directly into your Salesforce CRM, automating field mapping and record management with minimal configuration. This integration also automatically pulls lead outcomes — like lead status, opportunity stage, revenue, or any custom field — right back into your flows for full funnel reporting.
Key benefits:
- Enables rapid, secure connection to Salesforce without custom API development
- Automatically maps standard Salesforce fields (e.g., First Name, Last Name, Email) to your lead flows
- Simplifies lead delivery and record updates, ensuring data consistency and reducing manual entry
- Enhances sales and marketing alignment by consolidating lead information in one unified system
Typical use cases:
- Delivering incoming leads from online forms or external lead sources directly into Salesforce
- Automatically updating existing Salesforce records with new lead data from LeadConduit flows
- Enriching and standardizing lead information for improved sales follow‐up and accurate reporting
- Streamlining lead management by integrating lead qualification results with Salesforce CRM processes
How the Salesforce integration works
Step‑by‑step instructions
-
Add a Salesforce recipient step:
In your LeadConduit flow editor, navigate to the “Add to Flow” menu and click on “Integration”. From the integrations list, select “Salesforce” to add the Salesforce recipient step. -
Name your Recipient:
Assign a name to your new Recipient and add a description if needed; this will help you identify it in case you are delivering leads to different Salesforce accounts. -
Authorize and connect to Salesforce:
When prompted, authorize LeadConduit by signing in to your Salesforce account using credentials that have the API enabled permission. Complete the sign‑in process on the Salesforce login page. -
Configure the integration settings:
Once connected, choose the action you want to perform (e.g., Add, Upsert, or Update a Contact/Lead record). Review the automatic mapping of standard Salesforce fields (such as Salutation, First Name, Last Name, Email, and Phone) and manually adjust any custom field mappings if necessary.- For Upsert actions, you will be prompted to select an External ID field and connect the appropriate data to it to make Upsert work properly. You can think of the External ID as a unique reference key since you won’t know the Salesforce ID needed to update the record.
-
Configure Conversion Feedback:
Enable “Conversion Feedback” by selecting the option to capture key fields (e.g., Opportunity Stage or Lead Status). What are conversions? -
Save and review your setup:
Save the integration settings and verify that Salesforce appears as the selected recipient in your flow’s configuration. Confirm that all mappings and authentication details are correct. -
Activate and test your flow:
Activate your flow so it begins processing incoming leads. Submit a test lead to ensure that Salesforce is called, and that a new record is created or an existing record is updated with the mapped data.
Expected result:
Salesforce displays a new or updated lead/contact record containing data from your LeadConduit flow, with all standard and custom fields correctly populated.
Skipping fields on submission
Skip is a wildcard field that omits a specific field from the record sent to Salesforce — including fields the integration populates by default when you haven’t mapped them. The delivery still happens; that field simply isn’t in it.
To configure it:
- Open the flow and click the Salesforce recipient step.
- Open Field Mappings and click Add Mapping.
- In the left Map box, type
true. - In the right to selector, choose the wildcard field Skip.
- In the suffix box that appears next to the Skip prefix, type the name of the field to omit. The mapping reads Map
trueto Skip → FieldName. - Remove any other mapping to that same field in the step.
- Click Save.
Add one mapping per field you want skipped. Available on Create Lead, Upsert Lead, Create Contact, and Upsert Contact only.
Validation & monitoring (optional)
-
Test the setup:
Submit a test lead through your flow and then log in to Salesforce to verify that the lead record is created/updated correctly, and that all mapped fields contain the expected data. -
Where to monitor?:
Monitor the LeadConduit Events Log for the status of the Salesforce Recipient Step and review Salesforce CRM dashboards or reports to confirm that lead conversions and updates are occurring as expected.
Best practices
-
Use dedicated API credentials:
Ask your Salesforce Administrator to create a dedicated API user account for the integration to ensure reliable authentication and follow security best practices. -
Start with standard field mappings:
Leverage the automatic mapping for Salesforce standard fields and only modify or add custom mappings when your business requirements necessitate additional fields. -
Test thoroughly before production:
Run multiple test submissions to validate field mappings and authentication. Ensure that both new lead creation and record updates perform correctly, then monitor flow events for any anomalies. -
Review field-level security in Salesforce:
Confirm that the integrated Salesforce user has access to all the required fields in Salesforce to avoid data update issues. -
Document your configuration:
Maintain detailed documentation of all field mappings, custom settings, and integration credentials to streamline troubleshooting and future enhancements.
Troubleshooting
| Symptom / Error | Likely cause | Resolution |
|---|---|---|
| Salesforce integration fails to authenticate | Incorrect credentials or missing API Enabled permission | Verify that the correct Salesforce user with API Enabled permission is being used and re‑authenticate. |
| Mapped Salesforce fields are not updating | Field mappings are incomplete or using incorrect API field names | Review and adjust field mappings in the flow editor to ensure they match Salesforce field definitions. |
| Test lead record not appearing in Salesforce | Integration step not activated or misconfigured integration settings | Check that the Salesforce Recipient Step is active and review the integration logs for any errors. |
| Unexpected or incomplete data in records | Inaccurate or missing custom field mapping | Validate all custom mappings and ensure that any additional fields are properly configured. |
| A field keeps getting overwritten on updates | Every field sent replaces the stored value, including ones the integration fills in automatically | Add a Skip mapping for that field, and remove any explicit mapping to the same field. |
| A field is still being sent even though it has a Skip mapping | An explicit mapping to the same field is also present, or the suffix doesn’t match the field name | Remove the competing mapping, and check the spelling and casing of the name typed into the Skip suffix box. |
| The Skip field doesn’t appear in the field selector | The step uses an action that doesn’t support it | Skip is available on Create/Upsert Lead and Create/Upsert Contact only. |
Glossary
| Term | Definition |
|---|---|
| Salesforce Integration | A connection between LeadConduit and Salesforce that enables automatic lead creation and updates within CRM. |
| Recipient Step | A step in a LeadConduit flow that delivers lead data to an external system, such as Salesforce. |
| API Enabled Permission | A Salesforce user profile setting that allows API-based access, necessary for integration connectivity. |
| Field Mapping | The process of matching LeadConduit fields with the corresponding fields in Salesforce to ensure accurate data transfer. |
| Authentication | The process of verifying credentials to securely connect LeadConduit with Salesforce. |
| Test Lead | A sample lead submission used to validate integration setup and field mappings before going live. |
| Real-Time Processing | The immediate handling of lead data as it is received, with minimal delay for record creation or update. |
| Skip | A wildcard field. Mapping true to Skip → FieldName omits that field from the record sent to Salesforce while the rest of the delivery proceeds. |
| External ID / upsert field | The Salesforce field used as a unique key to find and update an existing record on an Upsert. Required for Upsert actions. |
- salesforce-recipient.png200 KB
Comments
0 comments
Please sign in to leave a comment.