{"workflow":{"id":13012,"name":"Generate AI case studies from Feedspace testimonials with Google Gemini and publish to WordPress","views":33,"recentViews":0,"totalViews":33,"createdAt":"2026-01-26T13:01:44.821Z","description":"**Who is this for?**\nThis template is for teams who collect customer testimonials on feedpsace (via forms) and want to automatically convert them into professional case studies using AI and publish them to WordPress.\n\n**What this workflow does**\n\nThis workflow listens for incoming testimonial data via a webhook, extracts the relevant fields, uses an AI agent to generate a complete case study (including title, sections, and structure), and publishes the final content directly to WordPress.\n\nThe AI is instructed to vary tone, angle, and structure across case studies to avoid repetitive content and improve SEO value.\n\n**Requirements:**\n- Feedspace account with webhook integration enabled\n- Access to a WordPress site with REST API enabled\n- An AI API key (Google Gemini or compatible model)\n\n**Setup steps**\n- Connect to Feedspace\n\t- Activate the workflow and copy the Production webhook URL\n\t- Go to Feedspace → Automations → Webhooks\n\t- Paste the webhook URL and activate it\n\t- See https://www.feedspace.io/help/automation/ for more information\n- Add your AI API credentials to the AI model node\n- Connect your WordPress account in the WordPress node\n- Send testimonial data to the webhook in this format:\n\t- Reviewer name\n\t- Rating\n\t- Text feedback\n\t- Event or feedback type\n\t- Activate the workflow\n\n\n\n**How it works**\n\n1. Receives testimonial data through feedpsace webhook\n2. Extracts reviewer name, rating, feedback, and event type\n3. Filters for text-based testimonials\n4. Uses an AI agent to:\n5. Choose a unique case study angle and tone\n6. Generate structured HTML content\n7. Create an SEO-optimized title\n8. Parses and validates the AI output\n9. Publishes the generated case study to WordPress as a post\n\n\n\n","workflow":{"id":"5VKYXGWVzbtLYzwp","meta":{"instanceId":"f0747a2ab7bdb7818912df9d8ffc6da4a1ce737cc82675bee25a59dc7af11611"},"name":"Generate AI-Powered Case Studies from Testimonials and Publish to WordPress","tags":[],"nodes":[{"id":"91443bc7-6d23-4356-b92f-4eecb6400ae4","name":"Feedspace Webhook","type":"n8n-nodes-base.webhook","onError":"continueRegularOutput","position":[-4256,1040],"webhookId":"feedspace-testimonial-webhook","parameters":{"path":"fs-wp","options":{},"httpMethod":"POST","responseMode":"lastNode"},"typeVersion":2.1},{"id":"4763e7fd-fbd5-4d56-b55c-06d96827de6f","name":"Extract Testimonial Data","type":"n8n-nodes-base.set","position":[-4000,1024],"parameters":{"options":{},"assignments":{"assignments":[{"id":"b547bab0-3e6b-4080-b1bb-e0efca300cbd","name":"review","type":"string","value":"={{ $json.body.data.response.comment }}"},{"id":"98ca1a27-2cb8-4fb5-8f2e-ad0c2727c222","name":"review_user","type":"string","value":"={{ $json.body.data.response.Name }}"},{"id":"94e74847-264b-4382-b527-791f922f6949","name":"feedback_type","type":"string","value":"={{ $json.body.type }}"},{"id":"rating-field-id","name":"rating","type":"string","value":"={{ $json.body.data.response.value }}"}]}},"typeVersion":3.4},{"id":"a9941a48-be90-4b7b-857f-7325bc989cb8","name":"If","type":"n8n-nodes-base.if","position":[-3776,1024],"parameters":{"options":{},"conditions":{"options":{"version":2,"leftValue":"","caseSensitive":true,"typeValidation":"strict"},"combinator":"and","conditions":[{"id":"0eaf5a98-98c8-4db5-bef7-1e6411860d63","operator":{"name":"filter.operator.equals","type":"string","operation":"equals"},"leftValue":"={{ $json.feedback_type }}","rightValue":"feed.text.received"}]}},"typeVersion":2.2},{"id":"1bfd3606-dba1-4393-8f70-932e989afbe6","name":"AI Agent - Generate Case Study & Title","type":"@n8n/n8n-nodes-langchain.agent","onError":"continueRegularOutput","position":[-3408,1024],"parameters":{"text":"=I'm sending you a new customer testimonial to convert into a case study.\n\nTESTIMONIAL DATA:\nCustomer: {{ $('Extract Testimonial Data').item.json.review_user }}\nRating: {{ $('Extract Testimonial Data').item.json.rating }} stars\nReview: {{ $('Extract Testimonial Data').item.json.review }}\n\nINSTRUCTIONS:\n\nStep 1: MEMORY CHECK\nLook back at our conversation history. Have we created case studies before? If yes:\n- What angle did the previous case study use?\n- What tone and title formula?\n- Which features were highlighted?\n- Note this in your 'reasoning' field\n\nStep 2: CHOOSE VARIETY\nBased on what you remember:\n- Select a DIFFERENT angle from last time\n- Use a DIFFERENT tone\n- Apply a DIFFERENT title formula\n- Highlight DIFFERENT product features\n\nStep 3: CREATE CASE STUDY\nGenerate a professional case study with:\n\n

Executive Summary

(or vary the header: The Breakthrough, The Success Story, etc.)\n2-3 sentences summarizing the transformation\n\n

The Challenge

(or: The Problem, The Pain Point, etc.)\nCustomer's problem before using the product\n\n

The Solution

(or: The Answer, How FeedSpace Helped, etc.)\nHow the product solved their problem - highlight different features than recent case studies\n\n

The Results

(or: The Impact, The Outcome, etc.)\nSpecific outcomes and metrics - vary between quantitative and qualitative focus\n\n

Customer Testimonial

\n

{{ $('Extract Testimonial Data').item.json.review }}

\n\n

Key Takeaways

(or: Key Benefits, Success Factors, etc.)\n\n\nStep 4: GENERATE SEO TITLE\nCreate title (50-60 characters) using one of the 5 formulas - rotate from previous usage\n\nStep 5: EXPLAIN YOUR CHOICES\nIn the 'meta.reasoning' field, briefly explain:\n- If this is your first case study: \"First case study, choosing [angle] approach\"\n- If you have memory: \"Previous case study used [X], so choosing [Y] for variety\"\n\nCRITICAL: Return ONLY the JSON object. No markdown blocks, no backticks, no extra text.","options":{"systemMessage":"You are a professional marketing content writer who creates diverse, engaging case studies from customer testimonials.\n\nCRITICAL: You have conversation memory enabled. Before creating each case study, you should:\n1. Mentally review what case studies you've created in our previous conversation turns\n2. Notice patterns: What angles did I use? What tone? What title formulas?\n3. Deliberately choose DIFFERENT approaches to create variety\n\nANGLE OPTIONS (rotate through these):\n- Transformation Story: Focus on before/after journey\n- Problem-Solution: Emphasize pain points and resolution\n- ROI-Focused: Highlight metrics, upgrades, business impact\n- Feature Spotlight: Deep dive into specific capabilities\n- Integration Success: Emphasize connections and workflow\n- Efficiency Gains: Focus on time-saving and automation\n\nTONE OPTIONS (vary these):\n- Data-driven: Metrics and statistics focused\n- Emotional: Customer satisfaction and relief focused\n- Technical: Features and capabilities focused\n- Narrative: Story-driven with journey arc\n\nTITLE FORMULAS (rotate these):\n1. \"[Customer]: Achieves [Benefit] with [Product]\"\n2. \"How [Customer] Increased [Metric] by [X]%\"\n3. \"From [Problem] to [Solution]: [Customer] Story\"\n4. \"[Customer] Leverages [Feature] to [Outcome]\"\n5. \"How [Customer] Solved [Problem]\"\n\nVARIATION STRATEGY:\n- If you just created a data-driven, ROI-focused case study with formula #2, now try emotional, transformation story with formula #1\n- If you highlighted 'Google integration' last time, focus on 'widget customization' this time\n- If you used

Executive Summary last time, try

The Breakthrough this time\n- Keep content fresh by changing section headers, emphasized features, and narrative angles\n\nRESPONSE FORMAT:\nReturn ONLY valid JSON (no markdown, no code blocks):\n{\n \"title\": \"SEO-optimized title (50-60 chars)\",\n \"content\": \"

Section

Content...

\",\n \"meta\": {\n \"angle\": \"transformation_story\",\n \"tone\": \"emotional\",\n \"title_formula\": \"formula_3\",\n \"features_highlighted\": [\"feature1\", \"feature2\"],\n \"reasoning\": \"Chose X because previous case study used Y\"\n }\n}\n\nHTML RULES:\n-

for headers\n-

for paragraphs\n-

for quotes\n-