Keep publishing plans current
Send the revised date and identifying details to a webhook. Notis can find the matching event and update the fields that changed.
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 changed publish date can leave a calendar event behind with an outdated time or title.
- Bring revised content details into the matching calendar event.
- Avoid manually locating and editing the event after a schedule change.
- Use an identifying title or event detail in the request to find the right item.
Setup
Build it in a few focused steps.
- 1Connect Cloudpress and Google Calendar once in the Notis portal.
- 2Create an automation in Automations, then choose a name and prompt.
- 3Tell Notis to find the matching calendar event and update it with the revised details in the request.
- 4Choose the webhook trigger and where run reports should go.
- 5Test with one real revised content date and its matching calendar event.
Questions about this workflow
What details should the webhook request include?
Include enough information to identify the existing event, along with the revised details. A title and new date are a useful starting point.
Does this trigger on a native Cloudpress event?
No. Cloudpress has no listed trigger events here. An HTTP request starts the Notis webhook automation.
What happens if there is no matching event?
The prompt should tell Notis how to handle a missing match, such as reporting it without changing another event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cloudpress to Google Calendar. A trigger fires from one place; an action lands in another.
Cloudpress 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.
Cloudpress 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.