Connect Zendesk to Corrently

When something happens in Zendesk, 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 Zendesk to Corrently

View example

Turn New Zendesk Tickets Into CO2 Meter Updates

Read electricity usage details from new Zendesk tickets and record an updated CO2 meter reading in Corrently.

View example

Use New Zendesk Tickets to Request PV Forecasts

Extract a site location from a new Zendesk ticket and request a Corrently PV generation forecast for planning.

View example

Create a CO2 Meter Entry From New User Energy Details

When a Zendesk user is created, use any supplied consumption details to create or update a Corrently CO2 meter reading.

View example

Request a Solar Forecast for Each New User Site

Use location information from a newly created Zendesk user to request a Corrently PV generation forecast.

View example

Send Webhook Energy Readings to a Corrently CO2 Meter

Accept an HTTP webhook with an electricity reading and create or update the corresponding Corrently CO2 meter.

View example

Turn Location Webhooks Into Corrently PV Forecasts

Receive a site location over HTTP and request an hourly Corrently PV generation forecast.

View example

Reconcile Scheduled Energy Readings in Corrently

On a schedule, review supplied electricity readings and create or update the relevant Corrently CO2 meter entries.

View example

Review Scheduled PV Forecasts for Energy Planning

Run a recurring Corrently PV generation forecast review for supplied site locations and report changes or risks.

View example

Apply Corrected Consumption From Zendesk Tickets

Use a new Zendesk ticket that reports a corrected electricity value to update the related Corrently CO2 meter.

Supported Triggers and Actions

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

Zendesk 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

New User Created

Triggered when a new user is created in Zendesk.

TriggerInstant

New Zendesk Ticket

Triggers when a new ticket is created in a specified Zendesk view.

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.