Summary
SendGrid shows up in TruAgents as part of the contact-data and communication infrastructure story, not just as a random third-party provider mention. The current product makes SendGrid especially important because it appears in two different places:- as a contact-data source path
- as part of the broader email and template-management workflow
Who this is for
Technical admins and operators connecting external systems to TruAgents.Where it fits in the product
- Contacts → Data Sources for import-related workflows
- related email setup and communication operations, depending on your final implementation pattern
What this page should eventually cover
- what data TruAgents can pull from SendGrid-related workflows
- what credentials or provider setup are required
- how field mapping behaves for imported contacts
- how to tell whether the import or sync actually worked
Practical workflow
The current SendGrid import path strongly suggests:- create or reuse a SendGrid integration
- create or reuse the associated data source
- inspect incoming fields
- map them into TruAgents contact fields
- import contacts and validate the result
Why SendGrid needs careful interpretation
SendGrid can matter both for:- contact data coming into TruAgents
- email infrastructure and template-related operations elsewhere in the product
What to validate first
- whether the right SendGrid credentials or provider setup are in place
- whether the incoming fields were mapped correctly
- whether the imported contacts are actually usable for campaigns
- whether the question belongs to contact ingestion or email operations
Common mistakes
- confusing SendGrid import setup with email-delivery setup
- assuming provider connectivity removes the need for mapping review
- diagnosing campaign issues before checking the imported records