# Build brief — a focused alternative to IFTTT

> **Verdict:** Yes, for personal use · **Buildability:** 81/100 · **Category:** Automation
> **Source:** https://www.canitbevibecoded.com/ifttt
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from IFTTT. Verify current pricing and capabilities before acting.

## Context

**IFTTT** — Consumer automation applets across smart home, apps, and services. It currently costs $2.99/mo.

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.

This brief describes a focused, single-operator replacement for the part of IFTTT that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Create small trigger-action scripts, poll APIs or receive webhooks, and call target APIs.

- Automate a small number of known workflows with logs, retries, and manual recovery.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Small hosted function.
- Secrets storage.

### Data and integrations

- API keys/OAuth.
- Webhook endpoint or scheduler.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

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.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Consumer integration catalog.
- Smart-home integrations.
- Mobile applets.
- Easy UI.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Huginn](https://github.com/huginn/huginn) — Open-source system for building agents that monitor and act on events; useful IFTTT-style 

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/ifttt