Look up potential partners mentioned in comments
Capture the first brand candidates while a partner suggestion is still in the conversation, so you do not need to remember to research it later.
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
Search Brand
Tool to search for brands based on a query string. use when you need to retrieve a list of matching brands with optional pagination and filters by country or industry.
Why this helps
Partner ideas often arrive in passing, then disappear beneath the next batch of decisions.
- Make a partner suggestion easier to revisit.
- See potential brand matches while the discussion is current.
- Reduce the memory load of tracking informal research requests.
Setup
Build it in a few focused steps.
- 1Connect Notion and Logo dev to Notis once in the portal, with Notion comment access enabled.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Give Notis one plain-language instruction to search Logo dev when a comment names a potential partner and report likely matches.
- 4Choose the Notion Comment Created trigger and a channel for run reports.
- 5Test with a real comment that names a partner company.
Questions about this workflow
Will it search comments unrelated to partners?
The trigger may see comments across the integration's accessible workspace. The instruction should limit searches to comments naming potential partners.
What access does the comment trigger require?
The Notion integration needs Read comments capability. Reauthorize if that capability was enabled after connecting.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Logo dev. A trigger fires from one place; an action lands in another.
Notion triggers
Logo dev actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Logo Image
Tool to retrieve the logo image for a domain. use when you need the raw image bytes (png or svg) of a specific domain's logo. use after validating the domain string.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Search Brand
Tool to search for brands based on a query string. use when you need to retrieve a list of matching brands with optional pagination and filters by country or industry.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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 Logo dev, 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 Logo dev.