UptimeRobot

Overview

Connect UptimeRobot with Flows360

Monitor your websites, APIs, and servers. Get alerted when things go down.

Use the UptimeRobot connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and no declared triggers.

Available actions

• Get Monitors
• Create HTTP Monitor
• Edit Monitor
• Delete Monitor
• Pause or Resume Monitor

Available triggers

• No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

• Connector: UptimeRobot
• Package: @activepieces/piece-uptimerobot@0.0.5
• Exact artifact digest: sha256:efc79b5b49458edf0165a0aaa5764a25c40d4464dc4a5aeda32f2f2c9dfba7b6
• Runtime: Activepieces-compatible deterministic worker
• Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

• Get Monitors (get_monitors), List and search your UptimeRobot monitors with optional filters. Leave the Monitors / Monitor IDs fields empty to return all monitors. Classification: read.
• Create HTTP Monitor (create_monitor), Create a new HTTP uptime monitor in UptimeRobot Classification: read.
• Edit Monitor (edit_monitor), Update the settings of an existing UptimeRobot monitor Classification: read.
• Delete Monitor (delete_monitor), Permanently delete a monitor from UptimeRobot. This cannot be undone. Classification: read.
• Pause or Resume Monitor (pause_resume_monitor), Temporarily pause or resume monitoring for a specific monitor. Classification: read.

Trigger contracts

• No trigger delivery contracts are declared.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authentication

Authentication method: custom

Authentication profiles

Supported objects

Setup

Setup

1. Add the UptimeRobot connector to the workflow in the target Flows360 Studio instance.
2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
3. Provide the connection fields declared by the pinned package:

• No provider credential fields are declared by the pinned package.

1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

• This content describes @activepieces/piece-uptimerobot@0.0.5; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 5 actions and 0 triggers declared by this pinned package are represented here.
• Tenant credentials and connection values are not stored in the public connector record.
• Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
• Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Related documentation