Connect new Notion views with Folk group context
A new view often signals a new way of organizing work. Bring Folk groups into the conversation while planning it.
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
List Groups
Tool to list workspace groups. use when you need to retrieve a paginated list of all workspace groups after authentication.
Why this helps
A new workflow view can be built without knowing which Folk group holds the related relationships.
- Make Folk groups easy to review during workflow planning.
- Reduce the effort of rediscovering CRM organization.
- Keep new Notion workflows linked to relationship structure.
Setup
Build it in a few focused steps.
- 1Connect Notion and Folk to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Ask Notis to retrieve Folk groups when a new Notion view is created and summarize which groups may suit the view's purpose.
- 4Select the Notion View Created trigger and choose a channel for run reports.
- 5Test with one real view creation and assess the summary.
Questions about this workflow
Does this create a Folk group?
No. It retrieves the existing group list for review.
Can Notis use the view type?
Yes. The trigger includes the view type and its parent context for the instruction to consider.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Folk. A trigger fires from one place; an action lands in another.
Notion triggers
Folk actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Company
Tool to create a new company in the workspace. use after gathering all required company details and ensuring the name is unique.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Company
Tool to delete a company from the workspace (irreversible). use after confirming this company should be removed.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Delete Person
Tool to delete an existing person in the workspace (irreversible). use after confirming this person should be permanently removed.
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.
List Companies
Tool to list companies in the workspace. use when you need a paginated overview of companies, optionally filtered.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Company
Tool to retrieve an existing company by its id. use after authentication has been verified.
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 Current Workspace User
Tool to get details of the current authenticated workspace user. use after authentication to retrieve the user's profile information.
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 Person
Tool to retrieve an existing person by their id. use when you need full profile details of a person by their unique identifier.
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 Group Custom Fields
Tool to list custom fields for a specific group and entity type. use after selecting a group and entity type to inspect available custom fields.
Connect any two apps with Notis in the middle.
Notion and Folk, 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 Folk.