Use readiness as the export boundary
A Smartlead export should not treat every mailbox row as usable. GTM partitions inboxes by SMTP readiness so ready rows can continue while rows missing SMTP, IMAP, credential, or smoke-test evidence are blocked with safe operator-facing reasons.
- Check inbox status, managed MTA assignment, SMTP metadata, and IMAP metadata.
- Require encrypted credential and password hash metadata without returning secrets.
- Persist blocked export rows with failureType set to readiness-oriented reasons.
Keep provider errors customer-safe
Provider integrations can fail for account, auth, quota, or upstream validation reasons. GTM keeps the workflow useful by normalizing failures and returning redacted messages instead of raw Smartlead payloads, provider secrets, JWTs, or SMTP passwords.
Separate export success from campaign success
A successful Smartlead account export means the provider workflow accepted the ready rows. It is not a guarantee of inbox placement, warmup performance, replies, or safe prospect volume. First prospect traffic should still depend on launch-gate and seed-placement evidence.