Get image search results from an updated Notion brief
Add the subject to a Notion research brief and let Autom return image result links, titles, domains, and metadata.
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
Google Images
Tool to fetch images from google search results. use when you need urls, titles, domains, and metadata for images matching a query.
Why this helps
Visual research often gets postponed when it means opening another search and collecting reference links by hand.
- Fetches image search results for the updated research subject.
- Returns URLs, titles, domains, and available metadata.
- Creates a useful starting point for visual review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Autom to Notis once through the portal.
- 2Create an automation in the portal or ask Notis conversationally for the result.
- 3Give one plain-language instruction to search Google Images via Autom for the subject in an updated Notion brief and report the result links and details.
- 4Select the Notion Page Content Updated trigger and choose where run reports should go.
- 5Test by adding a specific subject to one real research brief.
Questions about this workflow
Does this copy images into Notion?
No. It returns image result URLs and available result details for review.
Can I use it for a creative brief?
Yes, when the brief names a concrete subject for visual exploration.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Autom. A trigger fires from one place; an action lands in another.
Notion triggers
Autom actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Google Countries
Tool to list google-supported countries. use when you need to filter or suggest countries based on a search string.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Google Images
Tool to fetch images from google search results. use when you need urls, titles, domains, and metadata for images matching a query.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Google Languages
Tool to retrieve google-supported languages. use when you need a list of language codes for localization.
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.
Google Locations
Tool to retrieve google-supported locations. use when searching for locations by name. returns locations ordered by reach (most populous first).
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 Autom, 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 Autom.