Resources · Make integration

Site24x7 Make integrationAutomate Site24x7 with Make.

What if every Site24x7 alert started the next step on its own? The Site24x7 Make integration gives you 12 modules: 3 triggers, 7 actions and 2 searches. This guide is for ops and IT leads who connect their account, then build a first scenario step by step.

Try the Site24x7 integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Site24x7 Make integration do for you?

The Site24x7 Make integration links your monitoring account to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes something. With it, Site24x7 monitors, users and alerts feed other tools, and you never write code.

Alerts that reach the right people. Watch New Alert is instant: Site24x7 calls Make the moment an alert is generated. Add Get a Monitor right after and the scenario holds the full monitor record, ready to post in a chat room or log in a ticket.

User accounts that follow your team. A new engineer joins, and Create a User adds them to Site24x7 from your HR tool. Someone leaves, and Delete a User removes the access. Watch Users, on the other side, spots accounts added by hand so you can copy them elsewhere.

A clean monitor inventory. Watch Monitors notices each new monitor, and List Monitors returns the whole set when you want to audit it or push it into a spreadsheet. Delete a Monitor closes the loop on checks you no longer need.

The official doc lists no numeric limit for this app. When a need falls outside the 12 modules, Make an API Call reaches the rest of the Site24x7 API with the same connection. If you are weighing tools, the n8n vs Make comparison sets out the criteria, Make training covers the editor from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect Site24x7 to Make?

  1. 01

    Log in to Site24x7

    Open your Site24x7.com account in the same browser first. Make needs that account to exist, and signing in beforehand makes the authorization window straightforward when it shows up.

  2. 02

    Add the connection in Make

    Insert any Site24x7 module in a scenario, then click Add next to the Connection field. Give it a clear label in Connection name and pick your location in Data Center.

  3. 03

    Approve the access

    Click Accept so Make can read and change data in your account. That link is your connection: every Site24x7 module in every scenario reuses it, so you set it up only once.

First scenario

Your first scenario: enrich each new alert

GoalWhen Site24x7 generates an alert, Make fetches the full record of the monitor involved.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. That empty circle is where the first module goes.

  2. 02

    Pick Watch New Alert

    Search for Site24x7, choose Watch New Alert and click Add to create or reuse your connection. The lightning badge tells you this trigger is instant.

  3. 03

    Add Get a Monitor

    Click the + to the right of the trigger and pick Get a Monitor. Map the monitor from the alert bundle, the item the trigger hands over, instead of picking one by hand. Run once shows you which alert data identifies the monitor.

  4. 04

    Test with Run once

    Click Run once, then let an alert happen in Site24x7. Each module shows a bubble with the bundles it received, so you can check the monitor details arrived.

  5. 05

    Switch it on

    Turn the scenario on. Because the trigger is instant, Site24x7 calls Make through a webhook as soon as an alert is generated, and the scenario starts on its own.

Triggers

Site24x7 triggers in Make

3 modules start a scenario when something happens in Site24x7. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Site24x7 as soon as it happens.

Site24x71Watch Monitors

Watch Monitors

Scheduled trigger

In Make“Triggers when a new monitor is added to Site24x7.”

Watch Monitors picks up each monitor added to Site24x7 at the next scheduled check, so every fresh check gets the same follow-up without anyone remembering it. The result is one bundle per new monitor, ready to log, announce or copy into your inventory.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and the module carries a clock badge.
When to use it
a colleague sets up monitoring for a new website and you want it recorded in the team spreadsheet.
Watch out
it only reacts to new monitors, not to changes on existing ones.
Site24x72Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a new user is added to Site24x7.”

Watch Users picks up the people added to your Site24x7 account at each scheduled check. Each new person arrives as a bundle, which lets you mirror the account list in a directory or tell an admin who just got access.

How it fires
scheduled. Make checks the app on the scenario's schedule; lower the interval in Scheduling if you need it, down to 1 minute on paid plans.
When to use it
a security review asks for a trace of every account created.
Watch out
if your scenario also runs Create a User, keep the two in separate scenarios so each one has a single, clear job.
Site24x73Watch New Alert

Watch New Alert

Instant trigger

In Make“Triggers when a new alert is generated in Site24x7.”

Watch New Alert is the fastest route from a Site24x7 alert to action: the scenario runs the moment an alert is generated, and the alert lands as a bundle you can route anywhere. It is the trigger to reach for when minutes matter.

How it fires
instant. The app calls Make through a webhook as soon as it happens, which the lightning badge on the module shows.
When to use it
an on-call engineer needs a message with the alert in their chat tool, or a ticket opened in the helpdesk.
Watch out
Run once only tests; switch the scenario on afterward so every new alert starts it without you.
Modules

Site24x7 actions and searches in Make

Site24x7 gives you 9 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Monitors

3 modules
Site24x71

List Monitors

Search

In Make“Gets a list of monitors.”

List Monitors hands you your monitors as separate bundles, so a single scenario can review the whole set instead of one check at a time.

