Per-pair page

Connect Gmail to Elasticsearch in two minutes.

Real-time triggers from Gmail, ready-made actions in Elasticsearch. Filter, transform, and route without writing a line of code.

Connect Gmail and Elasticsearch See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

Elasticsearch as the action

Workflows do something in Elasticsearch, instantly.

Index DocumentAPI

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

Gmail → Elasticsearch

When something happens in Gmail, do it in Elasticsearch.

1 Gmail triggers wired to 1 Elasticsearch actions. Most-used pairing: New Email → Index Document.

New Email

Elasticsearch → Gmail

Or fire it the other way around.

0 Elasticsearch triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See Elasticsearch → Gmail →

Popular pairings

Common Gmail → Elasticsearch workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 1 of 1 combinations

When new email in Gmail, index document in Elasticsearch.

Fires when a new email is received in Gmail. Returns full email content; enable "Include Attachments" to automatically download all file attachments.

How it works

Connect Gmail and Elasticsearch in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize Gmail and Elasticsearch
Open Tiny Command, authorize Gmail and Elasticsearch once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a Gmail trigger
Drop the Gmail → New Email trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/google-gmail.trigger-email-received
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the Elasticsearch action
Drop the Elasticsearch → Index Document action below it. Map fields from the Gmail payload into the Elasticsearch inputs.
elasticsearch-api.elasticsearch-index-document
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about Gmail + Elasticsearch.

How long does it take to connect Gmail and Elasticsearch on Tiny Command?

Under two minutes. Authorize Gmail and Elasticsearch once each, drop the Gmail trigger and Elasticsearch action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.

Is the Gmail ↔ Elasticsearch integration real-time?

Yes. Both Gmail and Elasticsearch expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.

Can I filter or transform data between Gmail and Elasticsearch?

Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Elasticsearch.

What Gmail events can trigger a Elasticsearch workflow?

Any of the 1 Gmail triggers, including "New Email". Each fires in real time when the matching event happens in Gmail.

Do I need a paid plan to use Gmail with Elasticsearch?

No. There's a free tier that covers most Gmail+Elasticsearch use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.

What if I want Elasticsearch → Gmail instead?

Build it the same way, in reverse. There's a dedicated /integrations/elasticsearch-api/with/google-gmail page with the reverse-direction triggers and actions.

Other apps that pair well with Gmail.

Gmail + Slack

Communication

Gmail + Google Sheets

Spreadsheets & Databases