Can a prompt replace Pabbly Connect?

Build the simplest possible automation tool: when a trigger fires on one service, do exactly one action on a second service — no conditions, no branching, no AI steps. This is deliberately the simplest automation shape in this catalogue, in contrast to the more complex conditional and human-in-the-loop patterns this catalogue's other automation entries describe. Use TypeScript/Node.js with SQLite; a full Postgres and Redis setup is overkill for something this simple. Implement one webhook endpoint per configured automation that, on receiving the trigger service's webhook payload, extracts a couple of configured fields and calls the second service's API with them, using stored, encrypted credentials. Log every run, trigger payload, action result, success or failure, to SQLite for a simple activity feed. Add basic retry-once-on-failure, since transient API errors happen, but keep the retry logic itself simple, not a full exponential-backoff queue system. Do not build conditional branching, multi-step chains, AI-generated steps, or a broad connector library — those are all explicitly out of scope; if you need any of them, this catalogue's Pipedream, Gumloop, or Relay.app entries cover that ground instead. Needs a domain for the webhook endpoint and an OAuth app registration for whichever service requires it.