Make new Notion views work for you
A view should reduce friction. A brief task helps you decide whether the new perspective earns a place in your routine.
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
Insert Task
Creates a new task in a given `tasklist id`, optionally as a subtask of an existing `task parent` or positioned after an existing `task previous` sibling, where both `task parent` and `task previous` must belong to the same `tasklist id` if specified.
Why this helps
Creating another view can feel productive but add another choice when you return to the workspace.
- Encourages a quick usability check
- Helps avoid accumulating views without a clear purpose
- Keeps workspace choices more intentional
Setup
Build it in a few focused steps.
- 1Connect Notion and Google Tasks to Notis once in the portal.
- 2Create the automation in the portal or tell Notis conversationally what outcome you want.
- 3Ask Notis in one prompt to create a task to review the purpose and usefulness of each new Notion view.
- 4Select the Notion View Created trigger and choose a channel for run reports.
- 5Test with a real view creation and see whether the task has enough context.
Questions about this workflow
Can it include the view type?
Ask Notis to include the available view type or parent context in the task description.
Does this change the view?
No. It creates a task for you to decide whether the view belongs in your workflow.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google Tasks. A trigger fires from one place; an action lands in another.
Notion triggers
Google Tasks actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear tasks
Permanently clears all completed tasks from a specified google tasks list; this action is destructive and idempotent.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a task list
Creates a new task list with the specified title.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete task
Deletes a specified task from a given task list in google tasks.
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 task list
Permanently deletes an existing google task list, identified by `tasklist id`, along with all its tasks; this operation is irreversible.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Task
Use to retrieve a specific google task if its `task id` and parent `tasklist id` are known.
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 task list
Retrieves a specific task list from the user's google tasks if the `tasklist id` exists for the authenticated user.
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.
Insert Task
Creates a new task in a given `tasklist id`, optionally as a subtask of an existing `task parent` or positioned after an existing `task previous` sibling, where both `task parent` and `task previous` must belong to the same `tasklist id` if specified.
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.
List task lists
Fetches the authenticated user's task lists from google tasks; results may be paginated.
Connect any two apps with Notis in the middle.
Notion and Google Tasks, 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 Google Tasks.