Build an Automation Workflow

Background workflows that run on schedules or webhooks: scrapers, email senders, AI batch jobs, notifications. Pair a job runner with Postgres and you have a production-grade automation platform.

Repos

Layers

Build time

A weekend

Outcome

See below

You will ship

A workflow service that runs scheduled jobs, retries on failure, and exposes a UI.

How to feed this to your AI agent Browse the full directory

Job orchestration

0 repos

More additions coming to this layer.

Database + queues

2 repos

supabase

Postgres + cron + Edge Functions. Sufficient for most v1 automation.

Postgres + Auth + Storage + Realtime + Edge Functions in one open-source platform. ~73k stars. The fastest way to ship a backend in 2026 for…

drizzle-team

drizzle-orm

Type-safe queries for the job state tables.

TypeScript-first ORM with SQL-like syntax. ~25k stars. Lighter than Prisma, zero codegen step, faster cold starts on serverless. Becoming th…

Webhooks + payments

1 repo

razorpay

razorpay-node

If your automation reacts to Razorpay events (subscription renewals, etc.).

The Indian payment stack. UPI, cards, wallets, EMI, subscriptions. INR-native so you avoid currency-conversion headaches. Mandatory if you a…

6 more layers · 11 more repos · members only

Email + notifications1 repo
Observability1 repo
Job orchestration3 repos
Postgres-native queues2 repos
Notifications2 repos
AI-augmented automation2 repos

11 more curated repos · unlock full access · members only

Unlock with lifetime membership.

Pay once. Full directory unlocked forever. No renewals, no surprise charges.

See pricing

How to build build an automation workflow with AI

The 4-step AI workflow

The AI agents are good at code. They're bad at deciding what stack to use. This bundle does the second part. You bring the agent.

1
Ideate with ChatGPT or Claude.ai (web)
Paste your idea: “I'm building build an automation workflow. Help me sharpen the product spec — features, edge cases, MVP scope.” Iterate for 10-15 minutes until you have a clear one-page brief.
2
Pick your coding agent
For this kind of bundle, we recommend Claude Code — Sonnet 4.6/4.7 handles full-stack multi-file reasoning best. See the install guide → Cursor and Codex are also great; pick the one you already pay for.

Feed this bundle to the agent

Open Claude Code / Cursor / Codex in an empty folder, then paste:

I'm building build an automation workflow. Use this bundle as the source of truth for the stack:
https://stackpicks.dev/build/automation-workflow

Brief from my product spec:
[paste your brief from step 1]

Follow the bundle order strictly:
  1. Job orchestration
  2. Database + queues
  3. Webhooks + payments
  4. Email + notifications
  ...

Stop and confirm with me after each layer.

4
Wire one layer at a time, commit between each
Don't let the agent install everything before the first git commit. One layer = one commit. Catches drift early, easy rollback.

Beyond the bundle

1Ship the boring version first. The bundle above is the maximalist list. For an MVP, start with 60% of these and add the rest when real users ask.
2Deploy early. Push to Railway / Vercel after layer 02 (auth) — not after layer 09. Production breaks differently than localhost.
3Read CLAUDE.md / .cursor/rules in this repo for the project conventions your AI agent should follow.
4Iterate on the take. If a repo here doesn't fit your specific use case, tell us — contact — and we'll add a better one within 60 minutes.