Skip to main content

​
Integration Health

The Integration Health system monitors all your connected services in real time — tracking connection status, token expiry, failure rates, and generating smart suggestions to keep everything running smoothly.

​
Health Status

Each connected integration reports one of five statuses:

​
How status is determined

The engine derives health status automatically from three signals:
Token expiry takes priority over failure count. If a token is expired, the status is always Expired regardless of failure count.

​
Health Summary

The dashboard displays an aggregated health summary across all connected integrations:

​
Dashboard view

The Today view shows a compact health bar at the top. Services that need attention are highlighted with their status icon and a brief description of the issue.

​
Token Expiry Tracking

For integrations using OAuth tokens, OpenPawz tracks expiry dates and warns you before they expire.
Not all integrations have token expiry. API key–based services (like GitHub personal access tokens or Stripe API keys) don’t expire automatically — their status is based solely on failure count.

​
Smart Suggestions

When integrations are connected, OpenPawz generates contextual suggestions on the Today view to help you get started each day.

​
Available suggestions

Suggestions are capped at 3 per session to avoid information overload. They’re generated from your connected services — disconnected services don’t generate suggestions.

​
Service Health Data

Each integration tracks the following metrics:

​
Chain Rules

Chain rules let you create automated follow-up actions when specific integration events occur. For example: “When a GitHub issue is created, post a message to Slack.”

​
Rule structure

​
Example chains

Chain rules are a lightweight alternative to full n8n workflows. Use them for simple “if-this-then-that” automation. For complex multi-step flows, use the n8n integration instead.