Keep a shift event current when details change
Send corrected shift details through a webhook and update the matching calendar event without replacing unrelated event information.
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
When a shift changes, a calendar copy can keep showing old details unless someone remembers to correct it.
- Apply corrected details to an existing calendar event.
- Use patch semantics to update only the specified fields.
- Keep shift changes visible in the calendar.
Setup
Build it in a few focused steps.
- 1Connect 7shifts and Google Calendar once in the Notis portal.
- 2Create an automation in the portal, or tell Notis to create it from your preferred channel.
- 3Describe how to identify the existing event and apply the corrected shift details included in a request.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real update and confirm the intended event and changed fields.
Questions about this workflow
Will this detect changes in 7shifts by itself?
No. 7shifts trigger events are not listed. The webhook caller must send the corrected details and enough information to identify the calendar event.
What does Patch Event do?
It updates specified fields on an existing event using patch semantics. If you provide array fields such as attendees, the array is fully replaced.
What information is needed to update an event?
The workflow needs a valid calendar ID and event ID, plus the fields to change. The authenticated user needs write access to that calendar.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link 7shifts to Google Calendar. A trigger fires from one place; an action lands in another.
7shifts 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.
7shifts 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.