feat: launch Vibeflow n8n v0.5.0

recipes/invoice-reminder.md

@@ -0,0 +1,17 @@
+# Recipe: Invoice Reminder Workflow
+
+## Scenario
+
+Track invoices nearing due date, notify the internal team, and optionally send customer reminders with explicit approval rules.
+
+## Caution
+
+This recipe should not assume customer-facing messages are allowed without confirmation.
+
+## Suggested intake questions
+
+1. Where do invoice records come from?
+2. How many days before due date should reminders fire?
+3. Is there an approval step before contacting customers?
+4. Which channels should be used for internal vs external notifications?
+5. How should paid invoices be excluded?

recipes/lead-triage.md

@@ -0,0 +1,51 @@
+# Recipe: Lead Triage with AI Enrichment
+
+## Scenario
+
+A user wants to capture incoming leads, enrich them with AI, classify urgency, notify a team, and store the lead in a structured system.
+
+## Typical trigger
+
+- webhook
+- form submission
+- CRM new record
+
+## Systems involved
+
+- form tool or webhook source
+- AI provider
+- Slack or email
+- Airtable / HubSpot / CRM
+
+## Suggested intake questions
+
+1. What triggers the workflow?
+2. Where should the lead be stored?
+3. How should hot leads be defined?
+4. Who should be notified and where?
+5. Should the workflow create-only or upsert existing leads?
+
+## Suggested node sequence
+
+1. Trigger
+2. Normalize payload
+3. AI enrichment / classification
+4. Conditional branch by priority
+5. Notification for high priority
+6. Store record
+7. Error notification branch
+
+## Common risks
+
+- duplicate lead creation
+- unclear hot/warm/cold criteria
+- missing CRM identifiers
+- over-broad notifications
+
+## Validation checklist
+
+- priority branch exists
+- CRM mapping is explicit
+- alert channel is defined
+- duplicate strategy is stated
+- missing credential placeholders are visible

recipes/support-triage.md

@@ -0,0 +1,23 @@
+# Recipe: Support Ticket Triage
+
+## Scenario
+
+Route support requests from a form, email parser, or webhook into categorized queues with optional AI summarization and escalation.
+
+## Suggested node sequence
+
+1. Trigger
+2. Extract or normalize ticket fields
+3. AI summary and category suggestion
+4. Severity classification
+5. Conditional routing
+6. Ticket creation or update
+7. Team notification
+8. Failure path
+
+## High-value follow-ups
+
+- What defines severity?
+- Which queues or teams should receive each category?
+- Should responses be internal-only or customer-facing?
+- Should the workflow auto-tag, auto-assign, or only recommend?