Pingdom is a web performance monitoring service that allows users to monitor the uptime and performance of websites, servers, and applications.
Pingdom is a web performance monitoring service that allows users to monitor the uptime and performance of websites, servers, and applications. On Nagent, Pingdom is exposed as a fully-configurable server monitoring integration that any agent can call — 13 actions, and API key authentication. No code is required to wire Pingdom into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Pingdom to automate the kinds of tasks server monitoring teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Pingdom into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Pingdom, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PINGDOM_GET_ACTIONS_ALERTSRetrieves configured alert actions (notifications) from your Pingdom account. Alert actions define how and where notifications are sent when checks trigger alerts (e.g., email, SMS, webhooks, integrations like Slack/PagerDuty). Use this to list all actions or filter by specific checks, users, delivery channels, or time ranges. Supports pagination for large result sets.
Input parameters
List of notification delivery channels to filter by. Tested values: 'email', 'sms'. Note: Other integration types may not be supported by this filter parameter.
Maximum number of alert actions to return per request. Valid range: 1-100.
Starting index for pagination (offset). Use with limit for paginating through results.
Filter actions created/triggered before this Unix timestamp (in seconds). Use with starttime for time-range queries.
List of user IDs to filter actions. Only returns actions created by or assigned to these specific users.
List of check IDs to filter actions. Only returns actions associated with these specific uptime/transaction checks.
Filter actions created/triggered after this Unix timestamp (in seconds). Use for time-range queries.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_CHECKS_LISTRetrieves a list of all uptime/monitoring checks configured in Pingdom with optional filtering and pagination. Use this to: view all monitoring checks, filter by status/type/tags, search by name, or paginate through large check lists. Returns check details including ID, name, hostname, status, type, resolution, and optional tags.
Input parameters
Filter checks by name (partial match allowed)
Comma-separated list of tags to filter checks
Filter checks by team ID
Type of check to filter (e.g., http, tcp, udp)
Maximum number of checks to return (1-250)
Index of the first check to return for pagination (zero-based)
Filter checks by status (up, down, paused)
Comma-separated list of probe IDs for filtering checks
If true, only return transaction checks
If true, include tag details with each check
Comma-separated list of integration IDs for filtering
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_CONTACT_DETAILSRetrieves comprehensive details of a specific Pingdom alerting contact by ID, including all configured notification methods (email, SMS), team memberships, contact type, and pause status. Use this when you need complete information about a contact's notification configuration.
Input parameters
Unique identifier of the alerting contact to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_CONTACTSTool to retrieve all alerting contacts. Use when you need to list every contact along with their notification targets after establishing a Pingdom session.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_CREDITSRetrieves comprehensive account information including check limits, SMS credits, and resource usage. Use this to monitor available checks (uptime and transaction), SMS credits, RUM sites, and alerting user capacity. Returns current usage counts and available slots for all resource types.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_LIST_MAINTENANCE_OCCURRENCESTool to list maintenance occurrences. Use when you need occurrences filtered by time range or a specific maintenance window ID.
Input parameters
Maximum number of occurrences to return
Start listing from this occurrence offset
Unix timestamp marking the end of the time range for occurrences
Unix timestamp marking the start of the time range to retrieve occurrences
Filter occurrences by a specific maintenance window ID
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_MAINTENANCE_WINDOWSTool to retrieve a list of maintenance windows. Use when you need to list user's maintenance windows with optional pagination and time range filters.
Input parameters
Number of maintenance windows per page (1-1000)
Offset for pagination (zero-based)
Only maintenance windows starting before this Unix timestamp
Only maintenance windows starting after this Unix timestamp
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_PROBESRetrieves the complete list of Pingdom probe servers worldwide. This action returns all available probe servers that can be used for monitoring checks. Probes are distributed globally across regions (NA, EU, APAC, LATAM) and provide information about their location, IP addresses (IPv4 and IPv6), and availability status. Use this when you need to: - List all available monitoring locations - Select probes for creating uptime or transaction checks - Identify probe servers by region or country - Get IP addresses of probe servers for allowlisting
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_REFERENCE_DATARetrieves Pingdom reference data including regions, timezones, datetime formats, number formats, and countries. This data is used for configuring Pingdom account settings, checks, and understanding available formatting options. Use this when you need to know valid timezone IDs, region configurations, or country codes for Pingdom operations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_SINGLE_CHECKPerform a single on-demand Pingdom check against a target host. This executes an immediate test from a specified probe (or random probe if not specified) and returns the result. Use this when you need a quick connectivity or performance test of a website, server, or service. Example uses: "Test if google.com is reachable", "Check response time for example.com from a specific region", "Verify HTTP status of api.mysite.com".
Input parameters
Full URL path for HTTP checks (e.g., '/status')
Hostname or IP address to test
Port number for tcp/udp checks (1-65535)
Type of check to perform
Pingdom probe ID to execute the check from. If not specified, a random probe will be used
Expected IP address for DNS checks. Required when type is 'dns'
String to send to the server for TCP/UDP checks. Required for UDP checks
String to expect in response for TCP/UDP checks
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_TEAM_DETAILSTool to fetch detailed information for a specific alerting team. Use after listing teams to get full members and integrations details.
Input parameters
Unique identifier of the Pingdom alerting team
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_TEAMSTool to retrieve all alerting teams and their members. Use after authenticating to Pingdom to manage team configurations.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PINGDOM_GET_TMS_TRANSACTION_CHECKS_LISTRetrieves a paginated list of all transaction (TMS) checks configured in Pingdom. Transaction checks (also called TMS checks) are synthetic monitoring tests that simulate user interactions with web applications by executing scripted sequences of actions. Use this action to: - Get an overview of all configured transaction checks - Retrieve check IDs, names, types, and current status - Paginate through large lists of transaction checks Returns an empty list if no transaction checks are configured.
Input parameters
Maximum number of transaction checks to return per page (1-1000). Defaults to 1000 if not specified.
Zero-based index to start returning transaction checks from. Use with limit for pagination (e.g., offset=0 for first page, offset=100 for second page with limit=100).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 64 agents privately built on Nagent that already use Pingdom.
Build on Nagent
Connect Pingdom to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Pingdom, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Pingdom is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Pingdom is connected, you configure its 13 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Pingdom steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Pingdom event fires, the agent kicks off automatically.
Every Pingdom action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Pingdom ships with 13 pre-built server monitoring actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Pingdom together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Pingdom-based workflows tailored to your business.