Check past Beamer posts as feature plans evolve
Feature plans change, and old announcements can become relevant again. Let Notis search Beamer for posts connected to an edited brief.
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 Posts
Tool to retrieve a list of posts. use when you need ids and titles of posts for further operations.
Why this helps
Keeping feature plans and past announcements in mind at once can make overlap checks hard to fit into a busy day.
- Search for existing posts when a brief changes.
- Keep the review tied to the edited Notion page.
- Get a concise report instead of reopening Beamer to search manually.
Setup
Build it in a few focused steps.
- 1Connect Notion and Beamer to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3In one instruction, ask Notis to search for Beamer posts related to the changed feature brief and report titles and IDs.
- 4Choose the Notion Page Content Updated trigger scoped to the feature briefs data source and a channel for run reports.
- 5Test by editing one real feature brief.
Questions about this workflow
Will every body edit run the search?
The trigger aggregates content edits over a short window, but each qualifying update can start a run.
Can the automation decide whether a match is truly a duplicate?
It can surface related posts for your review. Treat relevance as a prompt for checking, not as a definitive duplicate decision.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Beamer. A trigger fires from one place; an action lands in another.
Notion triggers
Beamer actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Count Posts
Tool to count existing posts. use when you need the number of posts matching specific filters.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Category
Tool to retrieve a specific category by its id. use when you need to load metadata for a category before filtering or grouping posts by that category.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Feed
Tool to retrieve the url for your standalone feed. use after embedding to fetch the feed link for embedding or sharing.
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.
Get Feeds
Tool to retrieve the url for your feed. use when you need to embed or access your standalone feed.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Feed URL
Tool to retrieve the url for your personalized feed. use after setting segmentation or language options to embed or redirect users.
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.
Get Notification
Tool to retrieve details of a specific notification by its unique notification id. use after obtaining the notification id to fetch its full details.
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.
Get Notifications
Tool to fetch unread notifications. use after providing user context to retrieve and mark notifications as read.
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.
Get Post Comments
Tool to retrieve comments for a specific post. use after identifying the post id to list its comments.
Connect any two apps with Notis in the middle.
Notion and Beamer, 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 Beamer.