Make room for a weekly threat intelligence check
Set a recurring moment to review current threat intelligence and put any needed investigation time on your calendar.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Threat intelligence can accumulate without a reliable review rhythm, making it harder to spot items that need action.
- Create a regular checkpoint for threat intelligence.
- Reserve time when the review identifies actionable items.
- Keep recurring security review work visible alongside other commitments.
Setup
Build it in a few focused steps.
- 1Connect Abuselpdb and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis: Review current Abuselpdb threat intelligence and create a calendar event for a review when findings need investigation; summarize the findings in the event.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real example and confirm the event time and summary.
Questions about this workflow
How does this workflow get started?
A recurring Notis cron schedule starts it. During each run, Notis can ask Abuselpdb for current threat intelligence.
Will it create an event every time it runs?
Your instruction can ask Notis to create an event only when the returned findings need investigation. Notis can analyze returned data, but it needs the relevant findings from Abuselpdb.
What if no findings need attention?
Instruct Notis to report that there is nothing to schedule, rather than create an empty review event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abuselpdb to Google Calendar. A trigger fires from one place; an action lands in another.
Abuselpdb 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.
Abuselpdb 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.