Connect Google Super to Elasticsearch

When something happens in Google Super, Notis takes the next step in Elasticsearch. 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 Google Super to Elasticsearch

View example

Find Elasticsearch context for new Google Docs

When a Google Doc is created, search Elasticsearch for related indexed documents and send a short context summary to your report channel.

View example

Check indexed context when a Doc changes

When an existing Google Doc is updated, search Elasticsearch for related records and send a focused context report.

View example

Find indexed context for incoming Gmail

When a Gmail message arrives, search Elasticsearch for related records and send a brief context report for follow-up.

View example

Gather indexed context for new calendar events

When a calendar event is created, search Elasticsearch for related attendee or topic records and send a concise briefing.

View example

Check new Sheet rows against indexed history

When a Google Sheet row is added, search Elasticsearch for related records and report useful matches alongside the row context.

View example

Find indexed records related to newly shared files

When Drive permissions are added, search Elasticsearch for related records and report file context for an informed follow-up.

View example

Get a scheduled Elasticsearch index inventory

On a recurring schedule, list Elasticsearch indices and send an inventory report to your chosen channel.

Supported Triggers and Actions

Notis builds workflows that link Google Super to Elasticsearch. A trigger fires from one place; an action lands in another.

Google Super triggers

Elasticsearch actions

Recurring trigger

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

TriggerScheduled

Get Index Schema

View the structure and field mappings of an index.

ActionInstant

Webhook trigger

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

TriggerInstant

List Indices

Lists available Elasticsearch indices.

ActionInstant

Aggregate Metric Changed

Triggers when an aggregate calculation in a spreadsheet changes.

TriggerPolling

Query Index

Searches an Elasticsearch index for documents.

ActionInstant

Attendee Response Changed

Triggers when an attendee accepts, declines, or tentatively responds to an invitation.

TriggerPolling

Ping Cluster

Pings the cluster to check its connectivity and health.

ActionInstant

Cell Range Values Changed

Triggers when values change in a specified spreadsheet range.

TriggerPolling

Comment Added (Docs/Sheets/Slides)

Triggers when someone adds a comment to a document, sheet, or presentation.

TriggerPolling

Conditional Format Rule Changed

Triggers when spreadsheet conditional formatting rules are added, changed, or removed.

TriggerPolling

Data Validation Rule Changed

Triggers when spreadsheet data validation rules change.

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.