Capture energy readings from Telegram
Turn a Telegram message with electricity usage details into a Corrently CO2 meter reading, so consumption does not need to be logged later.
When something happens in Telegram, 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
Creates or updates an electricity reading for CO₂ emissions tracking.
Turn a Telegram message with electricity usage details into a Corrently CO2 meter reading, so consumption does not need to be logged later.
When a Telegram message identifies a site and location for planning, ask Corrently for an hourly PV generation forecast to inform energy scheduling.
Turn consumption figures published in a Telegram channel into Corrently CO2 meter readings, keeping shared operating updates traceable.
Let a teammate tap an inline button to request Corrently's hourly PV generation forecast for the location discussed in the bot conversation.
When a Telegram message with energy figures is edited, have Notis update the relevant Corrently CO2 meter reading to reflect the correction.
When a Telegram planning message names a location and a proposed operating window, request Corrently hourly PV estimates to help assess timing.
When a new operator joins a Telegram group, use the onboarding context to prompt a first consumption reading into Corrently when they share it.
Request a Corrently hourly PV generation forecast each morning for a chosen location, giving the founder a repeatable input for energy decisions.
Run a weekly check for newly provided energy usage details and update the corresponding Corrently CO2 meter reading when found.
Notis builds workflows that link Telegram to Corrently. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Creates or updates an electricity reading for CO₂ emissions tracking.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Provides hourly solar generation forecasts for a location in Germany.
Finalize an electricity receipt after collecting the seller, buyer, and transaction details.
Convert a place name or free-text location into geographic coordinates.
Plans the best operating times for energy-hungry devices using regional renewable, price and emissions forecasts.
Creates an optimized schedule of operating time slots for energy-consuming devices, such as heat pumps or EV chargers, using the GrünstromIndex (Green Power Index). It analyzes regional renewable energy availability, electricity prices, and CO₂ emissions forecasts. Regional data requires a German postal code; computation also requires the desired goal—price, CO₂, or comfort—and the number of hours the device needs to run.
Retrieve an electricity meter reading with its green and grey energy split and CO2 emissions.
Retrieve account balances for green energy bonuses, generation, self-consumption, offsets, and trees planted.
Retrieve the available contract choices for an energy account.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Telegram and Corrently, or any other combination from 1,500+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Corrently.