Log each Opsgenie alert in a Google Sheets incident tracker
Opsgenie alert events you choose are added as rows in a Google Sheets spreadsheet, giving your on-call team a running incident log to sort, filter and review after each outage.
Opsgenie
Google Sheets2 steps Setup ~5 min Used on 1.5k sites Free to import
What this workflow does
Opsgenie is built for waking the right person, not for keeping a tidy history you can hand to managers. When you write a post-mortem or a monthly report, pulling alerts back out takes time. This workflow writes alert events into a spreadsheet as they happen.
The Opsgenie trigger, Setup Webhooks, fires for the Opsgenie events you specify. FlowMattic receives the alert data for each event and passes it to Google Sheets, where Add New Row writes your mapped values into the next empty row of the spreadsheet you choose.
Each event gives one row. If you choose several events for the same alert, such as its creation and its closing, that alert appears more than once, which can be useful as a timeline. Pick only the creation event if you want one row per alert. Task History shows each run, so you can see what Opsgenie sent.
Material for post-mortems
After an outage, the sheet already lists every alert raised during the incident, ready to paste into the write-up or sort by time.
Monthly reliability reports
A team lead filters the incident tracker by month and service to count alerts, without exporting anything from Opsgenie.
Sharing incidents outside the on-call team
Support or account managers who don't use Opsgenie can view the Google Sheet to see what alerted and when.
How this workflow runs
What happens at each step once the workflow is on, and what you need before you import it.
Opsgenie Setup WebhooksFires for the Opsgenie events you specify, such as an alert being created. The alert data that comes with each event is passed to Google Sheets for mapping.
- Google Sheets Add New Row
Adds a new row to your incident tracker spreadsheet with the values you map from the Opsgenie alert. Connect your Google account and match each column to an alert field.
What you need
- FlowMatticCore
- Opsgenie AccountAccount
- Google Sheets AccountAccount
After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.
Make it yours
Changes worth making after you import it.
- Put a Filter after the trigger if only some alerts belong in the tracker, for example a priority value you see in a test run.
- Add a timestamp column and map a time value from the Opsgenie data, so the sheet sorts in the order alerts happened.
- Use a Router with one route per event type, each with its own Add New Row step, to keep created and closed events on separate tabs.
Questions about this workflow
Will each Opsgenie alert appear once in the Google Sheet?
Only if you select a single event per alert, such as creation. Every event you subscribe to adds its own row, so creating and closing the same alert gives two rows.
Does the workflow update the row when an Opsgenie alert is closed?
No. It only adds rows. A closing event, if you select it, appears as a new row rather than changing the existing one.
Are alerts from before setup copied into the sheet?
No. Only events Opsgenie sends after the workflow is active reach the spreadsheet.
Can I post the alert to chat as well as logging it?
Yes. Add a message step, such as Slack Send Channel Message, after the Google Sheets step so each alert is logged and posted in the same run.
More Spreadsheets & Data workflows
Other ready-to-import templates from the same category.
Import this workflow into your WordPress site
Download the JSON, import it from the Workflows screen and connect your accounts. Every run stays on your server, with no per-task fees.
30-day money-back guarantee Unlimited workflows and runs Self-hosted