2 Commits

Author	SHA1	Message	Date
Arnas Donauskas	ed15493f95	feat(flows): templates + v1.5 nodes (collect_input/condition/set_tag) + run-history viewer (PR 4/4) ... Final feature PR before GA cleanup. Closes the gap between "flow runner works" (PR 2) and "users have everything they need to build real automation" — three new node types, plain-text sends actually sending, three starter templates, a run-history page for debugging. What landed: 1. engineSendText helper (src/lib/flows/meta-send.ts) — wraps sendTextMessage with the phone-variant retry + DB persistence pattern. Unblocks send_message + collect_input nodes that previously auto-advanced without sending. 2. Three new node types in the engine: - collect_input: sends a prompt, suspends, captures the next text reply into flow_runs.vars[var_key], advances. Supports {{vars.X}} interpolation in downstream prompts + handoff notes. - condition: branches on subject (var / tag / contact_field) with operators (equals / contains / present / absent). Auto-advancing, no Meta call. Pure predicate logic exported as evaluateConditionPredicate with 7 new unit tests. - set_tag: upsert/delete on contact_tags then advance. Non- fatal on write failure — logged + advances anyway so a tag glitch doesn't strand the customer. 3. Real send_message — calls engineSendText, logs the result, handles errors by ending the run with status='failed'. Same {{vars.X}} interpolation. 4. Three starter templates (src/lib/flows/templates.ts): - Welcome menu (the owner's brief example) - FAQ bot (keyword → list → answers → end) - Lead capture (first_inbound → collect_input chain → handoff with vars in the note) POST /api/flows now accepts {template_slug} to clone a template into a fresh draft. GET /api/flows/templates exposes the gallery shape (no nodes payload — fetched on actual clone). 5. Builder UI extensions: - NODE_META + config sub-forms for collect_input, condition, set_tag. - Template gallery on the /flows New-flow dialog (loads from /api/flows/templates, falls back gracefully if absent). - "Runs" button in the editor header → /flows/[id]/runs. 6. Run-history viewer at /flows/[id]/runs — newest-first list of the 50 most recent runs, with expandable per-run event timeline (started, node_entered, message_sent, reply_received, fallback_fired, handoff, timeout, error, completed). Useful for debugging "why didn't my flow advance?" from the brief's use case. 7. Validator updates: new error rules for each new node type (prompt_text required, var_key alphanumeric, operator valid, true_next/false_next exist, etc.). outgoingEdges helper now covers collect_input/condition/set_tag for reachability. All gated behind isFlowsEnabled(profile). Non-beta accounts see no change. Run-history API is also 404 for non-beta. Validation: 173/173 tests pass (added 7 new for the predicate); typecheck + lint + build all clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 14:27:01 +03:00
Arnas Donauskas	4871d7aa06	feat(flows): no-code builder UI + flows API + validator (PR 3/4) ... Ships the surface that lets opted-in beta accounts build, save, and activate WhatsApp conversation flows entirely from the web UI — no SQL fixtures needed. Sidebar gets a "Flows" entry (hidden for non-beta accounts), the /flows list page surfaces existing flows, /flows/[id] is the linear-list editor. Wraps the runner from PR 2 with everything a real user needs to build the welcome-menu example end-to-end. What landed: 1. `src/lib/flows/validate.ts` — pure validator. Checks entry node exists, all next_node_key refs resolve, no unreachable nodes, Meta-limit violations (button title ≤20, ≤3 buttons, ≤10 list rows, ≤24 chars per list row). 24 unit tests. 2. `src/app/api/flows/route.ts` — GET (list user's flows), POST (create draft). 3. `src/app/api/flows/[id]/route.ts` — GET (load with nodes), PUT (replace name + trigger + nodes; delete-then-insert), DELETE (cascade clean-up). 4. `src/app/api/flows/[id]/activate/route.ts` — status toggle. Activation runs the validator; returns 422 + the full issue list when blocked. 5. `src/app/(dashboard)/flows/page.tsx` — list of cards, "New flow" dialog, delete with confirm. 6. `src/app/(dashboard)/flows/[id]/page.tsx` — editor shell that loads data and hands it to FlowBuilder. 7. `src/components/flows/flow-builder.tsx` — the editor itself. Header with name + save/activate/pause/delete; trigger panel; entry-node picker; node list with expandable per-node config forms (start, send_buttons, send_list, send_message, handoff, end); bottom validation panel that mirrors what the server's activate endpoint would reject. 8. `src/components/layout/sidebar.tsx` — Flows entry between Automations and Settings, rendered only when isFlowsEnabled. Every API route + page is gated server-side by isFlowsEnabled — non-beta accounts get 404 (not 403) so the routes don't even hint at existing. UI gate is for snappy redirect; security is at the API layer. Validation: 166/166 tests pass (added 24 validator tests); typecheck + lint + build all clean. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-22 13:57:38 +03:00