Skip to main content

​
Summary

In the current product, integrations are best understood through the workflows they support, not as a flat directory of vendor logos. The biggest integration story today is getting reliable audience and contact data into TruAgents and making sure channel-related infrastructure is ready for actual communications work.

​
Who this is for

Technical admins and operators connecting external systems to TruAgents.

​
The main integration buckets

  • Data source integrations for importing or syncing contact data
  • File-based imports for fast first-run setup
  • Channel infrastructure setup for email and SMS readiness
  • future developer-facing integrations if and when public technical surfaces are supported

​
What the current app suggests

The main operational entry point for many integrations is:
  • Contacts → Data Sources
That area currently supports multiple provider paths and makes integrations part of the audience workflow, not just a standalone admin page.

​
How to choose an integration path

  • choose file imports when speed matters most
  • choose direct provider connections when ongoing sync matters
  • choose channel-specific settings when the goal is delivery readiness rather than contact ingestion

​
The practical decision tree

Ask this first:

​
“Do we just need contacts in the product quickly?”

Choose a file-based import path.

​
”Do we need TruAgents to stay aligned with another system over time?”

Choose a provider-backed data source or sync path.

​
”Do we already have contacts, but communications setup is the blocker?”

Do not start with a CRM or import integration. Start with email or SMS infrastructure instead.

​
What integrations are really for

The easy mistake is to think “integrations” means “connect every outside system.” In practice, the highest-value integration jobs today are:
  • getting contact data in cleanly
  • keeping audience data trustworthy
  • connecting delivery infrastructure so campaigns can actually run

​
Common misunderstandings to avoid

  • importing data once is not the same thing as setting up an ongoing sync
  • channel setup is an integration concern even when it does not feel like a CRM integration
  • the best integration path depends on the workflow goal, not the most recognizable vendor name
  • an integration being connected does not guarantee the imported data is operationally usable

​
Simple version

If you are asking “How do I connect an outside system to TruAgents?”, the answer is usually one of three things:
  1. import contact data
  2. sync contact data
  3. configure the channel infrastructure needed to actually send