Skip to content
ntfy logoEmailit logo

Connect ntfy to Emailit

Move data between ntfy and Emailit 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.

ntfy triggers
1
ntfy actions
8
Emailit triggers
0
Emailit actions
21

Automation ideas

What you can build with ntfy and Emailit

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

  • New Message in ntfy creates Send Email in Emailit

    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 Message in ntfy creates Get Email in Emailit

    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 Message in ntfy creates Find Emails in Emailit

    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.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in ntfy and acts in Emailit, 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.