Put incident response time on the calendar
Start a coordinated response with one webhook and a calendar event that keeps the incident details close at hand.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
Why this helps
When an incident fires, coordinating a response meeting by hand adds another task during an already noisy moment.
- Give responders a shared time to focus on the incident.
- Keep the incident details with the calendar event.
- Reduce the delay between an alert and coordinated follow-up.
Setup
Build it in a few focused steps.
- 1Connect Better Stack and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to create a response event using the incident details received by webhook.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test it with one real Better Stack incident example.
Questions about this workflow
Does Better Stack provide a trigger event for this automation?
No. Start the automation with a Notis webhook and have Better Stack or an intermediary send the request when the incident needs a response session.
What information should the request include?
Include the incident summary and any useful incident link or context. Notis can use only details included in the request or available from connected services.
Can Notis choose a meeting time automatically?
The request should supply a start and end time, or your instruction should use another available scheduling rule. Google Calendar requires valid RFC3339 UTC start and end times.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Better stack to Google Calendar. A trigger fires from one place; an action lands in another.
Better stack triggers
Google Calendar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Update Calendar
Updates metadata for a calendar.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
Delete event
Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Better stack and Google Calendar, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Google Calendar.