Skip to content
Notis

Refresh company lookups when Notion details change

Update a company record in Notion and let Fundable check for the best matching profile again.

Trigger

Page Properties Updated

Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.

Action

Look Up Company

Search for a company by name, domain, LinkedIn, or Crunchbase

Why this helps

A changed domain or corrected company name can make old search notes unreliable, and remembering to search again is easy to miss.

  • Recheck a company after key details are corrected.
  • Reduce the chance of carrying forward a mismatched profile.
  • Let updates in your working database prompt the next research action.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Fundable to Notis once through the portal.
  • 2Create an automation or tell Notis in plain language to look up the company in Fundable whenever its Notion record is updated.
  • 3Select the Notion Page Properties Updated trigger and choose a channel for run reports.
  • 4Test with one real company after updating a useful identifying detail.

Questions about this workflow

Does every property edit cause a lookup?

The selected trigger fires on page property updates. Describe the desired behavior in the automation prompt.

Can this identify the correct company?

Fundable searches using available identifying information; review the result if multiple companies could match.

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.

TriggerScheduled

Look Up Company

Search for a company by name, domain, LinkedIn, or Crunchbase

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Search Funding Rounds

Search and filter funding rounds by company, investor, and round details

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get Company Rounds

Get deals for a company by identifier

ActionInstant

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.

TriggerInstant

Get Person Investments

Get deals a person participated in as an investor by identifier

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Get Round Investors

Get investors for a specific funding round

ActionInstant

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.

TriggerInstant

Get Investor Profile

Get investor details and statistics by identifier

ActionInstant

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.

TriggerInstant

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.

TriggerInstant

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.