Per-pair page

Connect Gmail to ntfy in two minutes.

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

Connect Gmail and ntfy See reverse direction

Trigger app

Gmail as the trigger

Workflows fire when something happens in Gmail.

New EmailWebhook

Action app

ntfy as the action

Workflows do something in ntfy, instantly.

Both directions

Pick the way that fits your stack.

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

Gmail → ntfy

When something happens in Gmail, do it in ntfy.

1 Gmail triggers wired to 2 ntfy actions. Most-used pairing: New Email → ntfy Send Notification.

New Email

ntfy → Gmail

Or fire it the other way around.

0 ntfy triggers wired to 27 Gmail actions downstream.

Use any trigger in the catalog as the upstream.

See ntfy → Gmail →

Popular pairings

Common Gmail → ntfy workflows.

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

Showing 2 of 2 combinations

When new email in Gmail, ntfy send notification in ntfy.

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

When new email in Gmail, ntfy send with tags + priority in ntfy.

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 ntfy in five steps.

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

1
Connect
Authorize Gmail and ntfy
Open Tiny Command, authorize Gmail and ntfy 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 ntfy action
Drop the ntfy → ntfy Send Notification action below it. Map fields from the Gmail payload into the ntfy inputs.
ntfy.send-notification
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 + ntfy.

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

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

Is the Gmail ↔ ntfy integration real-time?

Yes. Both Gmail and ntfy 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 ntfy?

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 ntfy.

What Gmail events can trigger a ntfy 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 ntfy?

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

What if I want ntfy → Gmail instead?

Build it the same way, in reverse. There's a dedicated /integrations/ntfy/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