How do I monitor integration health?
Required Feature Flags
The following feature flags and permissions are required to use this feature:
Feature Flag | Description |
Integrations | Enables platform integrations for contact import |
Required Permissions:
Manage Integrations — to view integration status and edit configuration
Why This Matters
Once an integration is set up, you want to know two things at a glance: is it running, and is data flowing? The Platforms tab on the Integrations page answers both. Use it as your daily check before you assume conversations are arriving as expected.
Step 1: Open the integrations health view
Go to Conversations > Integrations.
The Platforms tab shows every integration on your account in a single table.
Step 2: Read the status indicators
Each row shows a status for the integration. Treat these as your first signal:
Status | What it means | What to do |
Active | The last run completed and data is flowing | No action needed |
Warning | The integration ran but something needs attention (e.g. a partial fetch, a missing field) | Open the integration and review the message |
Error | The last run failed | Re-authenticate or fix the configuration. See How do I troubleshoot a failed import? |
Paused | The integration has been stopped manually | Resume it from the integration page when you're ready |
Hover over the status indicator to see the most recent message in full.
Step 3: Check when data last arrived
Two columns tell you about freshness:
Last ran at — when evaluagent last attempted to fetch data
Last data imported — when a record was last successfully saved
A healthy integration shows recent timestamps in both columns, in line with its schedule.
How timestamps display
Time since import | Display format | Example |
Less than 7 hours | Relative time | "2 hours ago" |
7 hours or more | Absolute date and time | "Feb 8, 2026 3:45 PM" |
What "No data" means
No data in the Last data imported column means the integration ran but nothing new matched your import criteria. That's not a failure on its own. Common reasons:
No new conversations have closed since the last run
Your filters exclude everything in the source window
The integration has just been set up and hasn't completed a full cycle yet
If you see No data for an integration that should be busy, check your filters and the source platform.
Step 4: Action error states
If the Status column shows an error or warning:
Click the integration name to open its detail page
Review the error message at the top
Take the relevant action:
- Authentication failed — click Reconnect or edit the integration and re-enter credentials - Permission denied at source — check the user or API key in the source platform still has the access evaluagent needs - Source unreachable — usually transient. If it persists past the next scheduled run, contact support - Rate limited — no action needed. The next run will resume
After fixing the underlying issue, wait for the next scheduled run or trigger a manual import to confirm the fix.
Step 5: Build a regular check into your routine
A short weekly check covers most issues before they affect QA delivery:
Scan the Status column for anything that isn't active
Cross-reference Last ran at with Last data imported — a big gap between them means data isn't being saved even though the run is happening
Watch for integrations that have gone quiet without an obvious reason
If you manage several integrations, sort the table by Status to surface anything that needs attention first.