Handle logo requests posted in Notion
A request tucked into a page discussion does not need to become a separate reminder. Validate the domain and retrieve the logo image when the request is clear.
Trigger
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Action
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.
Why this helps
Small requests in comments are easy to lose among other work, even when the next step is straightforward.
- Turn an explicit logo request into a practical next step.
- Check the domain before retrieving an image.
- Reduce the mental effort of revisiting comment threads.
Setup
Build it in a few focused steps.
- 1Connect Notion and Logo dev to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally.
- 3Use one plain-language instruction asking Notis to retrieve a logo only when a comment clearly requests one and the company domain can be validated.
- 4Choose the Notion New Comment trigger for the relevant page or block and a channel for run reports.
- 5Test with one real comment requesting a known company's logo.
Questions about this workflow
Can I limit the workflow to a particular discussion?
Choose the Notion New Comment trigger for a specified page or block when setting it up.
What does it do with an unclear request?
The instruction can ask Notis to report that it needs a company domain or more detail before retrieving an image.
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.