Bring investment history into outreach discussions
A new comment on an investor page can prompt Fundable to retrieve investment history before your next outreach step.
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
Get Person Investments
Get deals a person participated in as an investor by identifier
Why this helps
Outreach questions often surface in comments, but research gets delayed when it requires switching tools and remembering context.
- Give an outreach discussion a concrete research follow-up.
- Bring deal participation context closer to investor notes.
- Reduce delays between questions and useful background.
Setup
Build it in a few focused steps.
- 1Connect Notion and Fundable to Notis once through the portal.
- 2Create an automation or ask Notis to retrieve the investor's Fundable deals when a comment is added to the specified outreach page.
- 3Select the Notion Comment Created trigger and scope it to the outreach page if appropriate; choose a channel for run reports.
- 4Test by adding a real comment requesting investment background.
Questions about this workflow
Can I scope this to one outreach page?
Yes. The Comment Created trigger supports an optional page scope.
What access is needed for comments?
The Notion connection needs the Read comments capability, with reauthorization if it was granted after connection.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Fundable. A trigger fires from one place; an action lands in another.
Notion triggers
Fundable actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Look Up Company
Search for a company by name, domain, LinkedIn, or Crunchbase
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search Funding Rounds
Search and filter funding rounds by company, investor, and round details
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Company Rounds
Get deals for a company by identifier
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 Person Investments
Get deals a person participated in as an investor by identifier
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Round Investors
Get investors for a specific funding round
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 Investor Profile
Get investor details and statistics by identifier
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 Fundable, 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 Fundable.