Summary
SFTP is the more operational, infrastructure-oriented import path in the current TruAgents integration story. It is usually the right fit when data is exchanged as files on a schedule rather than pulled through a direct SaaS API connection.Who this is for
Technical admins and operators connecting external systems to TruAgents.Where it fits in the product
- Contacts → Data Sources
- recurring or batch-style contact import workflows
What this page should eventually cover
- what credentials and file-delivery setup are required
- how file naming and expected schema should be handled
- how mapping and sync verification work after files land
- what teams should check when a scheduled import does not produce expected contacts
Practical workflow
The current SFTP path looks different from the SaaS-provider integrations. It appears to involve:- creating an SFTP integration
- generating or using the provided SFTP access details
- uploading CSV files using the provided command or connection details
- creating or refreshing the data source
- listing available CSV files and importing them into TruAgents
Why SFTP is different
SFTP is best understood as a file-delivery pipeline, not an in-app business app connection. That means teams need to think about:- who owns the upstream file drop
- how often files are delivered
- whether the delivered schema stays consistent
- how import verification happens after files land
Good operational habits
- treat the upload command and connection details as sensitive infrastructure
- validate file shape before assuming the import is healthy
- check whether the expected files are actually present before debugging deeper
- decide who owns the upstream file delivery process
Common mistakes
- assuming SFTP behaves like HubSpot or Salesforce auth flows
- debugging mapping before confirming the files actually arrived
- forgetting that a scheduled batch process can fail before TruAgents ever sees the data