Carry a new Notion review lens into Gigasheet
When you create a new Notion view for a particular slice of work, have Notis retrieve the related Gigasheet filter template so the same review can continue there.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Apply Filter Template On Sheet
Tool to fetch a saved filter template's model for a given sheet. Use when you need the exact filter structure for a specific sheet and template.
Why this helps
A new way of organizing work in Notion often leaves the related Gigasheet review setup hard to find.
- Make the relevant saved filter easier to retrieve when a review view is added.
- Reduce setup searching across tools.
- Keep related data-review habits connected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Gigasheet to Notis once in the portal.
- 2Create an automation in the portal or tell Notis what to do in plain language.
- 3Ask Notis in one instruction to retrieve the corresponding Gigasheet filter template when a named kind of Notion view is created.
- 4Select View Created and choose a channel for run reports.
- 5Create one real view and confirm the intended template is retrieved.
Questions about this workflow
Can the trigger distinguish view types?
The event includes a view type such as table, board, or calendar. Explain which view types should prompt the lookup.
Does this create a new filter?
The action retrieves a saved template model. To create or change one, use a separate Create/Update Filter Template action.
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.