End the week with a clear impact baseline
Close the loop with a short snapshot, then return next week knowing where the current figures stand.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Total Carbon Offset
This tool retrieves the total carbon offset and other forest-related information for the authenticated user. it provides comprehensive data about the user's forest, including the total co₂ captured, number of trees planted, gifted, and received. authentication is provided via an api key in the headers (x-api-key) and no additional parameters are needed as it fetches data for the authenticated user.
Why this helps
Without a closing checkpoint, sustainability work can feel unfinished and hard to restart.
- Create a clear weekly stopping point.
- Make it easier to resume sustainability work next week.
- Close the week with current figures in view.
Setup
Build it in a few focused steps.
- 1Connect Notion and More trees to Notis once in the portal.
- 2Create an automation with one plain-language prompt to retrieve More trees totals and summarize them as a concise Friday wrap-up.
- 3Choose a Friday schedule and run-report channel, then test with one real run.
Questions about this workflow
Does this include a list of completed Notion tasks?
No. The supplied action retrieves More trees totals and does not read or summarize Notion tasks by itself.
Can I change the schedule later?
The automation schedule is selected in the portal when you create it.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to More trees. A trigger fires from one place; an action lands in another.
Notion triggers
More trees actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Total Carbon Offset
This tool retrieves the total carbon offset and other forest-related information for the authenticated user. it provides comprehensive data about the user's forest, including the total co₂ captured, number of trees planted, gifted, and received. authentication is provided via an api key in the headers (x-api-key) and no additional parameters are needed as it fetches data for the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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.
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 More trees, 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 More trees.