Can I vibecode IFTTT?

price $2.99/moyou'd save $35.88/yrbuild time one sittingcategory automationreplaced by 1 people

YES

MOATintegrationsexecution polish

For a few personal applets, a script or simple webhook worker is enough; the full consumer integration catalog and smart-home breadth are what you lose.

In-List Ad$79/30 days

promote your product in the vibecoded list

The Build Prompt

copy it and go build

ready to paste · 1,190 chars

open in Claude Code open in Codex open in Cursor

Build me a personal trigger-action automation runner to replace IFTTT. Requirements:

- A single Node project: each applet is one JS file in applets/ exporting a trigger
  (cron expression or webhook path) and an action function. node-cron for schedules,
  Express on localhost:4820 for incoming webhooks.
- Ship three working example applets: new RSS item sends a push via ntfy.sh, a 7am
  weather check emails me if rain is forecast, a GitHub webhook appends to a log.
- Poll-based triggers keep a last-seen cursor in SQLite (better-sqlite3) so restarts
  never double-fire.
- Every run logged to SQLite: applet, timestamp, ok/fail, error text. A /log page
  lists the last 100 runs.
- Failures retry 3 times with backoff, then send one alert email (SMTP creds in .env).
- All API keys and tokens live in .env, referenced by name from applet files.
- Runs as a single systemd service. Binds to localhost only, no accounts, no
  telemetry.
- Out of scope: a visual applet builder and smart-home device integrations. A new
  applet is a new file, that is the UI.
- README: how to write an applet, .env keys, and how to tunnel the webhook path when
  a third-party service needs to reach it.

In-List Ad$79/30 days

promote your product in the vibecoded list