Look up Make timezones from a Notion scheduling note
Keep timezone research close to your scheduling notes: update a Notion page and let Notis retrieve Make's timezone options for review.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
Action
List Enums Timezones
Tool to retrieve a list of timezone codes and names. use when populating timezone selectors after authentication.
Why this helps
Choosing a schedule timezone often means leaving planning notes to search a separate list, adding a small but disruptive context switch.
- Request timezone options in the same place you document scheduling decisions.
- See the available Make timezone codes and names in a run report.
- Avoid guessing a timezone when preparing a Make automation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Make to Notis once through the portal.
- 2Create an automation in the portal, or ask Notis conversationally to retrieve Make's timezone list when a scheduling note is updated and summarize the options in its run report.
- 3Choose the Notion Page Content Updated trigger for the page or data source where scheduling notes are kept.
- 4Choose a channel for run reports, then test by updating one real scheduling note.
Questions about this workflow
What does the timezone lookup return?
It retrieves the timezone codes and names available through Make's List Enums Timezones action.
Will this schedule or change a Make scenario?
No. This action lists timezone options for review; it does not configure a schedule.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Make. A trigger fires from one place; an action lands in another.
Notion triggers
Make actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Operations
Tool to retrieve all operations. use when you need to discover available operations after authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Enums Languages
Tool to retrieve a list of language codes and names. use when you need to populate language selectors after authentication.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
List Enums Timezones
Tool to retrieve a list of timezone codes and names. use when populating timezone selectors after authentication.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Make, 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 Make.