Beyond Global English: Why Vapi and Retell Struggle with 2026 Dialect Needs

I'll help you create a properly formatted Writer Agent prompt for your n8n workflow. Here's the corrected version that uses n8n expressions:

**TOPIC:** {{ $json.topic }}
**CONTENT TYPE:** {{ $json.content\_type }}
**PILLAR:** {{ $json.pillar }}
**DATE:** {{ $json.date }}

**KEYWORDS:** {{ $json.keywords }}
**PRODUCT FOCUS:** {{ $json.product\_focus }}
**SUB-TOPICS:** {{ $json.sub\_topics }}

**CTA URL:** {{ $json.cta\_url }}
**BOOKING URL:** {{ $json.booking\_url }}

**INTERNAL LINKS TO USE:**
{{ $json.internal\_links }}

**INSTRUCTIONS:**

1. RESEARCH FIRST (use Google Search):
- Search for the topic to understand what already exists online
- Search for recent data, statistics, and research related to this topic
- Search for what competitors (Vapi, Retell, Bland AI) have published on similar topics
- Find the CONTENT GAP — what has nobody explained well yet?

1. WRITE THE ARTICLE following the {{ $json.content\_type }} template from your system instructions

1. CRITICAL RULES:
- NEVER mention client names (Danube, Gargash, Century 21, RE/MAX, eSanad, Palladium)
- Use anonymous references: "a top-3 Gulf developer", "a leading automotive group", etc.
- Maximum 2 anonymous case study references in the entire article
- If content\_type is NOT a competitor comparison, do NOT make the article about competitors
- Ravan.AI mentions should feel natural, not forced — the article should be valuable even without them
- Use the SPECIFIC {{ $json.content\_type }} structure (how-to = steps, myth-buster = myths, trend = trends, etc.)

1. FORMAT:
- Start with a compelling hook (NOT "In today's fast-paced world")
- "In this article:" section with 5 items
- 5 H2 sections with H3 subsections where needed
- CTA boxes after sections 1, 3, and 5 ONLY
- FAQ with 5 questions at the end
- Tags line with 6-8 tags
- Editorial note

1. RESEARCH DEPTH:
- Include at least 3-5 external data points or statistics
- Reference at least one recent study or report (2024-2026)
- Create original frameworks or models that readers can apply

1. OUTPUT: Return the full blog post in clean Markdown format.

Key Changes Made:

1. Fixed n8n expressions: Changed from <expression> to {{ $json.field\_name }}
2. Added content\_type references: The prompt now properly uses the content type field to guide article structure
3. Enhanced research instructions: Added specific guidance on finding external data and studies
4. Clarified formatting rules: Made the CTA placement and structure requirements more explicit

How to Use This:

1. Copy the entire prompt above
2. Paste it into your WF3 Writer Agent node's Prompt field (the text input, not System Message)
3. Make sure your workflow passes these fields to the Writer Agent node:

• topic
• content\_type (NEW — must be one of: how-to, trend, myth-buster, roi, buyer-guide, industry, technical, opinion)
• pillar
• date
• keywords
• product\_focus
• sub\_topics
• cta\_url
• booking\_url
• internal\_links

Testing the Content Type System:

Try generating articles with different content types to see how the structure changes:

• content\_type: "how-to" → Should produce step-by-step guide
• content\_type: "myth-buster" → Should lead with myths and debunk them
• content\_type: "trend" → Should analyze 5-7 emerging trends
• content\_type: "technical" → Should dive deep into engineering details

Does this match your workflow structure? Let me know if you need any adjustments!