feat: release Vibeflow n8n v0.6.0

recipes/ai-lead-enrichment.md

@@ -0,0 +1,48 @@
+# Recipe: AI Lead Enrichment
+
+## Goal
+
+Capture a new inbound lead, enrich the company context, generate a short structured summary, score the lead using simple rules, and write the result to the CRM.
+
+## Typical trigger
+
+- new CRM lead
+- form submission
+- webhook from a landing page
+
+## Systems involved
+
+- CRM such as HubSpot or Pipedrive
+- enrichment source such as Clearbit-like data or internal lookup
+- optional LLM step for summarization
+- Slack for alerts
+
+## Core steps
+
+1. Receive the lead payload.
+2. Normalize fields such as company name, email domain, and source.
+3. Query enrichment data.
+4. Generate a concise structured summary.
+5. Apply a scoring rule based on company size, geography, and source.
+6. Update the CRM record.
+7. Notify Slack if the lead crosses a threshold.
+
+## Important assumptions
+
+- scoring starts with safe defaults
+- enrichment can fail without blocking the whole workflow
+- missing optional fields should not break CRM updates
+
+## What makes this recipe good for demos
+
+- shows practical AI usage
+- stays grounded in business logic
+- produces an output people immediately understand
+
+## Validation checklist
+
+- lead payload is parsed correctly
+- enrichment failures are captured clearly
+- summary format is stable
+- score thresholds are visible and editable
+- CRM update succeeds even when optional data is missing

recipes/slack-to-notion-triage.md

@@ -0,0 +1,47 @@
+# Recipe: Slack to Notion Triage
+
+## Goal
+
+Capture important Slack mentions, classify them, create a Notion item for tracking, and route urgent cases to an escalation channel.
+
+## Typical trigger
+
+- mention of a bot in Slack
+- reactions on flagged messages
+- specific channel messages matching a pattern
+
+## Systems involved
+
+- Slack
+- Notion
+- optional AI classification step
+- optional email or secondary Slack alert
+
+## Core steps
+
+1. Listen for the configured Slack trigger.
+2. Normalize message text, author, channel, and timestamp.
+3. Classify urgency and category.
+4. Create a Notion page or database item.
+5. Route urgent messages to an escalation destination.
+6. Write a final status field for reporting.
+
+## Important assumptions
+
+- urgency rules should be explicit and editable
+- Notion database schema is known or mapped in advance
+- Slack formatting should be simplified before storage
+
+## What makes this recipe good for demos
+
+- looks modern and relatable
+- easy to understand visually
+- strong before-and-after story from message to tracked item
+
+## Validation checklist
+
+- trigger fires only for intended messages
+- urgency logic is deterministic
+- Notion fields are mapped correctly
+- urgent path and normal path both succeed
+- duplicate handling is defined