[{"data":1,"prerenderedAt":1533},["ShallowReactive",2],{"home-blog":3},[4,743,1143],{"id":5,"title":6,"author":7,"body":8,"category":717,"date":718,"description":719,"extension":720,"faqs":721,"image":734,"meta":737,"navigation":738,"path":739,"readingTime":204,"seo":740,"stem":741,"__hash__":742},"blog\u002Fblog\u002Fhow-to-connect-monitoristic-to-n8n-make-zapier.md","How to Connect Monitoristic to n8n, Make, and Zapier","Monitoristic Team",{"type":9,"value":10,"toc":707},"minimark",[11,31,34,37,42,45,66,69,73,76,360,372,387,391,398,403,443,448,456,463,467,474,478,510,515,521,524,528,535,539,573,578,584,587,591,594,600,606,617,623,629,633,644,655,662,666,686,689,697,703],[12,13,14,15,20,21,25,26,30],"p",{},"Monitoristic tells you the moment your site goes down — via ",[16,17,19],"a",{"href":18},"\u002Fdocs\u002Ftelegram","Telegram"," or ",[16,22,24],{"href":23},"\u002Fdocs\u002Fwebhooks","webhooks",". But what if you want more than a notification? What if you want your downtime alert to ",[27,28,29],"em",{},"do something"," — create a ticket, escalate to your on-call engineer, log the incident, or trigger an automated recovery?",[12,32,33],{},"That's where automation platforms come in. n8n, Make, and Zapier all accept incoming webhooks, which means you can pipe Monitoristic alerts into any workflow you can imagine.",[12,35,36],{},"This guide shows you how to connect Monitoristic to all three.",[38,39,41],"h2",{"id":40},"how-it-works","How It Works",[12,43,44],{},"The mechanism is the same for every platform:",[46,47,48,57,60,63],"ol",{},[49,50,51,52,56],"li",{},"The automation tool gives you a ",[53,54,55],"strong",{},"webhook URL"," — a unique address that listens for incoming data.",[49,58,59],{},"You paste that URL into Monitoristic's webhook settings.",[49,61,62],{},"When a monitor goes down (or recovers), Monitoristic sends a JSON payload to that URL.",[49,64,65],{},"Your workflow receives the data and runs whatever steps you've built.",[12,67,68],{},"No code required on your end. You build the logic visually in the automation tool.",[38,70,72],{"id":71},"the-monitoristic-webhook-payload","The Monitoristic Webhook Payload",[12,74,75],{},"Before connecting anything, it helps to know what data you'll receive. When a monitor goes down or recovers, Monitoristic sends this JSON:",[77,78,83],"pre",{"className":79,"code":80,"language":81,"meta":82,"style":82},"language-json shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","{\n  \"event\": \"monitor.down\",\n  \"monitor\": {\n    \"id\": \"a1b2c3d4-e5f6-7890-abcd-ef1234567890\",\n    \"name\": \"My Website\",\n    \"url\": \"https:\u002F\u002Fexample.com\"\n  },\n  \"incident\": {\n    \"id\": \"f9e8d7c6-b5a4-3210-fedc-ba9876543210\",\n    \"title\": \"My Website is down\"\n  },\n  \"check\": {\n    \"status_code\": 500,\n    \"response_time\": 1234,\n    \"error\": null\n  },\n  \"timestamp\": \"2026-05-02T12:00:00.000Z\"\n}\n","json","",[84,85,86,95,123,138,161,182,202,208,222,242,261,266,280,298,315,330,335,354],"code",{"__ignoreMap":82},[87,88,91],"span",{"class":89,"line":90},"line",1,[87,92,94],{"class":93},"sMK4o","{\n",[87,96,98,101,105,108,111,114,118,120],{"class":89,"line":97},2,[87,99,100],{"class":93},"  \"",[87,102,104],{"class":103},"spNyl","event",[87,106,107],{"class":93},"\"",[87,109,110],{"class":93},":",[87,112,113],{"class":93}," \"",[87,115,117],{"class":116},"sfazB","monitor.down",[87,119,107],{"class":93},[87,121,122],{"class":93},",\n",[87,124,126,128,131,133,135],{"class":89,"line":125},3,[87,127,100],{"class":93},[87,129,130],{"class":103},"monitor",[87,132,107],{"class":93},[87,134,110],{"class":93},[87,136,137],{"class":93}," {\n",[87,139,141,144,148,150,152,154,157,159],{"class":89,"line":140},4,[87,142,143],{"class":93},"    \"",[87,145,147],{"class":146},"sBMFI","id",[87,149,107],{"class":93},[87,151,110],{"class":93},[87,153,113],{"class":93},[87,155,156],{"class":116},"a1b2c3d4-e5f6-7890-abcd-ef1234567890",[87,158,107],{"class":93},[87,160,122],{"class":93},[87,162,164,166,169,171,173,175,178,180],{"class":89,"line":163},5,[87,165,143],{"class":93},[87,167,168],{"class":146},"name",[87,170,107],{"class":93},[87,172,110],{"class":93},[87,174,113],{"class":93},[87,176,177],{"class":116},"My Website",[87,179,107],{"class":93},[87,181,122],{"class":93},[87,183,185,187,190,192,194,196,199],{"class":89,"line":184},6,[87,186,143],{"class":93},[87,188,189],{"class":146},"url",[87,191,107],{"class":93},[87,193,110],{"class":93},[87,195,113],{"class":93},[87,197,198],{"class":116},"https:\u002F\u002Fexample.com",[87,200,201],{"class":93},"\"\n",[87,203,205],{"class":89,"line":204},7,[87,206,207],{"class":93},"  },\n",[87,209,211,213,216,218,220],{"class":89,"line":210},8,[87,212,100],{"class":93},[87,214,215],{"class":103},"incident",[87,217,107],{"class":93},[87,219,110],{"class":93},[87,221,137],{"class":93},[87,223,225,227,229,231,233,235,238,240],{"class":89,"line":224},9,[87,226,143],{"class":93},[87,228,147],{"class":146},[87,230,107],{"class":93},[87,232,110],{"class":93},[87,234,113],{"class":93},[87,236,237],{"class":116},"f9e8d7c6-b5a4-3210-fedc-ba9876543210",[87,239,107],{"class":93},[87,241,122],{"class":93},[87,243,245,247,250,252,254,256,259],{"class":89,"line":244},10,[87,246,143],{"class":93},[87,248,249],{"class":146},"title",[87,251,107],{"class":93},[87,253,110],{"class":93},[87,255,113],{"class":93},[87,257,258],{"class":116},"My Website is down",[87,260,201],{"class":93},[87,262,264],{"class":89,"line":263},11,[87,265,207],{"class":93},[87,267,269,271,274,276,278],{"class":89,"line":268},12,[87,270,100],{"class":93},[87,272,273],{"class":103},"check",[87,275,107],{"class":93},[87,277,110],{"class":93},[87,279,137],{"class":93},[87,281,283,285,288,290,292,296],{"class":89,"line":282},13,[87,284,143],{"class":93},[87,286,287],{"class":146},"status_code",[87,289,107],{"class":93},[87,291,110],{"class":93},[87,293,295],{"class":294},"sbssI"," 500",[87,297,122],{"class":93},[87,299,301,303,306,308,310,313],{"class":89,"line":300},14,[87,302,143],{"class":93},[87,304,305],{"class":146},"response_time",[87,307,107],{"class":93},[87,309,110],{"class":93},[87,311,312],{"class":294}," 1234",[87,314,122],{"class":93},[87,316,318,320,323,325,327],{"class":89,"line":317},15,[87,319,143],{"class":93},[87,321,322],{"class":146},"error",[87,324,107],{"class":93},[87,326,110],{"class":93},[87,328,329],{"class":93}," null\n",[87,331,333],{"class":89,"line":332},16,[87,334,207],{"class":93},[87,336,338,340,343,345,347,349,352],{"class":89,"line":337},17,[87,339,100],{"class":93},[87,341,342],{"class":103},"timestamp",[87,344,107],{"class":93},[87,346,110],{"class":93},[87,348,113],{"class":93},[87,350,351],{"class":116},"2026-05-02T12:00:00.000Z",[87,353,201],{"class":93},[87,355,357],{"class":89,"line":356},18,[87,358,359],{"class":93},"}\n",[12,361,362,363,365,366,20,368,371],{},"The ",[84,364,104],{}," field is either ",[84,367,117],{},[84,369,370],{},"monitor.recovered",". You'll use these fields to build conditional logic — for example, \"if event is monitor.down, create a ticket; if monitor.recovered, close it.\"",[12,373,374,375,378,379,382,383,386],{},"There's also a separate payload for ",[16,376,377],{"href":23},"maintenance events"," (",[84,380,381],{},"maintenance.started",", ",[84,384,385],{},"maintenance.completed",", etc.) if you want to automate around planned downtime.",[38,388,390],{"id":389},"connecting-to-n8n","Connecting to n8n",[12,392,393,397],{},[16,394,396],{"href":395},"\u002Fmonitor\u002Fn8n","n8n"," is a powerful, often self-hosted automation tool that developers love for its flexibility.",[12,399,400],{},[53,401,402],{},"Steps:",[46,404,405,412,423,429,440],{},[49,406,407,408,411],{},"In n8n, create a new workflow and add a ",[53,409,410],{},"Webhook"," node as the trigger.",[49,413,414,415,418,419,422],{},"Set the HTTP method to ",[53,416,417],{},"POST"," and copy the ",[53,420,421],{},"Production URL"," n8n generates.",[49,424,425,426,428],{},"In Monitoristic, go to your notification settings, add a ",[53,427,410],{}," channel, and paste the n8n URL.",[49,430,431,432,435,436,439],{},"Back in n8n, add the nodes you want to run — an ",[53,433,434],{},"IF"," node to branch on ",[84,437,438],{},"{{$json.event}}",", then actions like creating a ticket or posting to Slack.",[49,441,442],{},"Activate the workflow.",[12,444,445],{},[53,446,447],{},"Example n8n workflow:",[77,449,454],{"className":450,"code":452,"language":453},[451],"language-text","Webhook (trigger)\n  → IF event == \"monitor.down\"\n      → Jira: Create Issue (title from incident.title)\n      → Slack: Post to #incidents\n  → IF event == \"monitor.recovered\"\n      → Jira: Transition Issue to Done\n      → Slack: Post \"Resolved\" message\n","text",[84,455,452],{"__ignoreMap":82},[12,457,458,459,462],{},"Because n8n is code-friendly, you can also drop in a ",[53,460,461],{},"Function"," node to transform the payload, enrich it with data from other APIs, or build complex routing logic.",[38,464,466],{"id":465},"connecting-to-make","Connecting to Make",[12,468,469,473],{},[16,470,472],{"href":471},"\u002Fmonitor\u002Fmake","Make"," (formerly Integromat) uses a visual scenario builder that's great for connecting many apps together.",[12,475,476],{},[53,477,402],{},[46,479,480,487,494,500,503],{},[49,481,482,483,486],{},"In Make, create a new scenario and add a ",[53,484,485],{},"Webhooks → Custom webhook"," module as the trigger.",[49,488,489,490,493],{},"Click ",[53,491,492],{},"Add",", name the webhook, and copy the generated URL.",[49,495,496,497,499],{},"In Monitoristic, add a ",[53,498,410],{}," notification channel and paste the Make URL.",[49,501,502],{},"Trigger a test from Monitoristic (or wait for a real event) so Make can detect the data structure.",[49,504,505,506,509],{},"Add modules after the webhook — a ",[53,507,508],{},"Router"," to branch on the event type, then actions like creating records or sending messages.",[12,511,512],{},[53,513,514],{},"Example Make scenario:",[77,516,519],{"className":517,"code":518,"language":453},[451],"Custom webhook (trigger)\n  → Router\n      → Route 1 (event = monitor.down): Trello → Create Card + Email → Send\n      → Route 2 (event = monitor.recovered): Trello → Archive Card\n",[84,520,518],{"__ignoreMap":82},[12,522,523],{},"Make's strength is the breadth of app integrations — if you use a tool, Make probably connects to it.",[38,525,527],{"id":526},"connecting-to-zapier","Connecting to Zapier",[12,529,530,534],{},[16,531,533],{"href":532},"\u002Fmonitor\u002Fzapier","Zapier"," is the most beginner-friendly of the three, with the largest catalog of app integrations.",[12,536,537],{},[53,538,402],{},[46,540,541,548,555,560,563],{},[49,542,543,544,547],{},"In Zapier, create a new Zap and choose ",[53,545,546],{},"Webhooks by Zapier"," as the trigger.",[49,549,550,551,554],{},"Select ",[53,552,553],{},"Catch Hook"," as the event and copy the custom webhook URL.",[49,556,496,557,559],{},[53,558,410],{}," notification channel and paste the Zapier URL.",[49,561,562],{},"Send a test event so Zapier can parse the fields.",[49,564,565,566,569,570,572],{},"Add action steps — use a ",[53,567,568],{},"Filter"," to run only on ",[84,571,117],{},", then connect actions like Slack, Google Sheets, or PagerDuty.",[12,574,575],{},[53,576,577],{},"Example Zap:",[77,579,582],{"className":580,"code":581,"language":453},[451],"Catch Hook (trigger)\n  → Filter: only continue if event = monitor.down\n  → PagerDuty: Create Incident\n  → Google Sheets: Add Row (log the downtime)\n",[84,583,581],{"__ignoreMap":82},[12,585,586],{},"Zapier's filters and paths make it easy to build conditional logic without any technical setup.",[38,588,590],{"id":589},"real-workflow-ideas","Real Workflow Ideas",[12,592,593],{},"Once your alerts flow into an automation tool, here's what you can build:",[12,595,596,599],{},[53,597,598],{},"Incident ticketing","\nDowntime automatically creates a ticket in Jira, Linear, or Trello with the monitor name, URL, and status code pre-filled. Recovery closes it. Your incident log builds itself.",[12,601,602,605],{},[53,603,604],{},"Smart escalation","\nPost to Slack immediately. If the monitor is still down after 10 minutes (use a delay step), escalate by sending an SMS or calling your on-call engineer via PagerDuty.",[12,607,608,611,612,616],{},[53,609,610],{},"Incident logging","\nEvery downtime and recovery event gets logged to a Google Sheet or database with timestamps. Over time, you build a complete incident history you can analyze for patterns — exactly the kind of data covered in ",[16,613,615],{"href":614},"\u002Fblog\u002Fhow-to-read-an-uptime-report","how to read an uptime report",".",[12,618,619,622],{},[53,620,621],{},"Automated response","\nFor some failures, you can trigger a fix. A webhook can call your hosting provider's API to restart a service, clear a cache, or scale up resources — turning detection into automatic remediation.",[12,624,625,628],{},[53,626,627],{},"Multi-channel broadcast","\nFan out a single downtime alert to Slack, email, a status page update, and a team SMS — all from one Monitoristic webhook.",[38,630,632],{"id":631},"a-note-on-reliability","A Note on Reliability",[12,634,635,636,382,638,640,641,643],{},"One important detail: if you're routing critical alerts through an automation platform, remember that platform is now part of your alert chain. If ",[16,637,396],{"href":395},[16,639,472],{"href":471},", or ",[16,642,533],{"href":532}," has an outage, your automated alerts could be delayed or dropped.",[12,645,646,647,650,651,654],{},"For mission-critical alerts (like a checkout outage), it's wise to keep a ",[53,648,649],{},"direct"," notification channel too — a ",[16,652,653],{"href":18},"Telegram alert"," straight from Monitoristic that doesn't depend on any third party. Use the automation platform for the rich workflow (tickets, logging, escalation) and keep a direct channel as your reliable backstop.",[12,656,657,658,661],{},"This is also why it's worth ",[16,659,660],{"href":395},"monitoring your automation tool itself"," — especially if you self-host n8n.",[38,663,665],{"id":664},"get-started","Get Started",[46,667,668,671,674,680,683],{},[49,669,670],{},"Pick your automation platform (n8n, Make, or Zapier)",[49,672,673],{},"Create a workflow with a webhook trigger and copy the URL",[49,675,496,676,679],{},[16,677,678],{"href":23},"webhook notification channel"," and paste the URL",[49,681,682],{},"Build your workflow steps",[49,684,685],{},"Test it, then let it run",[12,687,688],{},"From there, every downtime event becomes the start of an automated workflow — not just a notification you have to act on manually.",[12,690,691],{},[16,692,696],{"href":693,"rel":694},"https:\u002F\u002Fapp.monitoristic.com\u002Fregister",[695],"nofollow","Start monitoring with Monitoristic →",[12,698,699,700,616],{},"For the full webhook reference, see the ",[16,701,702],{"href":23},"webhook integration docs",[704,705,706],"style",{},"html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html pre.shiki code .spNyl, html code.shiki .spNyl{--shiki-light:#9C3EDA;--shiki-default:#C792EA;--shiki-dark:#C792EA}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}html pre.shiki code .sBMFI, html code.shiki .sBMFI{--shiki-light:#E2931D;--shiki-default:#FFCB6B;--shiki-dark:#FFCB6B}html pre.shiki code .sbssI, html code.shiki .sbssI{--shiki-light:#F76D47;--shiki-default:#F78C6C;--shiki-dark:#F78C6C}html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}",{"title":82,"searchDepth":97,"depth":97,"links":708},[709,710,711,712,713,714,715,716],{"id":40,"depth":97,"text":41},{"id":71,"depth":97,"text":72},{"id":389,"depth":97,"text":390},{"id":465,"depth":97,"text":466},{"id":526,"depth":97,"text":527},{"id":589,"depth":97,"text":590},{"id":631,"depth":97,"text":632},{"id":664,"depth":97,"text":665},"Guide","2026-06-01","Route downtime alerts into your automation workflows. Learn how to connect Monitoristic webhooks to n8n, Make, and Zapier to trigger tickets, escalations, and automated responses when your site goes down.","md",[722,725,728,731],{"q":723,"a":724},"Can Monitoristic send alerts to n8n, Make, or Zapier?","Yes. Monitoristic sends webhook notifications — JSON payloads via HTTP POST — when a monitor goes down, recovers, or during maintenance events. n8n, Make, and Zapier all accept incoming webhooks, so you can route Monitoristic alerts into any workflow you build on those platforms.",{"q":726,"a":727},"Do I need to write code to connect Monitoristic to an automation tool?","No. Each platform gives you a webhook URL that listens for incoming data. You paste that URL into Monitoristic's webhook configuration, and downtime alerts flow into your workflow automatically. From there, you build the automation visually — no code required.",{"q":729,"a":730},"What can I automate when my site goes down?","Anything your automation tool can do. Common examples: create a Jira or Trello ticket, post a formatted message to Slack or Microsoft Teams, log the incident to a Google Sheet or database, trigger an escalation chain, send an SMS to your on-call engineer, or even call an API to restart a service.",{"q":732,"a":733},"What data does Monitoristic send in the webhook?","The payload includes the event type (monitor.down, monitor.recovered, or maintenance events), the monitor's name and URL, the incident details, and check data like the HTTP status code, response time, and any error message. Your automation can use any of these fields to build conditional logic.",{"src":735,"alt":736},"\u002Fblog\u002Fblog-connect-monitoristic-to-n8n-make-zapier.webp","Monitoristic downtime alerts flowing into n8n, Make, and Zapier automation workflows",{},true,"\u002Fblog\u002Fhow-to-connect-monitoristic-to-n8n-make-zapier",{"title":6,"description":719},"blog\u002Fhow-to-connect-monitoristic-to-n8n-make-zapier","YyWc_3kUUGEuezuT8_vLER53PXCC86QAeTgsZ69wu64",{"id":744,"title":745,"author":7,"body":746,"category":717,"date":718,"description":1121,"extension":720,"faqs":1122,"image":1135,"meta":1138,"navigation":738,"path":1139,"readingTime":184,"seo":1140,"stem":1141,"__hash__":1142},"blog\u002Fblog\u002Fhow-to-set-up-uptime-monitoring.md","How to Set Up Uptime Monitoring (Step-by-Step for Beginners)",{"type":9,"value":747,"toc":1109},[748,751,754,758,761,764,767,771,774,777,798,801,805,808,821,832,842,852,858,866,870,873,876,884,893,896,902,906,909,929,932,936,939,942,986,993,997,1005,1008,1016,1019,1023,1031,1034,1038,1044,1050,1056,1062,1068,1072,1075,1100,1103],[12,749,750],{},"If you've never set up uptime monitoring before, it can sound more technical than it is. There's no code to write, nothing to install, and no server access required. If you have a URL and two minutes, you can have monitoring running.",[12,752,753],{},"This guide walks you through the whole process from scratch — what monitoring actually does, what to monitor first, how to configure it, and how to make sure alerts actually reach you when something breaks.",[38,755,757],{"id":756},"what-uptime-monitoring-actually-does","What Uptime Monitoring Actually Does",[12,759,760],{},"Uptime monitoring is simple at its core: a service outside your website sends a request to your site at regular intervals and checks whether it responds correctly. If it does, nothing happens. If it doesn't, you get an alert.",[12,762,763],{},"That's it. The monitoring service acts like a robot visitor that checks your site every few minutes, 24\u002F7, and taps you on the shoulder the moment something's wrong.",[12,765,766],{},"Because the monitor runs on separate infrastructure — not on your server — it works even when your entire site is down. That's the key advantage over checking things yourself or relying on a plugin installed on your site.",[38,768,770],{"id":769},"step-1-decide-what-to-monitor-first","Step 1: Decide What to Monitor First",[12,772,773],{},"Don't try to monitor everything at once. Start with the single most important URL on your site.",[12,775,776],{},"For most people, that's one of:",[778,779,780,786,792],"ul",{},[49,781,782,785],{},[53,783,784],{},"Your homepage"," — the most visible page; if it's down, everyone notices",[49,787,788,791],{},[53,789,790],{},"Your main app URL"," — if you run a web app, the dashboard or login page",[49,793,794,797],{},[53,795,796],{},"Your most important landing page"," — if you're running ads or campaigns to a specific page",[12,799,800],{},"Pick one. You'll add more later. Starting with one monitor keeps the setup simple and lets you understand how everything works before scaling up.",[38,802,804],{"id":803},"step-2-create-your-first-monitor","Step 2: Create Your First Monitor",[12,806,807],{},"Setting up a monitor means giving the tool a few pieces of information. Here's what each one means:",[12,809,810,813,814,817,818,616],{},[53,811,812],{},"URL"," — the full address you want to check, including ",[84,815,816],{},"https:\u002F\u002F",". For example, ",[84,819,820],{},"https:\u002F\u002Fyourdomain.com",[12,822,823,826,827,831],{},[53,824,825],{},"Check interval"," — how often the monitor checks your site. For your first monitor, ",[16,828,830],{"href":829},"\u002Fblog\u002Fhow-to-choose-the-right-check-interval","5 minutes"," is a sensible default. It catches any real outage without being aggressive.",[12,833,834,837,838,841],{},[53,835,836],{},"Expected status code"," — the HTTP response that means \"everything's fine.\" For almost every website, this is ",[53,839,840],{},"200"," (which means \"OK\"). Don't change this unless you know your endpoint returns something different.",[12,843,844,847,848,851],{},[53,845,846],{},"HTTP method"," — leave this as ",[53,849,850],{},"GET"," unless you have a specific reason to change it. GET is what a browser uses to load a page.",[12,853,854,857],{},[53,855,856],{},"Timeout"," — how long the monitor waits for a response before considering the site down. The default (usually 5-30 seconds) is fine.",[12,859,860,861,865],{},"In ",[16,862,864],{"href":863},"\u002Fdocs\u002Fsetting-up-monitor","Monitoristic",", you enter the URL, pick the interval, and the rest is pre-filled with sensible defaults. You can start with just the URL.",[38,867,869],{"id":868},"step-3-set-up-alerts-the-most-important-step","Step 3: Set Up Alerts (The Most Important Step)",[12,871,872],{},"A monitor that detects downtime but doesn't tell you is useless. Setting up alerts is the step people skip — and then wonder why they still find out about outages from customers.",[12,874,875],{},"You have two main options:",[12,877,878,880,881,616],{},[53,879,19],{}," — the fastest way to get personal alerts on your phone. You connect a Telegram bot, and downtime alerts arrive as messages instantly. Free, reliable, and works anywhere you have the app. See our ",[16,882,883],{"href":18},"Telegram setup guide",[12,885,886,889,890,616],{},[53,887,888],{},"Webhooks"," — more flexible. A webhook sends structured data to any URL you specify, so you can route alerts to Slack, Discord, your own backend, or an automation tool. Better for teams. See our ",[16,891,892],{"href":23},"webhook guide",[12,894,895],{},"For your first setup, Telegram is the easiest. You'll get a message the moment your site goes down and another when it recovers.",[12,897,898,901],{},[53,899,900],{},"Don't skip this step."," A monitor without alerts is just a dashboard you have to remember to check — which defeats the entire purpose.",[38,903,905],{"id":904},"step-4-verify-its-working","Step 4: Verify It's Working",[12,907,908],{},"Once your monitor is set up, confirm everything works:",[46,910,911,917,923],{},[49,912,913,916],{},[53,914,915],{},"Check the dashboard"," — your monitor should show as \"up\" with a recent check timestamp",[49,918,919,922],{},[53,920,921],{},"Test your alert channel"," — most tools have a \"send test notification\" button; use it to confirm alerts reach your phone",[49,924,925,928],{},[53,926,927],{},"Wait for a few check cycles"," — after 10-15 minutes, you should see a history of successful checks",[12,930,931],{},"If your alert test doesn't arrive, fix that now. It's much better to discover a broken alert during setup than during an actual outage.",[38,933,935],{"id":934},"step-5-add-your-other-critical-endpoints","Step 5: Add Your Other Critical Endpoints",[12,937,938],{},"Now that your first monitor works, add the other pages that matter. Each one gets its own monitor so you know exactly what's affected when something breaks.",[12,940,941],{},"Common additions:",[778,943,944,950,961,972],{},[49,945,946,949],{},[53,947,948],{},"Login page"," — if users log in, a broken login blocks everyone",[49,951,952,955,956,960],{},[53,953,954],{},"Checkout \u002F payment page"," — for ",[16,957,959],{"href":958},"\u002Ffor\u002Fe-commerce","e-commerce",", this is the most revenue-critical URL",[49,962,963,966,967,971],{},[53,964,965],{},"API endpoints"," — if you have an ",[16,968,970],{"href":969},"\u002Fblog\u002Fhttp-vs-api-monitoring","API",", monitor it separately from your website",[49,973,974,977,978,20,982],{},[53,975,976],{},"Key third-party dependencies"," — services you rely on, like ",[16,979,981],{"href":980},"\u002Fmonitor\u002Fstripe","Stripe",[16,983,985],{"href":984},"\u002Fmonitor\u002Fsupabase","your database provider",[12,987,988,989,992],{},"For revenue-critical endpoints like checkout, consider a ",[16,990,991],{"href":829},"faster check interval"," (1-2 minutes) so you catch problems sooner.",[38,994,996],{"id":995},"step-6-set-up-a-status-page-optional-but-recommended","Step 6: Set Up a Status Page (Optional but Recommended)",[12,998,999,1000,1004],{},"A ",[16,1001,1003],{"href":1002},"\u002Fblog\u002Fwhat-is-a-status-page","status page"," is a public page where your users can check if your service is up. Instead of emailing you \"is the site down?\", they check the page.",[12,1006,1007],{},"This does two things:",[778,1009,1010,1013],{},[49,1011,1012],{},"Reduces support load during outages",[49,1014,1015],{},"Builds trust by being transparent about your uptime",[12,1017,1018],{},"Most monitoring tools, including Monitoristic, let you create a status page from your existing monitors in a couple of clicks.",[38,1020,1022],{"id":1021},"step-7-configure-maintenance-windows","Step 7: Configure Maintenance Windows",[12,1024,1025,1026,1030],{},"When you do planned work — deploying updates, migrating servers, upgrading plugins — your site might go down intentionally. Without a ",[16,1027,1029],{"href":1028},"\u002Fblog\u002Fhow-to-use-maintenance-windows","maintenance window",", your monitor will fire false alerts and your status page will show an outage.",[12,1032,1033],{},"Setting a maintenance window tells your monitor \"expect downtime during this period, don't alert.\" It keeps your alerts meaningful and your uptime stats accurate.",[38,1035,1037],{"id":1036},"common-beginner-mistakes-to-avoid","Common Beginner Mistakes to Avoid",[12,1039,1040,1043],{},[53,1041,1042],{},"Monitoring only the homepage."," Your homepage can be up while your checkout or login is broken. Monitor each critical endpoint separately.",[12,1045,1046,1049],{},[53,1047,1048],{},"Skipping alerts."," The #1 mistake. A monitor with no alerts is just a dashboard. Set up Telegram or webhooks immediately.",[12,1051,1052,1055],{},[53,1053,1054],{},"Setting the interval too long."," A 30-minute check interval means a 25-minute outage could go undetected. For anything important, use 5 minutes or less.",[12,1057,1058,1061],{},[53,1059,1060],{},"Monitoring the wrong status code."," If your page returns a 301 redirect or a 403 for unauthenticated requests, expecting a 200 will cause false alerts. Match the expected code to what your endpoint actually returns.",[12,1063,1064,1067],{},[53,1065,1066],{},"Forgetting maintenance windows."," Deploying without a maintenance window floods you with false alerts and trains you to ignore notifications.",[38,1069,1071],{"id":1070},"youre-done","You're Done",[12,1073,1074],{},"That's the whole process. To recap:",[46,1076,1077,1080,1083,1088,1091,1094,1097],{},[49,1078,1079],{},"Pick your most important URL",[49,1081,1082],{},"Create a monitor with a 5-minute interval and expected status 200",[49,1084,1085],{},[53,1086,1087],{},"Connect an alert channel (Telegram or webhook)",[49,1089,1090],{},"Verify it works with a test alert",[49,1092,1093],{},"Add your other critical endpoints",[49,1095,1096],{},"Set up a status page",[49,1098,1099],{},"Use maintenance windows for planned downtime",[12,1101,1102],{},"The entire thing takes a few minutes, and from that point on, you'll know about every outage the moment it happens — instead of hours later from an angry customer.",[12,1104,1105],{},[16,1106,1108],{"href":693,"rel":1107},[695],"Set up your first monitor →",{"title":82,"searchDepth":97,"depth":97,"links":1110},[1111,1112,1113,1114,1115,1116,1117,1118,1119,1120],{"id":756,"depth":97,"text":757},{"id":769,"depth":97,"text":770},{"id":803,"depth":97,"text":804},{"id":868,"depth":97,"text":869},{"id":904,"depth":97,"text":905},{"id":934,"depth":97,"text":935},{"id":995,"depth":97,"text":996},{"id":1021,"depth":97,"text":1022},{"id":1036,"depth":97,"text":1037},{"id":1070,"depth":97,"text":1071},"Never set up monitoring before? This beginner's guide walks you through it end to end — what to monitor, how to configure checks, and how to get alerts that actually reach you.",[1123,1126,1129,1132],{"q":1124,"a":1125},"What do I need to start monitoring my website?","Just your website's URL and a place to receive alerts (like Telegram or a webhook endpoint). You don't need to install anything on your site, modify your code, or give the monitoring tool access to your server. External monitoring works entirely from the URL.",{"q":1127,"a":1128},"How long does it take to set up uptime monitoring?","About two minutes for a basic setup. You enter your URL, pick a check interval, set the expected status code (usually 200), and connect an alert channel. More advanced setups — multiple endpoints, custom headers, status pages — take a bit longer but are still quick.",{"q":1130,"a":1131},"What should my first monitor be?","Start with your most important page — usually your homepage or your main application URL. Once that's working and you understand the basics, add monitors for other critical endpoints like your login page, checkout, or API.",{"q":1133,"a":1134},"What check interval should a beginner use?","Start with 5-minute checks. They catch any meaningful outage and keep things simple. Once you understand your site's behavior, tighten the interval on critical pages — like checkout or your API — to 1 or 2 minutes.",{"src":1136,"alt":1137},"\u002Fblog\u002Fblog-how-to-set-up-uptime-monitoring.webp","Step-by-step setup of an uptime monitor from URL to alert",{},"\u002Fblog\u002Fhow-to-set-up-uptime-monitoring",{"title":745,"description":1121},"blog\u002Fhow-to-set-up-uptime-monitoring","uQ9J0TcXGPjwQTI1XiWZKqEAFiJ0edARHZkLUmb240E",{"id":1144,"title":1145,"author":7,"body":1146,"category":1510,"date":718,"description":1511,"extension":720,"faqs":1512,"image":1525,"meta":1528,"navigation":738,"path":1529,"readingTime":184,"seo":1530,"stem":1531,"__hash__":1532},"blog\u002Fblog\u002Fwhat-is-api-monitoring.md","What Is API Monitoring and Why It Matters",{"type":9,"value":1147,"toc":1496},[1148,1151,1157,1160,1164,1167,1170,1173,1177,1180,1200,1203,1207,1210,1284,1291,1297,1301,1306,1309,1313,1316,1346,1350,1356,1359,1363,1370,1374,1377,1390,1396,1402,1408,1412,1415,1420,1468,1474,1478,1481,1484,1490],[12,1149,1150],{},"Here's a scenario that trips up a lot of teams: your website monitor shows 100% uptime. Green across the board. But your users are complaining that the app doesn't work. They can load the page, but their data won't appear. Buttons don't respond. The dashboard is empty.",[12,1152,1153,1154,1156],{},"What happened? Your website is up, but your ",[53,1155,970],{}," is down.",[12,1158,1159],{},"This is exactly the gap that API monitoring fills. Let's break down what it is, how it's different from regular website monitoring, and why most modern applications need both.",[38,1161,1163],{"id":1162},"what-is-an-api","What Is an API?",[12,1165,1166],{},"If you're new to the term: an API (Application Programming Interface) is how different pieces of software talk to each other. When you load a web app, the page itself is one thing — but the actual data (your account info, your orders, your messages) is usually fetched separately from an API.",[12,1168,1169],{},"Think of a restaurant. The website is the dining room — it's what you see. The API is the kitchen — where the actual work happens. You can walk into a beautiful dining room, sit down, and still get no food if the kitchen is broken.",[12,1171,1172],{},"Modern websites work the same way. The page loads (the dining room), then JavaScript calls the API (the kitchen) to fetch your data. If the API fails, the page looks fine but nothing works.",[38,1174,1176],{"id":1175},"what-is-api-monitoring","What Is API Monitoring?",[12,1178,1179],{},"API monitoring is the practice of regularly checking that your API endpoints are:",[46,1181,1182,1188,1194],{},[49,1183,1184,1187],{},[53,1185,1186],{},"Available"," — the endpoint responds at all",[49,1189,1190,1193],{},[53,1191,1192],{},"Correct"," — it returns the expected status code (usually 200) and the right data",[49,1195,1196,1199],{},[53,1197,1198],{},"Fast"," — it responds within an acceptable time",[12,1201,1202],{},"A monitoring tool sends a request to your API endpoint at regular intervals — just like it would for a website — and verifies the response. If the endpoint returns an error, times out, or responds too slowly, you get an alert.",[38,1204,1206],{"id":1205},"how-api-monitoring-differs-from-website-monitoring","How API Monitoring Differs from Website Monitoring",[12,1208,1209],{},"The two are related but check different things. Here's the distinction:",[1211,1212,1213,1228],"table",{},[1214,1215,1216],"thead",{},[1217,1218,1219,1222,1225],"tr",{},[1220,1221],"th",{},[1220,1223,1224],{},"Website Monitoring",[1220,1226,1227],{},"API Monitoring",[1229,1230,1231,1245,1258,1271],"tbody",{},[1217,1232,1233,1239,1242],{},[1234,1235,1236],"td",{},[53,1237,1238],{},"What it checks",[1234,1240,1241],{},"Does the page load?",[1234,1243,1244],{},"Does the data endpoint respond correctly?",[1217,1246,1247,1252,1255],{},[1234,1248,1249],{},[53,1250,1251],{},"What it catches",[1234,1253,1254],{},"Server down, page errors, slow loading",[1234,1256,1257],{},"API errors, bad responses, auth failures, slow queries",[1217,1259,1260,1265,1268],{},[1234,1261,1262],{},[53,1263,1264],{},"Typical request",[1234,1266,1267],{},"GET the homepage HTML",[1234,1269,1270],{},"GET\u002FPOST a specific API endpoint",[1217,1272,1273,1278,1281],{},[1234,1274,1275],{},[53,1276,1277],{},"What it misses",[1234,1279,1280],{},"Backend\u002FAPI failures behind a working page",[1234,1282,1283],{},"Frontend\u002Fpage rendering issues",[12,1285,1286,1287,1290],{},"This is the same distinction we cover in detail in ",[16,1288,1289],{"href":969},"HTTP vs API monitoring",". The short version: they're complementary, not interchangeable.",[12,1292,1293,1296],{},[53,1294,1295],{},"The critical insight",": a static homepage served from a CDN can load perfectly even when your entire backend is on fire. Website monitoring alone gives you false confidence. If your homepage is the only thing you monitor, you can have a completely broken application showing green on your dashboard.",[38,1298,1300],{"id":1299},"why-api-monitoring-matters","Why API Monitoring Matters",[1302,1303,1305],"h3",{"id":1304},"_1-your-website-can-lie-to-you","1. Your Website Can Lie to You",[12,1307,1308],{},"As covered above, a loading page doesn't mean a working app. The most dangerous outages are the ones your monitoring doesn't catch — where everything looks fine but nothing works. API monitoring closes that blind spot.",[1302,1310,1312],{"id":1311},"_2-apis-fail-in-ways-pages-dont","2. APIs Fail in Ways Pages Don't",[12,1314,1315],{},"APIs have failure modes that simple page loads don't:",[778,1317,1318,1324,1334,1340],{},[49,1319,1320,1323],{},[53,1321,1322],{},"Authentication breaks"," — your auth service goes down, and every API call returns 401. The page loads, but no user can access their data.",[49,1325,1326,1329,1330,1333],{},[53,1327,1328],{},"Database connection exhaustion"," — your ",[16,1331,1332],{"href":984},"database"," hits its connection limit, and API calls start timing out while the static page keeps serving.",[49,1335,1336,1339],{},[53,1337,1338],{},"Rate limiting"," — a dependency you call starts rate-limiting you, and your API returns errors for a portion of requests.",[49,1341,1342,1345],{},[53,1343,1344],{},"Bad deploys"," — a code change breaks an endpoint's logic. It returns a 200 but with wrong or empty data.",[1302,1347,1349],{"id":1348},"_3-third-party-apis-are-single-points-of-failure","3. Third-Party APIs Are Single Points of Failure",[12,1351,1352,1353,1355],{},"Most apps depend on external APIs — ",[16,1354,981],{"href":980}," for payments, an email service, an auth provider, a data API. When any of these goes down, your app breaks even though your own code is perfect.",[12,1357,1358],{},"Monitoring the third-party endpoints you depend on means you find out about their outages immediately — instead of discovering them when your checkout starts failing and customers complain.",[1302,1360,1362],{"id":1361},"_4-performance-degradation-is-an-early-warning","4. Performance Degradation Is an Early Warning",[12,1364,1365,1366,1369],{},"API response times tell a story. An endpoint that normally responds in 100ms but slowly creeps to 800ms over a few weeks is warning you about something — a growing database, an inefficient query, a struggling dependency. ",[16,1367,1368],{"href":614},"Tracking response times"," lets you catch and fix these issues before they become full outages.",[38,1371,1373],{"id":1372},"what-to-monitor-on-your-api","What to Monitor on Your API",[12,1375,1376],{},"If you're setting up API monitoring, start with the endpoints that matter most:",[12,1378,1379,1382,1383,20,1386,1389],{},[53,1380,1381],{},"Health endpoint"," — many APIs expose a ",[84,1384,1385],{},"\u002Fhealth",[84,1387,1388],{},"\u002Fstatus"," endpoint that checks internal dependencies (database, cache, external services) and returns 200 only when everything is working. This is the single most valuable thing to monitor because it tests the whole stack in one call.",[12,1391,1392,1395],{},[53,1393,1394],{},"Authentication endpoint"," — if auth breaks, your whole app is effectively down. Monitor your login or token endpoint.",[12,1397,1398,1401],{},[53,1399,1400],{},"Core data endpoints"," — the API calls your app makes most often. If these fail, your main features break.",[12,1403,1404,1407],{},[53,1405,1406],{},"Critical third-party APIs"," — payment processors, email services, and any external API your app can't function without.",[38,1409,1411],{"id":1410},"how-to-set-up-api-monitoring","How to Set Up API Monitoring",[12,1413,1414],{},"The good news: API monitoring uses the same mechanism as website monitoring. You point a monitor at the API URL instead of a page URL.",[12,1416,1417,1418,110],{},"For a basic setup in ",[16,1419,864],{"href":863},[46,1421,1422,1432,1438,1444,1450,1459],{},[49,1423,1424,1427,1428,1431],{},[53,1425,1426],{},"Create a monitor"," pointing to your API endpoint (e.g., ",[84,1429,1430],{},"https:\u002F\u002Fapi.yourapp.com\u002Fhealth",")",[49,1433,1434,1437],{},[53,1435,1436],{},"Set the HTTP method"," — GET for read endpoints, POST if the endpoint requires it",[49,1439,1440,1443],{},[53,1441,1442],{},"Set the expected status code"," — usually 200, but match what your endpoint actually returns",[49,1445,1446,1449],{},[53,1447,1448],{},"Add custom headers if needed"," — some endpoints require an API key or auth token in the headers",[49,1451,1452,1458],{},[53,1453,1454,1455],{},"Set a tight ",[16,1456,1457],{"href":829},"check interval"," — APIs are usually more critical than marketing pages, so 1-2 minute checks make sense",[49,1460,1461,1467],{},[53,1462,1463,1464],{},"Connect ",[16,1465,1466],{"href":18},"alerts"," so you know the moment an endpoint fails",[12,1469,1470,1471,1473],{},"For best results, monitor a ",[84,1472,1385],{}," endpoint that internally verifies your database and key dependencies. That way, a single monitored endpoint reflects the health of your entire backend.",[38,1475,1477],{"id":1476},"the-bottom-line","The Bottom Line",[12,1479,1480],{},"Website monitoring tells you if your site loads. API monitoring tells you if it actually works. For any modern application that fetches data — which is almost all of them — you need both.",[12,1482,1483],{},"The page is the dining room. The API is the kitchen. Monitor both, or you'll keep seating customers in a beautiful room with no food coming out.",[12,1485,1486],{},[16,1487,1489],{"href":693,"rel":1488},[695],"Start monitoring your API →",[12,1491,1492,1493],{},"For a deeper look at the technical difference between the two, read ",[16,1494,1495],{"href":969},"HTTP vs API Monitoring: What's the Difference?",{"title":82,"searchDepth":97,"depth":97,"links":1497},[1498,1499,1500,1501,1507,1508,1509],{"id":1162,"depth":97,"text":1163},{"id":1175,"depth":97,"text":1176},{"id":1205,"depth":97,"text":1206},{"id":1299,"depth":97,"text":1300,"children":1502},[1503,1504,1505,1506],{"id":1304,"depth":125,"text":1305},{"id":1311,"depth":125,"text":1312},{"id":1348,"depth":125,"text":1349},{"id":1361,"depth":125,"text":1362},{"id":1372,"depth":97,"text":1373},{"id":1410,"depth":97,"text":1411},{"id":1476,"depth":97,"text":1477},"Education","Your website can look perfectly fine while your API is failing behind the scenes. Here's what API monitoring is, how it differs from website monitoring, and why your app needs it.",[1513,1516,1519,1522],{"q":1514,"a":1515},"What is API monitoring?","API monitoring is the practice of regularly checking that your API endpoints are available, responding correctly, and performing well. It sends requests to your API and verifies the response — the status code, the response time, and optionally the content of the response — then alerts you when something is wrong.",{"q":1517,"a":1518},"How is API monitoring different from website monitoring?","Website monitoring checks if a page loads in a browser. API monitoring checks if your data endpoints respond correctly to programmatic requests. A website can load perfectly while the API behind it returns errors — your homepage shows, but data doesn't load. Monitoring both catches problems that either one alone would miss.",{"q":1520,"a":1521},"Do I need API monitoring if I already monitor my website?","If your website depends on an API — and most modern sites do — yes. Your homepage might be a static page served from a CDN that loads fine even when your API is down. Without API monitoring, you'd see green on your website monitor while your users see broken functionality.",{"q":1523,"a":1524},"What should API monitoring check?","At minimum, that the endpoint returns the expected status code (usually 200) within an acceptable time. More advanced monitoring also verifies the response contains expected data, checks authentication flows, and tracks response time trends to catch performance degradation before it becomes an outage.",{"src":1526,"alt":1527},"\u002Fblog\u002Fblog-what-is-api-monitoring.webp","API monitoring checking endpoints behind a website's interface",{},"\u002Fblog\u002Fwhat-is-api-monitoring",{"title":1145,"description":1511},"blog\u002Fwhat-is-api-monitoring","UT3uGP2ealN4_Adv9PwGhhntUYoqyfeBevppEybwb90",1780490855095]