Arnas Donauskas 570fc1234c fix(automations): reject activation of invalid step/trigger config ... Activating an automation with obviously-broken config (add_tag step with empty tag_id, send_message with empty text, keyword_match trigger with no keywords, etc.) used to succeed — and then every dispatch produced a cryptic failed log row that users often missed. - New validate.ts centralises the checks (mirrors engine.ts's runtime guards one layer earlier so failures surface at save time). Returns { path, message } issues so the UI can point users at the exact problem. - POST /api/automations rejects with 400 when is_active === true and the merged config fails validation. - PATCH /api/automations/[id] computes the post-patch "effective" state (merging body fields over the existing row, loading current steps if body.steps isn't provided) and applies the same gate. Drafts (is_active=false) remain free to be incomplete so users can still save progress mid-build. - Builder surfaces the first issue in a toast with path as the description, so users don't need DevTools to find what to fix. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-17 21:50:13 +03:00
..
automations	fix(automations): reject activation of invalid step/trigger config	2026-04-17 21:50:13 +03:00
whatsapp	feat(automations): add 'First Message from Contact' trigger	2026-04-17 20:47:13 +03:00