Automating Content Generation with Node.js: A Technical Deep Dive into Handling Metadata and API Calls

 

TL;DR: This article explores the technical aspects of automating content generation using Node.js, focusing on handling metadata and making API calls. We will dive into the specific code changes and architecture decisions made to achieve this functionality.

The Problem

The problem at hand was to automate the generation of content for various platforms, including Dev.to, Medium, and Substack. The goal was to create a Node.js script that could handle metadata and make API calls to these platforms. One of the specific technical issues encountered was dealing with hydration errors in Sentry for NODE-G and reducing noise in development for NODE-H.

What I Tried First

Initially, I attempted to use a simple script that would generate content based on a set of predefined templates. However, this approach proved to be insufficient as it did not account for the varying metadata requirements of each platform. I then tried to use a more robust library that could handle metadata and API calls, but it was too complex and difficult to integrate.

The Implementation

The implementation involved creating a Node.js script that could handle metadata and make API calls to the various platforms. The script uses a combination of JavaScript and JSON files to manage metadata.

// content-automation/changelog.md
## 2026-07-08 - content-automation

### Changed
- Updated Bluesky post data in `content/2026/07/07/VS/bluesky_es.json` with new text describing a bug fix and feature implementation

The script uses the following code to generate content:

// content-automation/medium_en.md
# Debugging the Hydration Error: A Lesson in Persistence

As I reflect on my recent development experience, I'm reminded of the frustration that comes with debugging. Specifically,

The metadata is managed using JSON files:

// content/2026/07/08/VS/metadata.json
{
  "pull_requests": 2,
  "releases": 0,
  "closed_issues": 0,
  "medium_generated": true,
  "substack_generated": true
}

Key Takeaway

One of the key takeaways from this experience is the importance of handling metadata and API calls in a robust and scalable way. By using a combination of JavaScript and JSON files, we can create a flexible and maintainable system for automating content generation.

What's Next

The next step is to integrate this script with our CI/CD pipeline to automate the content generation process. This will involve creating a GitHub Actions workflow that runs the script on a schedule.

# .github/workflows/content-automation.yml
name: Content Automation

on:
  schedule:
    - cron: 0 8 * * *

jobs:
  automate-content:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Run content automation script
        run: node content-automation/script.js

By automating the content generation process, we can save time and reduce the risk of human error.

Conclusion

In conclusion, automating content generation with Node.js requires a robust and scalable approach to handling metadata and API calls. By using a combination of JavaScript and JSON files, we can create a flexible and maintainable system for automating content generation.

vibecoding #buildinpublic #nodejs #contentautomation #devto

---

Part of my Build in Public series — sharing the real process of building SaaS projects from Playa del Carmen, México.

Repo: zaerohell/content-automation · 2026-07-09

#playadev #buildinpublic