Bring a fresh solar outlook to regular planning
Get a Corrently production forecast on the planning cadence that suits your team.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
PV Generation Forecast
Tool to get solar energy production forecasts (hourly output and loss estimates) for a specific location. use when you need hourly pv generation data to optimize energy scheduling.
Why this helps
A forecast check can be useful for planning, but a manual lookup is easy to skip when the week gets busy.
- Build a regular forecast check into planning.
- Reduce repeated manual lookups for hourly production estimates.
- Keep the request tied to a predictable routine.
Setup
Build it in a few focused steps.
- 1Connect Notion and Corrently to Notis once in the portal.
- 2Create the automation in the portal or ask Notis to make it conversationally.
- 3Write one instruction for the location and planning context to use when requesting a Corrently PV forecast.
- 4Select a recurring schedule and choose a channel for run reports.
- 5Run one real example and confirm the forecast request.
Questions about this workflow
Can this use location details from Notion?
Describe in the prompt which Notion context Notis should use along with the scheduled forecast request.
What does a forecast provide?
Corrently's PV Generation Forecast action returns hourly production forecasts and loss estimates for a specific location.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Corrently. A trigger fires from one place; an action lands in another.
Notion triggers
Corrently actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
CO₂ Meter Update
Tool to create or update a co₂ meter reading for emissions tracking. use when sending new or updated electricity consumption readings to corrently.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
PV Generation Forecast
Tool to get solar energy production forecasts (hourly output and loss estimates) for a specific location. use when you need hourly pv generation data to optimize energy scheduling.
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 Corrently, 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 Corrently.