trigger.fyi is a push notification service for developers — specifically, for notifying yourself when something in your code happens.

Not your users. You.

#The problem it solves

You’ve launched a product, script, job, or service. Something happens — a user signs up, a payment comes in, a background job finishes. You find out by opening a dashboard, checking logs, or waiting until you happen to look.

trigger.fyi closes that gap. When something happens in your code, your phone knows.

#The model

There are three parts:

A key — a random token that identifies your app. One key per service, stored in an environment variable.

Send — POST plain text to trigger.fyi/your-key. That’s the API. Any language, any runtime, any environment that can make an HTTP request.

Watch — subscribe a device to receive the notifications. Your phone, your terminal, a colleague’s phone.

Send once, every watching device receives it.

#The quickest path to a notification

# Terminal 1 — start watching
npx trigger.fyi
 
# Terminal 2 — send something
curl -X POST "https://trigger.fyi/$TRIGGER_FYI_SECRET_KEY" -d "Hello"

Terminal 1 shows the event live. Scan the QR code to add your phone.

#The SDK

npm install trigger.fyi

import fyi from "trigger.fyi"
 
fyi("Someone signed up", { body: "[email protected]" })

fyi() never throws, never blocks, never fails your request. Fire-and-forget by design.

Three levels:

• fyi() — normal push notification
• fyi.log() — recorded in the feed, no push
• fyi.critical() — highest urgency the platform allows

#What it’s not

trigger.fyi is not for notifying your users. It’s for notifying you.

trigger.fyi is not incident monitoring. A signup isn’t an incident. A payment isn’t an incident. A background job finishing is not an incident. These are things that happened — you should know, without declaring an emergency.

trigger.fyi is not a logging platform. fyi.log() keeps a history, but the product isn’t built around querying and analyzing logs. It’s built around the moment of knowing.

#Who it’s for

Developers who have something running in production and currently check a dashboard or tail logs to know what it did.

The best early users are solo developers or small teams who want to know when a meaningful event happens — a real signup, a real payment, a long job completing — without setting up monitoring infrastructure.

#The 60-second path

1. npx trigger.fyi in your terminal
2. A key is generated, your terminal starts watching
3. Scan the QR code to add your phone
4. Run curl -X POST "https://trigger.fyi/$KEY" -d "Hello" from another window
5. Your terminal and phone both receive it

One key, one curl. No credit card.

#Pricing

The core loop — send, watch, receive — is free. Longer history and higher limits are coming in paid plans.

Related: The curl guide to trigger.fyi · Push notifications from Node.js · Cron job notifications · Pushover alternatives for developers