Reconcile Drive usage changes with Corrently
Let Notis review Drive change notices for energy usage updates that should be reflected in Corrently.
Trigger
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Action
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.
Why this helps
Consumption details can change across Drive files, making it easy to miss a correction when updating emissions records.
- Review a stream of Drive changes for relevant usage information.
- Reduce the chance of overlooking a revised consumption record.
- Flag uncertain changes for human review.
Setup
Build it in a few focused steps.
- 1Connect Google Drive and Corrently once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for energy record reconciliation.
- 3Tell Notis to inspect detected Drive changes for supported electricity usage revisions and update Corrently only when the right reading is clear.
- 4Pick the Google Drive Changes trigger and choose where run reports go.
- 5Test with one real change that includes an energy usage revision and verify the report.
Questions about this workflow
Does this trigger cover all Drive changes?
It starts when changes are detected in Drive. Your instruction should make clear which changed files are relevant to energy consumption.
Will Notis invent missing history or a baseline?
No. Ask it to flag missing context and avoid creating a reading when the source does not support the value.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Google Drive to Corrently. A trigger fires from one place; an action lands in another.
Google Drive 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.
Comment Added (Docs/Sheets/Slides)
Triggers when a new comment is added to Google Docs, Sheets, or Slides.
File Created
Triggers when a new file is created in Google Drive.
File Deleted or Trashed
Triggers when a file is moved to trash or permanently deleted in Drive.
File Shared (Permissions Added)
Triggers when new sharing permissions are granted to a file or folder. Uses Drive's `changes.list` endpoint with inline `permissions` in the `fields` mask so each change carries the file's current permission set provider-atomically. We diff that against `seen_permission_keys` to identify newly added grants. Drive page tokens are the primary cursor; if Drive rejects a stored token, the trigger raises `PollingTriggerError` without clearing state rather than silently re-baselining and dropping events. Limitation: truly ephemeral permissions (added and revoked between two polls without any other file modification in between) are not detected. Drive Activity API would catch those but requires an additional OAuth scope and a different payload contract.
File Updated
Triggers when a file's metadata or content changes in Google Drive.
Google Drive Changes
Triggers when changes are detected in a Google Drive.
Connect any two apps with Notis in the middle.
Google Drive 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.