Receive a daily Google Calendar agenda automatically
Mornings burn time as you piece together where you are supposed to be. Notis runs on a schedule, lists your Google Calendar events for the day, and hands you a clean agenda in the channel you already read, so the plan arrives before the scramble does.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
List Events
Returns events on the specified calendar.
Why this helps
The day starts with an anxious scroll through the calendar app, and half-open tabs make it hard to lock in a plan.
- One clear list of the day instead of an app scroll
- The plan arrives in a channel you already check
- No forgetting an early meeting buried in the calendar
- A calmer start with the whole day laid out in advance
Setup
Build it in a few focused steps.
- 1Connect Google Calendar to Notis from the portal.
- 2Open Automations in the portal and click New Automation, or ask Notis to build it in chat.
- 3Write the outcome: every morning, list my Google Calendar events for today and send me the agenda.
- 4Pick a recurring schedule as the trigger and choose the channel that should receive the agenda.
- 5Run a test to confirm the agenda arrives and reads the way you want.
Questions about this workflow
Where does the agenda get delivered?
Wherever you point the automation's channel, such as Telegram, WhatsApp, or email. You choose it when you set up the trigger.
Can I change the time it runs?
Yes. The recurring schedule is yours to set, so the agenda can land at whatever hour suits your morning.
Can it cover more than one calendar?
Yes. Name the calendars you want included in the plain-language prompt and Notis will pull from all of them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Calendar. A trigger fires from one place; an action lands in another.
Notion triggers
Google Calendar actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Update Calendar
Updates metadata for a calendar.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
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.
New Page
Triggers when a new page is added to a Notion database.
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.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Not just Notion and Google Calendar. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google Calendar.