Review Beeminder when your goal plan changes
A meaningful plan edit is a good moment to revisit the goal you are tracking.
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
Authenticate and Redirect User
Tool to authenticate a user and redirect them to a given url. use when sending a user into the beeminder web ui directly after oauth or token validation.
Why this helps
Plan changes can leave tracked goals out of sync with the direction you intend to follow.
- Link plan revisions to a timely tracking review.
- Keep the next step close to the edit that prompted it.
- Reduce the chance that a revised goal is forgotten.
Setup
Build it in a few focused steps.
- 1Connect Notion and Beeminder to Notis once in the portal.
- 2Create an automation in the portal or ask Notis to set it up conversationally.
- 3Ask Notis in one plain-language instruction to open Beeminder when the content of your goal plan page changes.
- 4Choose the Notion page-content-updated trigger scoped to the goal plan page and a report channel, then test with one real edit.
Questions about this workflow
Will it update a Beeminder goal automatically?
No. It opens Beeminder for you to review the goal.
Can I limit it to one plan page?
Yes. The page-content-updated trigger can be scoped to a specific page.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Beeminder. A trigger fires from one place; an action lands in another.
Notion triggers
Beeminder actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Authenticate and Redirect User
Tool to authenticate a user and redirect them to a given url. use when sending a user into the beeminder web ui directly after oauth or token validation.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Charge
Tool to create a new charge for a user. use when billing a user outside of goal pledges; supports dryrun mode.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get all goals
Tool to retrieve all goals for a specified user. use when listing a user's active goals.
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 Archived Goals
Tool to retrieve archived goals for a specified user. use when you need to inspect a user's past archived goals.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get Beeminder User Information
Tool to retrieve information about a specified beeminder user. use when you need to fetch details like timezone, goals, urgency, or deleted goals after authenticating successfully.
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 Beeminder, 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 Beeminder.