Go and Next.js project.

MVP feature set Triggers: webhook receiver (inbound HTTP), scheduled (cron-style), manual trigger Actions: HTTP request (call any API), send email (Resend/SMTP), Slack/Discord webhook post, delay/wait step Workflow builder: chain trigger → action → action, with conditional branching (if/else on a field) Execution engine: each run is logged with status (pending, running, success, failed), retries with backoff on failure Dashboard: list workflows, view run history, see logs per step, manually re-trigger failed runs Backend (Go) Huma v2 + Chi for the API layer pgx v5 + sqlc for data access, goose for migrations Core tables: workflows, steps, runs, run_steps, webhook_endpoints A worker (goroutine pool or a simple queue table + polling) that executes steps in order, persists state between steps so a crash mid-run can resume This is where you show real backend chops: idempotency (don't double-fire a webhook action), retry/backoff, execution state machine Frontend (Next.js) Workflow list + builder UI (drag steps in order is nice but a simple ordered list with add/remove is enough for MVP) Run history table with expandable step logs Auth (simple email/password or magic link, doesn't need to be fancy)