Researched stories and visuals delivered to the client's inbox automatically
Catches trending music & sports stories while they are still fresh
Client email approval before any content is published
The client publishes weekly music and sports content, but keeping up with breaking news, picking trending stories, writing posts, and creating visuals took hours every week—and by the time assets were finished manually, some stories were already stale.
Built a weekly n8n workflow that scrapes trending posts via Apify, runs live web searches for breaking music and sports news, uses OpenAI to select and write up the best stories, generates matching visuals with an AI image model, saves assets to Google Drive, and emails the weekly pack via Gmail for client approval.
Runs automatically every week with a configurable settings node at the start so search topics can be updated without editing workflow logic.
Combines Apify social scraping with live web search so the workflow captures what fans are talking about right now plus breaking news.
OpenAI selects the strongest stories and writes the copy, while an AI image model creates a custom visual for each story.
Uploads finished visuals to Google Drive and emails the weekly content pack to the client's inbox so nothing goes out without their sign-off.
Built a scheduled weekly n8n workflow with an easy-to-edit topic configuration node
Combined Apify source scraping with live web searches to gather fresh music and sports stories
Used OpenAI to rank stories and write engaging social copy for the week's pack
Generated matching visuals automatically, stored them in Google Drive, and sent a Gmail approval digest
Researched stories and visuals delivered to the client's inbox automatically
Catches trending music & sports stories while they are still fresh
Client email approval before any content is published
Watch the 22-second walkthrough showing how this system runs from start to finish.
Our Role
AI Automation Developer
Client
Digital Media Publisher
Industry
Marketing Analytics
Delivery Timeline
2 weeks
Book a free discovery call and we'll map out how to build this for your exact data sources and tools.
VideoThe client was sending the exact same follow-up email to every lead regardless of what they did with the previous message—someone who clicked a link got the same follow-up as someone who never opened it. Worse, replies were easy to miss, so leads sometimes kept getting automated follow-ups after they had already answered.
View Case Study
VideoPublishing strong LinkedIn content every day was taking the founder hours—finding a real source worth writing about, drafting the post, and designing a matching carousel. On busy days nothing went out, yet the owner still wanted 100% final approval before anything was published under their name.
View Case Study
VideoThe business had 693 customers but no clear way to tell them apart. Everyone got the same emails and offers—whether they bought every week or hadn't ordered in almost a year. There was no quick way to see who the best customers were or who had stopped buying.
View Case Study
VideoThe client's analysts were pulling social media data by hand every week—logging into YouTube, Facebook, Instagram, TikTok, and other platforms one by one, exporting CSVs, and pasting numbers into reports. That took 8+ hours every week, and because each platform names and counts metrics differently, reports never matched.
View Case Study
VideoA sales team in Spain was running its entire pipeline by hand. Three people spent their days inside the CRM: checking Gmail to see who had replied, moving leads from one stage to the next, setting follow-up reminders, and fixing contact records. It was slow, error-prone, and the only way to handle more leads was to hire more people.
View Case Study
VideoBuilding local business lead lists by hand took hours. To build a single prospect list—like coffee shop owners in Miami—someone had to search Yelp, then Google Maps, then US business directories, and manually open every business's website to hunt for an email address or phone number.
View Case Study