{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/97c4f3df8f5b4642aabd1195b94a67a1\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/97c4f3df8f5b4642aabd1195b94a67a1-b9cc017b5166919b.gif","duration":251.427,"title":"Preventing AI Hallucination in Code Outreach with Human-in-Loop Workflow ✉️","description":"Hi, I’m Abdul and in this video, I demonstrate an AISDR system I built that incorporates a human-in-loop workflow to prevent AI hallucination in code outreach. I walk you through two scenarios where we fetch a lead, draft a personalized email using the OpenRouter AI API, and send it for approval via a custom Slack app. After running the workflow, I show how the email was successfully sent to my Gmail after approval. I also explain how I utilized a rejects text parser to clean up the AI-generated content and added a brick arrow handler for system reliability. Please let me know your thoughts on this workflow and if you have any suggestions for improvement."}