Connect Gmail to Corrently

When something happens in Gmail, Notis takes the next step in Corrently. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Gmail to Corrently

View example

Turn Utility Bills Into CO2 Meter Updates

When a utility bill arrives in Gmail, use its electricity consumption details to update the matching Corrently CO2 meter reading.

View example

Get a Solar Forecast From a Site Inquiry

When a Gmail message includes a location and asks about solar availability, get an hourly Corrently PV generation forecast for that location.

View example

Log Sent Electricity Readings in Corrently

When you send an email containing a new electricity consumption reading, update the relevant Corrently CO2 meter from its details.

View example

Forecast Solar Output From Sent Site Details

When you send a Gmail message with a site location and a request for solar output analysis, get Corrently's hourly PV forecast.

View example

Run a Scheduled Solar Production Forecast

On a recurring schedule, request Corrently's hourly PV generation forecast for a location you specify in the automation instruction.

View example

Schedule a Recurring Corrently Meter Reading

On a recurring schedule, create or update a Corrently CO2 meter reading using electricity consumption data you provide in the instruction or run context.

View example

Request a Solar Forecast From a Site Webhook

When an HTTP request supplies a site location and forecast request, retrieve Corrently's hourly PV generation forecast for that location.

View example

Update a CO2 Meter From a Reading Webhook

When an HTTP request provides an electricity consumption reading and meter context, create or update the corresponding Corrently CO2 meter reading.

Supported Triggers and Actions

Notis builds workflows that link Gmail to Corrently. A trigger fires from one place; an action lands in another.

Gmail triggers

Corrently actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Email Sent

Triggers when a Gmail message is sent by the authenticated user. It polls the 'SENT' label and emits metadata including sender, recipients, subject, timestamp, and thread ID.

TriggerPolling

New Gmail Message Received Trigger

Triggers when a new message is received in Gmail.

TriggerPolling

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.