When to use it
you prepare an audit and want every monitor copied into a sheet before deciding what to keep.
Watch out
a search can return zero, one or many bundles, and each module after it runs once per bundle, which counts operations on your plan.
Site24x72

Get a Monitor

Action

In Make“Gets an existing monitor.”

Get a Monitor fetches the full record of one monitor you already know, which turns a short alert or an ID into readable details for the next module.

When to use it
right after Watch New Alert, to attach the monitor's details to the message your team receives.
Watch out
it targets a single monitor; to browse several, start with List Monitors instead.
Site24x73

Delete a Monitor

Action

In Make“Deletes an existing monitor.”

Delete a Monitor removes a monitor from Site24x7 as part of a scenario, which keeps your account free of checks for sites that no longer exist.

When to use it
a client project closes in your project tool and its monitors should disappear with it.
Watch out
a deletion does not come back; test with Run once on a throwaway monitor before switching the scenario on.

Users

5 modules
Site24x74

List Users

Search

In Make“Gets a list of all users.”

List Users returns everyone on your Site24x7 account, one bundle per person, which gives you a quick way to compare who has access with who should.

When to use it
an access review needs the full user list next to your HR directory.
Watch out
modules placed after it run for every user it returns, so keep the chain short when the account holds many people.
Site24x75

Get a User

Action

In Make“Gets an existing user.”

Get a User reads the details of one existing user, handy when a scenario knows who it is dealing with and needs the rest of that person's record.

When to use it
after Watch Users, to pull the complete profile before sending a welcome note to the new admin.
Watch out
the user has to exist already; for a list, List Users is the better start.
Site24x76

Create a User

Action

In Make“Creates a new user.”

Create a User adds a new person to your Site24x7 account from another tool, so access arrives on the same day as the rest of the onboarding.

When to use it
a new engineer appears in your HR software or a form, and the scenario opens their Site24x7 account.
Watch out
if the same person can come through twice, check with List Users first to avoid a duplicate.
Site24x77

Update a User

Action

In Make“Updates an existing user.”

Update a User changes an existing account from a scenario, which keeps Site24x7 in step when someone's details move in your source of truth.

When to use it
a team member changes role in your directory and their Site24x7 profile should follow.
Watch out
map the right person every time; pairing it with List Users or Get a User avoids editing the wrong account.
Site24x78

Delete a User

Action

In Make“Deletes an existing user.”

Delete a User takes a person off your Site24x7 account, which closes an access the moment someone leaves instead of waiting for a manual cleanup.

When to use it
an offboarding is recorded in your HR tool and the scenario revokes monitoring access.
Watch out
a deleted user cannot be restored from Make, so feed it only from a clear departure event and test it with Run once on a spare account.

Other

1 module
Site24x79

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call covers whatever the other modules do not: it calls any endpoint of the Site24x7 API with the connection you already set up, so nothing new to authorize.

When to use it
you need a Site24x7 feature that has no dedicated module, for instance something outside monitors, users and alerts.
Watch out
you pick the endpoint yourself, so keep the Site24x7 API documentation open while you fill it in.
Need help

Need help automating Site24x7 with Make?

A person reads every message.

FAQ

Site24x7 and Make: common questions

01Is the Site24x7 Make integration free?
Yes, Site24x7 is a standard app, so it works from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Make counts each operation, meaning one module running on one bundle. Paid plans (Core, Pro, Teams and Enterprise) raise those limits and bring the interval down to 1 minute. You still need your own Site24x7.com account.
02What do you need to connect Site24x7 to Make?
You need a Site24x7.com account and a Make account. Add any Site24x7 module to a scenario, click Add next to the Connection field, name the connection, pick your location in the Data Center field and click Accept. If your organization prefers its own credentials, open Show Advanced Settings and paste a Client ID and Client Secret created with ADD CLIENT in Site24x7. The connection is then reused by every Site24x7 module you add later.
03Do Site24x7 triggers react instantly in Make?
It depends on the trigger. Watch New Alert is instant: Site24x7 calls Make through a webhook as soon as an alert is generated. Watch Monitors and Watch Users are scheduled: Make checks Site24x7 on the scenario's schedule, which is every 15 minutes by default for a new scenario. On the Free plan that interval cannot go below 15 minutes, while paid plans allow 1 minute. For urgent alerts, build on Watch New Alert and keep the scheduled triggers for inventory work.
04What if a Site24x7 module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Site24x7 API with the connection you already created, so you can cover actions that the 12 listed modules leave out. You choose the endpoint and send the request yourself, which asks for a look at the Site24x7 API documentation. The Make doc for this app lists no numeric limit, so the practical boundary is your Make plan: operations, execution time and, on the Free plan, the number of active scenarios.
05Should you use Make or n8n for Site24x7?
It depends on how you like to work, not on a winner. Make gives Site24x7 a ready app with 12 modules, a visual editor, an instant alert trigger and Make an API Call for the rest of the API, all usable from the Free plan. Many apps also have an n8n node, so check whether Site24x7 has one before choosing. Compare the modules each tool offers for your actual use case, then test both on a single alert flow before moving everything.
Same platform

Other docs you might need on this stack.

Browse all integrations