Revisit image descriptions after content revisions
Content revisions can change emphasis and context. Retrieve image records and current alt text to see what deserves a second look.
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 Images
Tool to retrieve a paginated list of images in your library, including their alt text and metadata. use when you need to browse or filter images programmatically after authentication.
Why this helps
Revised copy can outgrow old descriptions, but editors rarely have a spare moment to remember every affected asset.
- Review image descriptions when a page's body changes.
- Keep descriptions connected to the latest content context.
- Make follow-up easier to notice after editing.
Setup
Build it in a few focused steps.
- 1Connect Notion and Alttext.ai to Notis once in the portal.
- 2Create an automation in the portal or explain the workflow to Notis conversationally.
- 3Ask Notis to retrieve Alttext.ai image records after a Notion content edit and report descriptions that should be compared with the revised page context.
- 4Select Page Content Updated and optionally scope it to the page or data source; choose a report channel.
- 5Test with an edited page and review the returned records.
Questions about this workflow
How quickly does the content event arrive?
Notion commonly aggregates content edits over a short window, around 60 seconds.
Can this confirm that an image description is still accurate?
It can retrieve existing descriptions for comparison; a person needs to judge whether they fit the revised context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Alttext ai. A trigger fires from one place; an action lands in another.
Notion triggers
Alttext ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Account
Tool to retrieve account settings and usage information. use when you need to check your alttext.ai account configuration and usage limits before generating alt text.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account
Tool to retrieve account settings and usage information. use when you need to check your alttext.ai account configuration and usage limits before generating alt text.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Images
Tool to retrieve a paginated list of images in your library, including their alt text and metadata. use when you need to browse or filter images programmatically after authentication.
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.
Search Images
Tool to search for images and their alt text. use after specifying search keywords to retrieve matching images.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Update Account
Tool to update account settings (e.g., webhook url, name). use after confirming current account details to modify settings.
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 Alttext ai, 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 Alttext ai.