Keep event locations aligned with verified addresses
When a location is corrected and verified, have Notis update the matching calendar event with the new address.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
A corrected location can leave an old address in an event, sending you or a collaborator to the wrong place.
- Keep event locations current after an address correction.
- Reduce the chance of navigating to an outdated destination.
- Patch an existing event when its identifying details are available.
Setup
Build it in a few focused steps.
- 1Connect Addresszen and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, then New Automation.
- 3Tell Notis to find the intended existing event using identifying details supplied in the submission, then patch its location with the updated verified address.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real correction that includes the event's identifying details and the new verified address.
Questions about this workflow
How will Notis know which event to update?
Include identifying details for the intended event in the webhook request and state how Notis should use them to find it. Google Calendar needs a valid event and calendar, with write access.
Does this create a new event?
No. This workflow patches a specified existing event. If the event cannot be identified, the instruction should have Notis report that rather than guess.
Could other event fields change?
Patch Event uses patch semantics, so only fields provided are updated. Array fields such as attendees are replaced if included.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Addresszen to Google Calendar. A trigger fires from one place; an action lands in another.
Addresszen 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.
Addresszen 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.