Site24x7
Developer ToolsKeep uptime monitoring in step with your workflows through Site24x7, Zoho's monitoring platform. Agents create and manage monitors, organize monitor groups, read live up, down, or trouble status, and pull uptime and performance summary reports.
What This Integration Enables
Monitoring coverage decays the same way documentation does: the infrastructure changes and the monitor list quietly stops matching it. This connector makes Site24x7 something your workflows maintain rather than something an engineer remembers to update. FlowRunner agents create URL monitors when endpoints go live, organize them into monitor groups that mirror the actual inventory, suspend and reactivate checks around planned maintenance, and read live up, down, or trouble status across the whole fleet in one call. The coverage disciplines this enables: - Monitors created by the provisioning flow itself, never by a follow-up ticket - Maintenance silence that is deliberate, logged, and reversed on schedule - Fleet status read in one call and reconciled against the inventory that should exist - Escalations that arrive with per-location diagnosis already attached The other half is evidence. Get Summary Report turns uptime from a claim into a number with downtime, outage counts, and mean response time per monitor, which means SLA reporting becomes a scheduled flow instead of a quarterly scramble. And because the connector can also silence and delete monitors, it is a natural fit for FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) discipline: agents propose, engineers rule on anything that would make the fleet go quiet.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Provisioning that ships with its own watcher
When the deployment pipeline brings a new customer site live, the agent calls Create URL Monitor with the endpoint, check frequency, and the standard location, notification, and threshold profiles, then files it into the right customer group with Create Monitor Group or an existing group from List Monitor Groups. Coverage stops being a follow-up task. Every endpoint enters production already watched, and List Monitors reconciled against the infrastructure inventory on a schedule catches anything that slipped through.
Outage detection that routes itself
A frequent sweep reads Get All Current Status. When a monitor reports down, the agent pulls per-location detail with Get Monitor Current Status to separate a regional blip from a global failure, pages the on-call engineer through [PagerDuty](/integrations/pagerduty), posts context to [Slack](/integrations/slack), and opens a public incident on [Statuspage](/integrations/statuspage) when the failure is customer facing. The engineer wakes up to a diagnosis, not a red dot.
The uptime report stakeholders actually receive
Monthly, the agent iterates the fleet with List Monitors and calls Get Summary Report for each: availability percentage, downtime minutes, outage count, mean response time. Rows land in [Google Sheets](/integrations/google-sheets) per customer and per service, and a digest goes to the operations channel with the monitors that missed their SLA highlighted. When a customer asks how their service performed in March, the answer is already in the sheet.
Human-in-Loop Highlight
Delete Monitor is permanent: the monitor and its configuration are gone, checks stop, and the action cannot be undone. The subtler danger is that deleting or suspending the wrong monitor does not break anything visibly. It just means the next real outage on that endpoint goes unwatched, and you discover the blind spot from a customer email. So cleanup flows in this connector never delete on their own judgment. The agent proposes: these six monitors point at decommissioned staging hosts, these two have been suspended for ninety days, here is each one's group and last polled time. The infrastructure owner names which monitors die and which stay. The same rule applies to Suspend Monitor outside a declared maintenance window, because deliberate silence and accidental silence look identical in the dashboard.
Agent Capabilities
13 actionsMonitors
7- List Monitors Retrieves every monitor in the account with ID, name, type, and configuration. The reconciliation step against your infrastructure inventory.
- Get Monitor Retrieves one monitor's full configuration: target, check frequency, and assigned location, notification, and threshold profiles.
- Create URL Monitor Creates a website monitor with display name, URL, check frequency, profiles, and a user group. The step that gives every new endpoint a watcher on day one.
- Update Monitor Changes only the fields you specify on an existing monitor, leaving the rest intact. Used to adjust frequency or repoint a URL after a migration.
- Delete Monitor Permanently deletes a monitor and stops all its checks. The operation this page's human gate exists for.
- Activate Monitor Resumes checks on a suspended monitor. The closing step of every maintenance window.
- Suspend Monitor Stops checks and alerting on a monitor for planned maintenance or an intentionally offline resource. Deliberate silence, applied on the record.
Monitor Groups
2- List Monitor Groups Retrieves all monitor groups with their member monitor IDs. How agents map monitors to customers, services, or environments.
- Create Monitor Group Creates a group with a name, optional description, and initial monitors. Keeps the monitoring taxonomy in step with the infrastructure it mirrors.
Current Status
2- Get All Current Status Returns the live up, down, or trouble status of every monitor in one call. The fleet-wide snapshot behind the outage sweep.
- Get Monitor Current Status Returns one monitor's live status with last polled time and per-location detail. The step that separates a regional blip from a real outage.
Reports
1- Get Summary Report Returns availability percentage, downtime, mean response time, and outage count for a monitor over a chosen period. The raw material of every SLA report on this page.
Users
1- List Users Retrieves account users with role, email, and notification settings. Used to resolve user groups for new monitors and audit who gets paged.
Frequently Asked Questions
What can FlowRunner do with Site24x7?
FlowRunner agents can run List Monitors, Get Monitor, and Create URL Monitor in Site24x7, plus 10 more actions.
Does connecting Site24x7 to FlowRunner require OAuth?
Yes. Site24x7 connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Site24x7 trigger a FlowRunner workflow automatically?
Site24x7 doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Site24x7
$100 in credits. No card required. Connect in minutes.