Connect GitHub to Elasticsearch

When something happens in GitHub, 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 GitHub to Elasticsearch

View example

Find context for new code scanning alerts

Search Elasticsearch for related records when GitHub creates a code scanning alert, then summarize useful context for triage.

View example

Search indexed evidence for new GitHub issues

When a new GitHub issue arrives, search Elasticsearch for related records and summarize possible prior context.

View example

Search Elasticsearch after a pull request review

After a GitHub review is submitted, search Elasticsearch for related records that may help explain the review decision.

View example

Check indexed context when a pull request gets a commit

Search Elasticsearch for related records when a new commit is added to a pull request, then report context for review.

View example

Search Elasticsearch after a failed check run

When a GitHub check run changes, search Elasticsearch for related records that may help explain a failure.

View example

Search indexed records for secret alert context

When GitHub detects a secret scanning alert, search Elasticsearch for related records to support a focused investigation.

View example

Check Elasticsearch index availability on pull request activity

When a pull request is opened, closed, or synchronized, list Elasticsearch indices and report which may hold relevant records.

View example

Inspect Elasticsearch schema when a pull request opens

When a new GitHub pull request is created, inspect a relevant Elasticsearch index schema and summarize fields for search planning.

View example

Check Elasticsearch connectivity when a GitHub workflow run changes

When a GitHub Actions run changes state, ping Elasticsearch and report whether the cluster responds.

Supported Triggers and Actions

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

GitHub 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

New Workflow Artifact Created

Triggers when a new workflow artifact is created in a repository.

TriggerPolling

Query Index

Searches an Elasticsearch index for documents.

ActionInstant

Branch Changed

Triggers when a branch receives commits or its protection settings change.

TriggerPolling

Ping Cluster

ActionInstant

New Branch Created

Triggers when a new branch is created in a repository.

TriggerPolling

Check Run Status / Conclusion Changed

Triggers when a check run’s status or conclusion changes.

TriggerPolling

Check Suite Status / Conclusion Changed

Triggers when a check suite’s status or conclusion changes for a reference.

TriggerPolling

New Code Scanning Alert Created

Triggers when a new code scanning alert is created in a repository.

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.