StatusCake

Zapier Set Ups – Keep a log of tests added to StatusCake

change log

There’s a lot that can be automated within StatusCake using the Zapier app. Today we’ll take you through how to keep an automatic log of any tests added to your StatusCake account, all the data will be stored on Google Sheets, and the data for each new test will occupy one row.

Zap2A

We do store similar data for you with our Audit log feature, but using this method allows you to keep your own hard copy which can be downloaded for offline access.

Before you start, you should decide which pieces of data will be useful. Zapier is able to grab the following information upon test creation:

  • Test Name
  • Test URL
  • Test Type
  • Test initial Status (UP/DOWN)
  • Test ID
  • Paused (0/1)
  • Check Rate
  • Contact Groups (Returned as CUID)
  • Test Tags

You will be prompted to assign these data fields to a column in your spreadsheet, assign the ones that you would like to store, and you will then be able to see the expected results within Zapier.

zapA3

Once you submit the Zap and enable it, a new row will be added to the spreadsheet each time that you add a new test within StatusCake.

Share this

More from StatusCake

What the Namecheap Outage Revealed About DNS Recovery

4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes

Monzo’s Stand-In Held Up on Wednesday. Some Customers Still Had a Bad Day.

3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and

What Broke GitHub on August 17 and How Retries Made the Incident Worse

3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests

Automate StatusCake Monitoring with viaSocket

3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect

Website Monitoring Checklist: What to Track Beyond Uptime

7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.