Put each new abuse report on your calendar
An abuse report arrives. Notis gives the investigation a place in your day, with the report details ready for review.
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
Abuse reports can arrive while you are focused elsewhere, leaving investigation and follow-up without a clear time.
- Reserve time to investigate a reported IP.
- Keep report context near the calendar event.
- Reduce the chance that an incoming report goes unreviewed.
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: When an abuse report is sent to this webhook, create a calendar event to review it and include the report details.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real abuse report and confirm the event details and timing.
Questions about this workflow
What starts this automation?
An HTTP request to the webhook starts it. Include the abuse report details in the request so Notis can use them in the calendar event.
Does Abuselpdb send a trigger event to Notis?
No Abuselpdb trigger event is specified here. This workflow uses a Notis webhook, which you can call when a report should be reviewed.
Can it choose a review time automatically?
Tell Notis how to determine the event time in your instruction, or provide the desired time with the webhook request. Calendar event creation needs valid start and end times.
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.