Give Cloudflare incidents a dedicated follow-up block
When an issue needs attention, put the next work session directly on your calendar and keep it from disappearing in a busy inbox.
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
Security and traffic issues demand attention, but follow-up work can get lost amid interruptions and open tabs.
- Reserve focused time for incident work
- Make the next step visible
- Reduce the risk of forgetting post-incident follow-up
Setup
Build it in a few focused steps.
- 1Connect Cloudflare api key and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for incident follow-up.
- 3Describe in one instruction what calendar event to create when the webhook arrives.
- 4Choose a Notis webhook trigger and select where run reports should go.
- 5Send one real example webhook and confirm the event details and timing in Google Calendar.
Questions about this workflow
Does Cloudflare automatically send the webhook in this workflow?
The trigger is a Notis webhook. Configure the system you use to send a request to that webhook when an incident needs calendar time.
Can it decide the right time for an incident block?
Give Notis the timing details in the webhook request or your instruction. The Create Event action needs valid RFC3339 UTC start and end times, with the end after the start.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudflare api key to Google Calendar. A trigger fires from one place; an action lands in another.
Cloudflare api key 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.
Cloudflare api key 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.