Check avoided emissions when your plans are refreshed
A content update can be a useful cue to revisit the carbon avoidance figure connected to your plans.
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 User Carbon Offset
Tool to get the total tonnes of CO2e emissions a user has avoided (carbon offset). Data refreshes every 10 minutes. No authentication required.
Why this helps
When sustainability notes change, remembering to refresh the related impact context becomes another loose end.
- Retrieve the emissions avoided total after a page content edit.
- Reduce a separate manual Ecologi lookup during planning.
- Use the new page content as context for a concise update.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ecologi to Notis once in the portal.
- 2Create an automation or ask Notis to check Ecologi carbon avoidance after Notion page content changes.
- 3Describe in a single plain-language prompt the kind of update you want after a content edit.
- 4Select Page Content Updated and a run-report channel, then test with one real content change.
Questions about this workflow
Can I scope content changes to a page or data source?
Yes. The trigger can be scoped to one page, one data source or a parent page, or left workspace-wide.
How quickly does the trigger arrive?
Notion aggregates many content edits within a short window, typically around 60 seconds.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ecologi. A trigger fires from one place; an action lands in another.
Notion triggers
Ecologi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get User Carbon Offset
Tool to get the total tonnes of CO2e emissions a user has avoided (carbon offset). Data refreshes every 10 minutes. No authentication required.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Carbon Removal
Tool to retrieve the total tonnes of CO₂e a user has permanently removed from the atmosphere. Data refreshes every 10 minutes. Use when checking carbon offset impact for a specific Ecologi user or business.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get User Habitat Restoration
Tool to get the total area of habitat and ecosystem a user has restored. Data refreshes every 10 minutes. No authentication required.
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 User Impact
Tool to get a combination of all impact types a user has funded: trees, carbon avoidance, carbon removal, and habitat restoration, in a single request. Data refreshes every 10 minutes and no authentication is required.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Get User Trees
Tool to get the total number of trees a user has funded on Ecologi. Use when you need to retrieve tree statistics for a specific user. Data refreshes every 10 minutes.
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 Ecologi, 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 Ecologi.