UPTIMEROBOT n8n INTEGRATION: AUTOMATE UPTIMEROBOT WITH N8N

This action retrieves a maximum of 50 public status pages from your UptimeRobot account. It's perfect for building dashboards that display all your status pages or for auditing which status pages exist across your organization.

Key parameters:

• Credential to connect with: Required dropdown to select your UptimeRobot account credentials.
• Resource: Set to "Public Status Page" to target status page data.
• Operation: Set to "Get Many" to retrieve multiple records.
• Return All: Toggle to fetch all available items, overriding any specified limit.
• Limit: Number field (default 50) defining maximum items to retrieve.
• Filters: Optional section to add filtering criteria.

Use cases:

• Audit all status pages across your organization
• Generate a directory of client status pages
• Identify status pages that need updates

Retrieve information about a specific public status page. Use this to verify configuration or pull page details for reporting before sharing with clients.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Public Status Page".
• Operation: Set to "Get" to retrieve a single status page.
• ID: Optional text field for the status page's unique identifier.

Use cases:

• Verify status page includes the correct monitors
• Pull status page URLs for documentation
• Check status page configuration before sharing with clients

Remove a public status page from your account. Essential for cleanup when services are retired or client relationships end.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Public Status Page".
• Operation: Set to "Delete".
• ID: Required text field for the status page to remove.

Use cases:

• Remove status pages for decommissioned services
• Clean up client status pages during offboarding
• Delete test status pages after development

Create public status pages that display the health of your monitored services. Perfect for transparency with customers or internal visibility across teams.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Public Status Page".
• Operation: Set to "Create".
• Friendly Name: Text field for the status page's display name.
• Monitor IDs: Text field to specify which monitors appear on the page.
• Additional Fields: Optional section for custom domains, descriptions, and styling.

Use cases:

• Auto-create client-facing status pages when onboarding new customers
• Build internal status pages for different teams or services
• Set up status pages for new product launches

Modify an existing monitor's configuration without touching the UptimeRobot interface. This is essential for maintaining monitors programmatically—update URLs when domains change, adjust intervals based on service criticality, or enable/disable monitors based on business hours.

Key parameters:

• Credential to connect with: Required authentication dropdown.
• Resource: Set to "Monitor".
• Operation: Set to "Update".
• ID: Required text field specifying which monitor to update.
• Update Fields: Optional section where you add the specific properties to modify (name, URL, interval, status, etc.).

Use cases:

• Update monitor URLs when services migrate to new domains
• Pause monitors during scheduled maintenance windows
• Adjust monitoring intervals based on traffic patterns

Reset a monitor's statistics, clearing its historical uptime data. This is useful after making significant changes to a service or when you want to start fresh with clean metrics.

Key parameters:

• Credential to connect with: Required authentication dropdown.
• Resource: Set to "Monitor".
• Operation: Set to "Reset".
• ID: Required text field specifying which monitor to reset.

Use cases:

• Reset statistics after major service migrations
• Clear historical data when handing over monitoring to a new team
• Start fresh metrics after resolving a prolonged incident

Fetch multiple monitors at once, with optional filtering capabilities. Perfect for building reports, syncing monitor data to external systems, or auditing your monitoring setup.

Key parameters:

• Credential to connect with: Required dropdown for UptimeRobot authentication.
• Resource: Set to "Monitor".
• Operation: Set to "Get Many" to retrieve multiple records.
• Return All: Optional toggle that fetches all monitors when enabled, ignoring the limit.
• Limit: Optional number field (default 50) that caps how many monitors to retrieve.
• Filters: Optional section to narrow results by specific criteria.

Use cases:

• Generate weekly uptime reports across all monitors
• Sync monitor list to a Google Sheet for stakeholder visibility
• Identify monitors that haven't been updated recently

Retrieve detailed information about a specific monitor using its ID. Use it to check a monitor's current status, uptime statistics, or configuration details before making decisions in your workflow.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Monitor".
• Operation: Set to "Get" to retrieve a single monitor.
• ID: Optional text field for the monitor's unique identifier.

Use cases:

• Check if a monitor is currently up before running deployment scripts
• Pull monitor statistics for custom reporting
• Verify monitor configuration matches expected values

Remove a monitor from your UptimeRobot account programmatically. Use this to clean up monitors for decommissioned services, maintaining a tidy monitoring environment without manual intervention.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Monitor".
• Operation: Set to "Delete".
• ID: Required text field containing the unique identifier of the monitor to remove.

Use cases:

• Automatically remove monitors when services are decommissioned
• Clean up test monitors after QA environments are torn down
• Delete monitors for churned clients as part of offboarding workflows

Programmatically add new monitors to your UptimeRobot account. It's incredibly powerful for teams managing many services—instead of manually creating monitors, trigger this action from your deployment pipeline, CRM, or any other system.

Key parameters:

• Credential to connect with: Required dropdown for selecting your UptimeRobot credentials.
• Resource: Set to "Monitor" to work with monitoring endpoints.
• Operation: Set to "Create" to add a new monitor.
• Friendly Name: Required text field for the monitor's display name.
• Type: Required dropdown to select the monitor type (HTTP, Keyword, Ping, Port, or Heartbeat).
• URL: Required text field for the endpoint to monitor.

