Turn trending tech stories into short videos and social posts. The system finds fresh links, builds visuals and clips, and stores files for reuse. Great for content and social teams that need a steady stream of posts.

It starts on click, pulls articles from Hacker News, and loops through each item. For every link, it fetches the page, uses OpenAI to extract a summary and related topics, and checks if the topic fits your rules. It prepares prompts, improves them with Leonardo, generates images, and waits for jobs to finish. The images go to Runway and Creatomate to produce videos. Assets upload to Amazon S3, Dropbox, Google Drive, and OneDrive. Finished videos can publish to YouTube, X, Instagram, and LinkedIn in the same run.

Plan for API keys and OAuth where needed. Start with a small limit so you can verify outputs. Expect production time to drop from hours to minutes per piece. This is useful for developer tool brands, tech newsletters, and creators who want daily content without extra staff.

• Pulls trending items from Hacker News and loops through them with batch controls
• Fetches full article content and parses a structured summary with OpenAI
• Filters topics with a rule check so only relevant stories move forward
• Builds and improves image prompts with Leonardo.ai and waits for job completion
• Generates images and converts them to videos with Runway image to video
• Creates an alternate video variant with Creatomate and retrieves the final file
• Uploads assets to Amazon S3 Dropbox Google Drive and Microsoft OneDrive
• Publishes finished videos to YouTube X Instagram and LinkedIn

• Reduce manual research and production from 3 hours to 15 minutes per video
• Automate about 80% of repetitive content tasks end to end
• Handle 10 to 50 stories per run using batch and limit controls
• Connect 12 systems in one flow to keep assets and posts in sync
• Publish to four social channels in one run to grow reach
• Improve asset reuse by storing files in S3 Dropbox Drive and OneDrive

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Hacker News, OpenAI, Leonardo.ai, RunwayML, Creatomate, Amazon S3, Dropbox, Google Drive, Microsoft OneDrive, YouTube, X, Instagram and LinkedIn. See the Tools Required section above for links to create accounts with these services.
3. Open the Hacker News node and confirm the resource and filters you want. No credential is needed for public data. Set the Limit node so you process a safe number of items while testing.
4. For OpenAI nodes, double click each OpenAI node and in the Credential to connect with dropdown click Create new credential. Enter your API key from the OpenAI dashboard and save.
5. For Leonardo.ai and RunwayML, double click each HTTP Request node, choose Create new credential, and add the API key from each platform’s account settings. Keep the default headers shown in the template.
6. For Creatomate, open the Creatomate nodes, create a new credential, and paste your API key from the Creatomate dashboard. Confirm the template or render settings match your plan.
7. For Amazon S3 uploads, open the S3 node, create a new credential with your access key, secret, and region. Enter your bucket name and optional public read setting. Test with a small file first.
8. Connect storage apps: open Dropbox, Google Drive, and Microsoft OneDrive nodes. Click Create new credential and follow the OAuth prompts. Choose the target folder paths for uploads.
9. Connect social apps: open YouTube, X, Instagram, and LinkedIn nodes. Create new credentials and finish the OAuth flow. For Instagram you need an Instagram Business account connected to a Facebook Page.
10. Review the If Topic node and adjust the conditions that decide which articles pass. Update the Set and Article Prep nodes to match your preferred titles, captions, and hashtags.
11. Test the media pipeline: set the Limit node to 1, click Test workflow, and watch the Leonardo and Runway steps. The Wait nodes will pause until jobs are ready. Confirm final files appear in your storage and the video posts correctly.
12. Troubleshoot: if uploads fail, check bucket names and permissions. If a 401 error appears, refresh API keys or OAuth tokens. If only one item runs, ensure the last processing node links back to the loop as noted.