Keep dataset column names clear for analysis
When changes to Notion properties are reflected in a Gigasheet dataset, have Notis make duplicate column names unique before they cause confusion in review.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
Rename Columns to Unique
Tool to rename all columns in a dataset to unique names. Use when duplicate column names could cause conflicts in downstream processing.
Why this helps
Duplicate column names make it harder to know which data a formula, filter, or update will affect.
- Avoid ambiguous headers in a dataset.
- Make later filtering and updates more predictable.
- Reduce small data-cleanup friction during busy work.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gigasheet to Notis once in the portal.
- 2Create the automation in the portal or describe it to Notis conversationally.
- 3Write one instruction naming the Gigasheet dataset whose duplicate columns should be made unique when relevant Notion properties change.
- 4Select Page Properties Updated and choose a reporting channel.
- 5Test with a safe example and inspect the resulting column names.
Questions about this workflow
Does a Notion property change automatically change Gigasheet columns?
Only if your workflow already reflects those properties in that dataset. This action makes existing duplicate Gigasheet names unique.
Can I limit the trigger?
Yes. Scope Page Properties Updated to a data source, page, or parent page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Gigasheet. A trigger fires from one place; an action lands in another.
Notion triggers
Gigasheet actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete sheet or folder by handle
Tool to delete a sheet or folder by handle. Use after obtaining the handle of a sheet or empty folder. Set recursive=True to delete all children of a folder.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Client State Current Version
Tool to fetch the current client-state version metadata for a sheet. Use after obtaining a sheet handle to determine the current version identifier for creating views.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Connector Connections
Tool to list connector connections. Use after setting a valid Gigasheet API token.
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.
Get Dataset by Handle
Tool to get dataset metadata. Use after you have obtained the dataset handle.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Dataset Columns
Tool to list all column metadata (IDs, names, types) for a dataset. Use after obtaining a dataset handle.
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.
Get Dataset Export Download URL
Tool to retrieve the download URL for an exported dataset. Use after initiating an export and obtaining its handle.
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.
Get Dataset Views
Tool to list all views associated with a specific dataset. Use after confirming the dataset handle and its status.
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 Docs Formulas Functions
Tool to retrieve all supported formula functions. Use after authenticating with a valid API token.
Connect any two apps with Notis in the middle.
Notion and Gigasheet, 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 Gigasheet.