ZenotiHelp

Monitor integration health and metrics

ZTZenoti Docs Team Updated August 20, 2026 3 min readGuide

The integration health dashboard surfaces the health and performance of every active integration β€” real-time (PMS, payments) and batch (accounting, inventory, payroll, tips). Use it to identify sync failures, track processing volumes, and troubleshoot issues proactively.


On this page


Before you begin

Permission: You need organization administrator access to view integration health dashboards.


Access the integration health dashboard

  1. Navigate to Configuration > Integrations > Integration settings, then search for and expand the provider.
  2. The dashboard displays summary cards for each active integration.
  3. Color indicators show integration health:
  • Green β€” active with no recent errors.
  • Yellow β€” warning or elevated error rate.
  • Red β€” critical errors or disconnected.

Integration settings follow Zenoti's standard inheritance: center-level settings override organization-level settings. The dashboard reflects the effective configuration per center.


Dashboard metrics

Metric Description
Status Current connection and sync status.
Last sync Time of the most recent successful sync.
Records synced Number of records processed in the last cycle.
Error count Number of failed records in the last cycle.
Error rate Percentage of records that failed.

View detailed sync logs

  1. Select any integration card to open the detailed view.
  2. The Sync Log shows record-level activity with timestamps, statuses, and error messages.
  3. Filter logs by:
  • Date range.
  • Status (Pending, Synced, Queued, SyncFailed, QueueFailed).
  • Record type.

Respond to integration errors

  1. In the sync log, open a failed record.
  2. Review the error details returned by the external system.
  3. Identify the cause (expired token, account mapping error, rate limit, transient outage).
  4. Take corrective action:
  • Re-authorize the connection if the token expired.
  • Update data mapping if an account is missing.
  • Wait and retry if the external system was temporarily unavailable.
  1. Failed records are automatically retried in the next sync cycle. For immediate retry, trigger a manual sync from the integration page.

Failure types by integration class

Different integrations surface different failure modes. Use the table below to route errors to the right next step.

Class Typical failures Where to resolve
Accounting (QBO, Xero, Codat) OAuth expired, account mapping, rate limit Re-authorize or fix mapping on the accounting integration page.
Inventory / supplier SKU mismatch, supplier endpoint down Fix SKU mapping; wait for supplier recovery.
PMS (Opera) Room not found, folio closed, credit limit Confirm reservation state with the hotel admin; see Post charges to Opera PMS.
Payroll (ADP Run) Token invalid, employee not mapped, earning code missing Re-authorize; fix mapping; ask ADP to add missing codes.
Tips payout Inactive Wisely/MyZen account, center account inactive Onboard employee account; reactivate center provider account.
Club (CSI) Field mismatch, API unreachable Fix mapping; confirm CSI availability.
Communication (Zoom, WhatsApp) Token expired, license limit, template rejected Re-authorize; add licenses; revise template.

Reconciliation

Use the health dashboard alongside integration-specific reconciliation steps. Each integration's reconciliation guidance is documented in its own workflow article (for example, Post charges to Opera PMS, Sync payroll data with ADP, Process tips payouts).

Source View Match key Cadence
Zenoti Integration health dashboard + sync log Record ID per integration Daily for financial integrations; weekly for others
External system Provider-specific report The match key documented in each integration's reconciliation section As above

Tips

  • Check the integration health dashboard daily for integrations processing financial data.
  • Set a regular review cadence (weekly or monthly) for lower-frequency integrations.
  • If multiple integrations show errors at once, investigate whether a shared dependency (network, identity provider, provider outage) is the cause before treating each one separately.

Was this article helpful?
Your feedback helps us improve our documentation.