Pingdom integration

Quick start

Call Pingdom from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Pingdom's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "PINGDOM_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own Pingdom API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

13 actions exposed via the Pingdom integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• PINGDOM_GET_ACTIONS_ALERTS
• PINGDOM_GET_CHECKS_LIST
• PINGDOM_GET_CONTACT_DETAILS
• PINGDOM_GET_CONTACTS
• PINGDOM_GET_CREDITS
• PINGDOM_GET_LIST_MAINTENANCE_OCCURRENCES
• PINGDOM_GET_MAINTENANCE_WINDOWS
• PINGDOM_GET_PROBES
• PINGDOM_GET_REFERENCE_DATA
• PINGDOM_GET_SINGLE_CHECK
• PINGDOM_GET_TEAM_DETAILS
• PINGDOM_GET_TEAMS