All templates
For backend engineering teams, API teams & platform engineers

Get alerted when Hasura API errors spike

Every hour, WebRun opens Hasura Cloud, checks each project's GraphQL error rate and p95 latency against the threshold you set, posts a Teams alert naming the project and its top failing operations, and schedules a review on Google Calendar for a breach.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every hour WebRun
1 Hasura check API error rate and latency
2 Microsoft Teams alert on a threshold breach
3 Google Calendar schedule a review
Run a sample
In short

How do I get alerted when Hasura GraphQL API errors spike?

WebRun checks Hasura Cloud every hour, comparing each project's GraphQL error rate and p95 latency against the threshold you set. A breach posts a Microsoft Teams alert naming the project and its top failing operations, and schedules a review on Google Calendar, so an API regression gets a fix booked before more requests fail.

  • API regressions get caught within the hour, not after a customer report
  • Every alert names the specific operations driving the errors
  • Threshold breaches get a scheduled review, not just a notification

Built for backend engineering teams · API teams · platform engineers · site reliability engineers

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens cloud.hasura.io in a real browser with your saved login - no setup, no API keys.

  2. 1
    Hasura - check API error rate and latency
    hasura.io
    WebRun in Hasura: check API error rate and latency
    WebRun opens Hasura to check API error rate and latency.
    • Open Hasura Cloud and check the GraphQL error rate and p95 latency for each project
    • Compare it to your threshold
    • Note which operations are driving the errors

    Done when Every project has been checked against its error rate threshold.

  3. 2
    Microsoft Teams - alert on a threshold breach
    microsoft.com How to Automate Microsoft Teams
    WebRun in Microsoft Teams: alert on a threshold breach
    WebRun posts to Microsoft Teams to alert on a threshold breach.
    • Post an alert to the API team channel naming the project and the error rate
    • Include the top failing operations

    Done when The team has a Teams alert for every threshold breach.

  4. 3
    Google Calendar - schedule a review
    calendar.google.com How to Automate Google Calendar
    WebRun in Google Calendar: schedule a review
    WebRun opens Google Calendar to schedule a review.
    • Schedule a review for any project that's crossed its threshold
    • Invite the API's usual owner

    Done when A review is scheduled for every project over threshold.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
cloud.hasura.io
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
API error alert · Microsoft Teams
OutputWhat each run produces - An API error rate alert with the top failing operations, and a scheduled review.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it roll back a schema change or fix the resolver on its own?

No. WebRun only reports the error rate and schedules a review. Rolling back a change or fixing a resolver is left to a human.

How does it decide the error rate is a problem?

It compares each project's GraphQL error rate and p95 latency against the threshold you set, so the alert reflects your own reliability bar.

What operations does it call out?

It reads the operations contributing the most to the error count, so the review starts with the specific query or mutation causing trouble, not a vague error rate.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.