Connect Whatsapp to Elasticsearch

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

View example

Find answers for new WhatsApp questions

Search Elasticsearch for relevant documents when a customer sends your WhatsApp Business number a message, then summarize the useful context for you.

View example

Check which search indices are available

When a new WhatsApp message arrives, list Elasticsearch indices so you can see which searchable collections are available for answering it.

View example

Look up records after a WhatsApp selection

When a customer selects a WhatsApp quick reply or list option, query Elasticsearch for related records and summarize the matches for your next step.

View example

Check indexed context when message status changes

When WhatsApp reports a message status change, query Elasticsearch for related indexed records and summarize context that may help you investigate the conversation.

View example

Review searchable collections after template status changes

When a WhatsApp template's review status changes, list Elasticsearch indices and report which searchable collections are available for related support context.

View example

Check Elasticsearch when a WhatsApp issue is reported

Start from a Notis webhook when you report an operational issue, then ping Elasticsearch and receive a concise connectivity result alongside the report.

View example

Review Elasticsearch support index structure on a schedule

On a schedule, retrieve the mapping for a chosen Elasticsearch index and summarize its structure for maintaining WhatsApp support lookups.

Supported Triggers and Actions

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

Whatsapp 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

Message Status Updated

Returns no results; message status changes are delivered through webhooks in real time.

TriggerPolling

Query Index

Searches an Elasticsearch index for documents.

ActionInstant

Ping Cluster

Pings the cluster to check its connectivity and health.

ActionInstant

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.