What this workflow does
This workflow automates managing website monitors using UptimeRobot API within n8n.
It creates new monitors, updates monitor names, and retrieves monitor status automatically.
This removes manual steps and saves time when checking if websites are online.
Who should use this workflow
This is useful for people managing many websites who want to track uptime easily.
No need to open dashboards or type commands manually after setup.
Tools and services used
- n8n: Automation platform where workflow runs.
- UptimeRobot API: Service to create, update, and get website monitor info.
- UptimeRobot API Key: Needed for authentication in API calls.
How this workflow works
Inputs
The main inputs are website URL and monitor names you want to use.
The API Key connects n8n to UptimeRobot.
Processing steps
- The workflow first uses UptimeRobot node to create a monitor with URL and name.
- It sends monitor ID from creation to another UptimeRobot node which updates the monitor’s friendly name.
- Finally, a third UptimeRobot node uses that ID to get the monitor’s status.
- Nodes are linked in sequence so each runs after the previous one finishes.
Output
The output is the current status and details of the created website monitor.
This can be used for reports, alerts, or tracking uptime automatically.
Beginner step-by-step: How to use this workflow in n8n
Import the workflow
- Download the workflow file using the Download button on this page.
- Open n8n editor.
- Click ‘Import from File’ and choose the downloaded workflow file.
Configure the workflow
- Add your UptimeRobot API Key in the credentials section.
- Check the first UptimeRobot node and change the URL of the website to monitor if needed.
- Modify the friendly name fields in update node if you want a different monitor name.
- Ensure the ID fields use expression
{{$json["id"]}}to connect nodes correctly.
Test and activate
- Run the workflow once manually to make sure nodes work and monitors are created and updated.
- Turn on the workflow toggle button to activate it in production.
Customization ideas
- Change the monitored URL in the create monitor node to track different websites.
- Use dynamic expressions in update node to give names based on input data.
- Add other UptimeRobot monitoring types like ping or port by changing the create node’s type field.
Common problems and fixes
- Invalid API key errors: Check if the API Key in n8n is correct and not expired. Generate a new key from UptimeRobot dashboard if needed.
- Name update not working: Verify the monitor ID is mapped correctly as
{{$json["id"]}}between create and update node.
Pre-production checks
- Test the create node separately to ensure API calls succeed.
- Run each node to verify proper output data and connections.
- Confirm all nodes are linked and pass IDs correctly.
Deployment instructions
Turn on the workflow to enable automation.
Watch execution logs for errors.
Confirm the website monitors appear and update correctly in UptimeRobot dashboard.
If using self-host n8n, keep your server and API key active to avoid failures.
Summary of results
✓ The workflow automatically creates, renames, and fetches website monitor status.
✓ It reduces manual work and errors in uptime monitoring tasks.
✓ The result is live status information that can support alerts and reports.