feat: release Vibeflow n8n v0.7.0

This commit is contained in:
Felipe Domingues 2026-04-12 14:01:31 -03:00
parent 260d447f40
commit d09d9a7c8f
9 changed files with 315 additions and 74 deletions

View file

@ -0,0 +1,35 @@
# Recipe: Customer Support Escalation
## Goal
Create an n8n workflow that watches a support inbox or helpdesk webhook, detects priority signals, enriches the ticket context, and escalates high-risk items to Slack with a clear summary.
## Why it demos well
- obvious business value
- clear trigger and escalation outcome
- easy to explain in less than two minutes
- one branch can demonstrate prioritization logic
## Suggested steps
1. Trigger from webhook or helpdesk event
2. Normalize ticket payload
3. Score urgency using rules or an LLM step
4. Route high-priority items to Slack
5. Log normal-priority items to a sheet or database
6. Add error notifications
## Critical questions
- What tool sends the ticket event?
- What counts as urgent?
- Who should receive escalations?
- Should every item be logged, or only urgent ones?
## Safe defaults
- urgency based on keywords, SLA breach flag, and VIP marker
- Slack notification for high priority only
- spreadsheet log for all processed tickets
- retry once before failure alert

View file

@ -0,0 +1,34 @@
# Recipe: HubSpot to Slack Qualification
## Goal
Create an n8n workflow that listens for new or updated HubSpot leads, evaluates qualification rules, and sends only promising leads to Slack with a concise summary.
## Why it demos well
- popular stack
- simple trigger, filter, and notification pattern
- easy to narrate as a sales ops use case
## Suggested steps
1. Trigger on lead created or updated
2. Map company, role, source, and score fields
3. Apply qualification rules
4. Send qualified leads to Slack
5. Log non-qualified leads for later review
6. Emit failure alerts when processing breaks
## Critical questions
- Which HubSpot event should trigger the flow?
- What rules define a qualified lead?
- What Slack channel should receive alerts?
- Should the workflow update HubSpot properties too?
## Safe defaults
- qualify by score threshold and role/company fit
- send concise Slack message with source and score
- log rejected leads to a review table
- leave CRM write-back optional