Skip to content
Notis

Refresh prospect context as sales notes evolve

Update a sales page and have Notis retrieve company information that helps you pick up the next conversation.

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 Company Information

This action retrieves detailed company information for a given brand identifier. while the brandfetch get brand info tool provides general brand information, this tool specifically focuses on extracting and returning the company-related firmographic data from the response.

Why this helps

After a sales conversation, founders can lose time rebuilding company context before following up.

  • Revisit company context after important sales updates.
  • Make it easier to resume follow-up after an interruption.
  • Avoid repeating basic company research.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Brandfetch to Notis once in the portal.
  • 2Ask Notis to retrieve company information for the prospect named in updated sales page content.
  • 3Select the Notion Page Content Updated trigger for the sales page or data source.
  • 4Choose a report channel and test by updating one real sales page.

Questions about this workflow

Can this be limited to sales notes?

Yes. Scope the content update trigger to a sales page or data source.

Does this send the follow-up?

No. It retrieves company information to support your follow-up preparation.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Brandfetch. A trigger fires from one place; an action lands in another.

Notion triggers

Brandfetch actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Brand Information

This tool retrieves comprehensive brand information including logos, colors, fonts, and company details for any brand using their domain name, brand id, isin, or stock ticker symbol. it provides access to a brand's complete visual identity and company information.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Company Information

This action retrieves detailed company information for a given brand identifier. while the brandfetch get brand info tool provides general brand information, this tool specifically focuses on extracting and returning the company-related firmographic data from the response.

ActionInstant

All Page Events

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

TriggerPolling

Get Brand Logo

This tool fetches the latest logo for any brand using brandfetch's brand api. it provides access to high-quality, up-to-date logos with customizable dimensions. the tool supports different logo types (icon, logo, symbol) and themes (light, dark).

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 Transaction Info

This tool converts payment transaction labels into detailed merchant brand information. it takes a transaction label (like what you see on your credit card statement) and returns comprehensive brand data (including logos, colors, fonts, and company information). it is useful for identifying merchants and enriching transaction data with detailed brand information.

ActionInstant

New Comment

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

TriggerPolling

Identify Merchant from Transaction

This tool identifies merchant brands from raw transaction data in a single call. it processes unstructured payment text (e.g., credit card transaction descriptions), maps it to a domain, and returns comprehensive brand details including name, logo, domain, and industry information.

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

Search Brands

This tool allows searching for brands by name and returns matching brand information. it enables searching and matching brand names to their corresponding urls and icons, providing rich autocomplete experiences.

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 Brandfetch, 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 Brandfetch.