Can ntfy and Gmail talk in both directions?

Yes. Build one flow that starts in ntfy and acts in Gmail, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.

Connect ntfy to Gmail

Move data between ntfy and Gmail the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Start building Explore ntfy Explore Gmail

ntfy triggers: 1
ntfy actions: 8
Gmail triggers: 4
Gmail actions: 11

Automation ideas

What you can build with ntfy and Gmail

A few flows teams run between ntfy and Gmail. Use one as a starting point, or build your own from scratch.

New Message in ntfy creates Send Email in Gmail
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Email in Gmail creates Send Notification in ntfy
Triggers when a new email matching the filters arrives.
New Message in ntfy creates Request Approval in Email in Gmail
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Email in Gmail creates Send File in ntfy
Triggers when a new email matching the filters arrives.
New Message in ntfy creates Reply to Email in Gmail
Triggers when a message is published to a ntfy topic. Needs the server to cache messages (ntfy.sh keeps them 12 hours); messages sent with "Do not cache" are never seen.
New Email in Gmail creates Update Notification in ntfy
Triggers when a new email matching the filters arrives.