Keep Notion account notes connected to Folk
An account note changes. Bring up the matching Folk company record while the new context is top of mind.
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 Person
Tool to retrieve an existing person by their id. use when you need full profile details of a person by their unique identifier.
Why this helps
New account context can remain buried in notes while the CRM profile stays out of sight.
- Make the CRM record easier to review after research changes.
- Connect account notes to a persistent company profile.
- Reduce follow-up delays from hidden updates.
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 tell Notis your desired result.
- 3Ask Notis to use an updated Notion account page to identify and retrieve the matching Folk company for review.
- 4Choose Notion Page Content Updated scoped to the account page or data source and select a report channel.
- 5Test with one real account-note edit.
Questions about this workflow
Does a content edit change the Folk company?
No. This workflow retrieves the existing company record for review.
Can it watch one account page?
Yes. The trigger can be scoped to a specific Notion page.
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.