Use cases:

• Auto-create monitors when new services are deployed via CI/CD
• Provision monitoring for new client websites from your onboarding workflow
• Create keyword monitors when new landing pages go live

Modify an existing maintenance window. Useful when deployment schedules change or maintenance needs to be extended.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Maintenance Window".
• Operation: Set to "Update".
• ID: Required text field for the maintenance window to update.
• Duration (Minutes): Number field to adjust the window length.
• Update Fields: Optional section for additional modifications.

Use cases:

• Extend maintenance windows when deployments take longer than expected
• Reschedule maintenance when conflicts arise
• Update maintenance window names for better clarity

Fetch multiple maintenance windows at once. Perfect for building maintenance calendars or auditing your scheduled downtime.

Key parameters:

• Credential to connect with: Required authentication dropdown.
• Resource: Set to "Maintenance Window".
• Operation: Set to "Get Many".
• Return All: Optional toggle to fetch all windows.
• Limit: Optional number field (default 50) for pagination.
• Filters: Optional section for filtering results.

Use cases:

• Build a maintenance calendar in Google Calendar or Notion
• Audit all scheduled maintenance across your infrastructure
• Generate reports on planned downtime

Retrieve details about a specific maintenance window. Useful for verifying scheduled maintenance or pulling information for reporting.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Maintenance Window".
• Operation: Set to "Get".
• ID: Optional text field for the maintenance window's unique identifier.

Use cases:

• Verify maintenance window is scheduled before deployment starts
• Pull maintenance schedule for team calendars
• Check maintenance window configuration

Remove a scheduled maintenance window. Use this when planned maintenance is cancelled or completed early.

Key parameters:

• Credential to connect with: Required authentication dropdown.
• Resource: Set to "Maintenance Window".
• Operation: Set to "Delete".
• ID: Required text field for the maintenance window to remove.

Use cases:

• Cancel maintenance windows when deployments are postponed
• Clean up completed one-time maintenance windows
• Remove outdated recurring maintenance schedules

Schedule maintenance windows programmatically to prevent false alerts during planned downtime. Connect this to your deployment pipeline and never worry about alert storms during releases again.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Maintenance Window".
• Operation: Set to "Create".
• Duration (Minutes): Required number field specifying how long the maintenance window lasts.
• Friendly Name: Required text field for the maintenance window's display name.
• Type: Required dropdown for recurrence pattern (once, daily, weekly, monthly).
• Start Time: Required date/time picker for when the maintenance begins.

Use cases:

• Auto-create maintenance windows before CI/CD deployments
• Schedule recurring maintenance for regular update cycles
• Coordinate maintenance across multiple time zones

Modify an existing alert contact's details. Keep your notification recipients up to date when email addresses change, phone numbers are updated, or team members move to different roles.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Alert Contact".
• Operation: Set to "Update".
• ID: Required text field specifying which contact to update.
• Update Fields: Optional section to add specific properties to modify.

Use cases:

• Update email addresses when team members change roles
• Modify webhook URLs when notification endpoints change
• Rename contacts to reflect updated team structures

Fetch multiple alert contacts at once. This is useful for auditing your notification setup, syncing contacts to external systems, or building custom alert management interfaces.

Key parameters:

• Credential to connect with: Required authentication dropdown.
• Resource: Set to "Alert Contact".
• Operation: Set to "Get Many".
• Return All: Optional toggle to fetch all contacts.
• Limit: Optional number field (default 50) for pagination.
• Filters: Optional section to filter contacts by specific criteria.

Use cases:

• Audit all alert contacts for compliance reviews
• Sync contact list to your team directory
• Identify inactive or outdated alert contacts

Retrieve details about a specific alert contact. Use this to verify contact configuration or pull contact information for reporting purposes.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Alert Contact".
• Operation: Set to "Get".
• ID: Optional text field for the alert contact's unique identifier.

Use cases:

• Verify an alert contact exists before assigning it to a new monitor
• Pull contact details for compliance audits
• Check notification settings before critical deployments

Remove an alert contact from your account. Essential for offboarding workflows to ensure former team members stop receiving alerts.

Key parameters:

• Credential to connect with: Required authentication dropdown.
• Resource: Set to "Alert Contact".
• Operation: Set to "Delete".
• ID: Required text field for the contact to remove.

Use cases:

• Remove contacts when team members leave the organization
• Clean up temporary contacts after project completion
• Delete test contacts after workflow development

Add new alert contacts to your UptimeRobot account programmatically. This lets you keep your notification recipients in sync with your team roster, PagerDuty rotations, or on-call schedules.

Key parameters:

• Credential to connect with: Required dropdown for authentication.
• Resource: Set to "Alert Contact".
• Operation: Set to "Create".
• Friendly Name: Required text field for the contact's display name.
• Type: Required dropdown to select the notification method (email, SMS, webhook, etc.).
• Value: Required text field for the actual contact detail (email address, phone number, webhook URL).

Use cases:

• Sync alert contacts from your HR system when new team members join
• Create webhook alert contacts for custom notification integrations
• Add temporary contacts for on-call rotations