Rather have us handle this? We set this up for clients every day.
See the Service
Guides / Getting Started

Understanding Your Dashboard

How to read your monitoring dashboard — what the statuses mean, how to spot issues.

Last verified: April 2026

What the Dashboard Shows

Your monitoring dashboard gives you visibility into your integration’s activity. You can see events as they flow between systems, check whether they were processed successfully, and spot problems before they affect your business.

Not every integration includes a dashboard — we’ll let you know during setup if yours does.

Understanding Statuses

Each event that passes through the integration gets a status:

Received

The integration received the event from the source system. This means the webhook or scheduled pull worked, and the data arrived at our middleware.

Processing

The event is being processed — data is being transformed, validated, and prepared for delivery to the destination system. Most events pass through this status in seconds.

Delivered

The data was successfully sent to the destination system and acknowledged. This is the status you want to see.

Failed

Something went wrong. The event couldn’t be processed or delivered. Failed events include an error message explaining what happened. Common reasons:

  • The destination system rejected the data (validation error, duplicate record, missing required field)
  • The destination system was temporarily unavailable
  • A field mapping produced an unexpected value

Retrying

The integration is automatically retrying a failed delivery. Most transient errors (timeouts, temporary outages) resolve on their own through retries.

Reading the Event History

The dashboard shows up to 30 days of event history. For each event, you can see:

  • Timestamp: When the event was received
  • Event type: What happened (contact created, deal updated, etc.)
  • Source record: An identifier for the record in the source system
  • Status: Current status of the event
  • Destination record: The corresponding record in the destination system (once delivered)

You can filter by date range, status, and event type to narrow down what you’re looking at.

Payload Availability

For debugging purposes, the dashboard stores the full payload (the actual data that was sent) for 7 days. After that, we keep the event metadata (timestamp, status, record IDs) but the payload is no longer available.

If you need to investigate a specific event, check it within that 7-day window so we have the full data to work with.

What to Do If You See Failures

A Few Scattered Failures

Occasional failures are normal. A destination system might have a brief hiccup, a record might have invalid data, or a network timeout might occur. If the status shows “Retrying” and then moves to “Delivered,” the system handled it.

A Spike in Failures

If you see many failures at the same time, it usually means:

  • The destination system went down temporarily
  • API credentials expired
  • A platform update changed something in the API

Check if the failures are ongoing or if they resolved. If they’re ongoing, contact us.

All Events Failing

If every event is failing, it’s likely a credential or connectivity issue. Check:

  1. Did someone change API keys or revoke access?
  2. Did the destination system change their API URL or version?
  3. Is there a platform outage? (Check the destination system’s status page)

Contact us if you can’t identify the cause.

When to Contact Us vs When It’s Normal

Normal — no action needed:

  • A single failed event surrounded by successful ones
  • “Retrying” status that resolves to “Delivered” within a few minutes
  • Brief gaps in activity during off-hours (if no events were generated, there’s nothing to process)

Contact us:

  • Multiple consecutive failures with the same error
  • Events stuck in “Processing” for more than 15 minutes
  • A pattern of failures at the same time every day
  • Any error message you don’t understand
Let's talk about your systems. Tell us what tools you're using and what's not working. We'll tell you what's possible.
Get in touch

Common Issues

Dashboard Shows No Activity

If the dashboard is empty, it could mean no events were triggered in the source system, or the webhook/connection isn’t active. Try creating a test event in the source system and see if it appears.

Status Stuck on “Processing”

Events that stay in “Processing” for more than a few minutes may indicate our middleware is having an issue. Contact us — we have deeper monitoring on our side.

Payload Shows “Expired”

If you’re looking at an event older than 7 days, the payload data is no longer available. We can only investigate events with full payloads.

Next Steps

Need help with the full integration?

This guide covers the setup. If you want us to handle the integration end to end, we can do that.

See Integration Services