Keep time-zone details in view when plans change
When your event timing changes in Notion, have Notis retrieve the ClickMeeting time-zone options.
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
Get Time Zone List
Tool to retrieve a list of available time zones. use when you need to select a time zone before scheduling events.
Why this helps
A changed event time can create uncertainty about timezone settings and add another detail to verify.
- Make timezone review part of the rescheduling handoff.
- Reduce uncertainty when events span regions.
- Find the relevant ClickMeeting time-zone options quickly.
Setup
Build it in a few focused steps.
- 1Connect Notion and ClickMeeting to Notis once.
- 2Create an automation in the portal or tell Notis the outcome in plain language.
- 3Ask Notis to retrieve the ClickMeeting time-zone list when an event page is updated with a timing change.
- 4Choose the Notion Page Content Updated trigger scoped to the event page and a run-report channel.
- 5Test with one event time update and review the returned options.
Questions about this workflow
Does this change the scheduled time automatically?
No. It retrieves available time zones so the scheduling details can be reviewed.
Can it look up time zones for a country?
This action retrieves the general list. A country-specific lookup is a separate ClickMeeting action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Clickmeeting. A trigger fires from one place; an action lands in another.
Notion triggers
Clickmeeting actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Conference
Tool to create a new conference. use when you need to schedule or start a meeting/webinar after authentication.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Contact
Tool to create a new contact in your clickmeeting account. use when you need to add or pre-register an attendee before scheduling an event.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Conference
Tool to delete a specific conference. use after confirming the conference is no longer needed.
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.
Delete Recording
Tool to delete a specific recording for a conference room. use when you need to remove an unwanted or outdated recording after confirming the conference and recording ids. deletion is irreversible.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Delete Recordings
Tool to delete all recordings for a conference room. use when you need to clear all saved recordings for a specific conference before archiving or reusing it.
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.
Generate Autologin URL
Tool to generate an autologin url for a conference participant. use when you need to provide direct access to a conference room without separate login.
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.
Generate Session PDF Report
Tool to generate a pdf report for a specific session. use when you need to download session analytics as a pdf file.
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.
Get Chat Details
Tool to retrieve details of a specific chat session. use when you have the chat id and need its metadata and messages.
Connect any two apps with Notis in the middle.
Notion and Clickmeeting, 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 Clickmeeting.