Carry meeting follow-up into contact prep
Turn a meeting follow-up note into a prepared contact research step while the conversation is still fresh.
Trigger
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.
Action
Create Contact Data List
Tool to create a list of contact data entries. Use when preparing the 'datas' payload for bulk enrichment; validates each contact's composition and returns a JSON-ready list.
Why this helps
Meeting follow-up can slip when action items and contact research live in different places.
- Connects meeting context to contact research.
- Cuts down on translating notes into a second tool.
- Makes it easier to follow through after a conversation.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fullenrich to Notis once in the portal.
- 2Create an automation or ask Notis to prepare Fullenrich contact data when a Notion meeting comment requests contact research.
- 3Give Notis one plain-language instruction explaining what requests count and how to identify the person discussed.
- 4Choose Comment Created, choose a report channel, and test with one meeting follow-up comment.
Questions about this workflow
Can it identify who the comment refers to?
Describe the relevant meeting page context in the prompt and ensure the person is identifiable.
What Notion access does this need?
Comment events require the Read comments capability on the Notion integration.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fullenrich. A trigger fires from one place; an action lands in another.
Notion triggers
Fullenrich actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Contact Data List
Tool to create a list of contact data entries. Use when preparing the 'datas' payload for bulk enrichment; validates each contact's composition and returns a JSON-ready list.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Bulk Enrichment Result
Tool to retrieve results of a bulk enrichment by enrichment ID. Use after confirming the job has been submitted to fetch status and enriched data.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get current credit balance
Tool to retrieve current workspace credit balance. Use after authenticating your API key.
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.
Start Bulk Enrichment
Tool to start a bulk enrichment job. Use when you have up to 100 contacts prepared and need batch enrichment. Use after confirming contact data.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Fullenrich, 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 Fullenrich.