Summary
Salesforce is part of the supported external data-source story for bringing customer records into TruAgents. The current product flow suggests Salesforce behaves as a connected provider integration with an authentication step and a direct transfer workflow, rather than a visible column-mapping step like some other import paths.Who this is for
Technical admins and operators connecting external systems to TruAgents.Where it fits in the product
- Contacts → Data Sources
- contact data preparation for segments, campaigns, and communications workflows
What this page should eventually cover
- what Salesforce data is expected to be useful in TruAgents
- how authentication and account access should be configured
- how imported fields should be validated before campaign use
- how sync results should be checked after the connection is established
Practical workflow
The current Salesforce path appears to be:- create or reuse a Salesforce integration
- create or reuse the associated data source
- authenticate with Salesforce
- trigger the contact transfer
- inspect the imported records in TruAgents
Why validation still matters
Because this path looks more direct than file upload or HubSpot-style column mapping, teams can wrongly assume the imported data is automatically campaign-ready. That is still risky. Simple version: fewer visible setup steps does not mean less need to validate the resulting contacts.What to check first
- whether authentication completed successfully
- whether the expected records actually landed
- whether the imported contact fields are usable for segmentation and campaigns
- whether the issue is data quality versus integration access
Common mistakes
- assuming a successful auth flow guarantees usable contact data
- using imported contacts in campaigns before checking sample records
- treating Salesforce import issues like generic campaign problems