Make upcoming event descriptions easier to scan
A scheduled pass can make rough event notes clearer, using the existing description as source material and updating only events that need it.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Patch Event
Updates specified fields of an existing event in a google calendar using patch semantics (array fields like `attendees` are fully replaced if provided); ensure the `calendar id` and `event id` are valid and the user has write access to the calendar.
Why this helps
Sparse or messy event notes make it harder to remember why a meeting is on the calendar.
- Improve clarity of existing event descriptions.
- Use the event's current notes as source material.
- Keep calendar context easier to scan before meetings.
Setup
Build it in a few focused steps.
- 1Connect Abstract and Google Calendar once in the Notis portal.
- 2Create an automation from Automations, New Automation, or tell Notis what you want from any channel.
- 3In one instruction, ask Notis to review upcoming events in the specified calendar, process each existing description with Abstract for clarity without adding unsupported details, and patch only descriptions that need improvement.
- 4Choose the recurring schedule trigger and select where run reports should go.
- 5Test with one real upcoming event that has a description you want to clarify.
Questions about this workflow
Will it invent meeting details?
The instruction should tell Notis to use only the event's existing description and avoid adding unsupported details.
Which calendar does it review?
Specify the calendar to review in the automation instruction.
Why use Patch Event?
Patch Event updates only the specified fields. This workflow updates the description while leaving other event fields alone.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abstract to Google Calendar. A trigger fires from one place; an action lands in another.
Abstract 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.
Abstract 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.