Upgrading Content Automation with Bluesky Integration

 

TL;DR: I integrated Bluesky into the content automation workflow, automating social media posts. This upgrade involved updating multiple files, including JSON configurations and Markdown templates.

The Problem

The content automation project required publishing content across multiple platforms, including Bluesky. Initially, the Bluesky integration was manual, which was inefficient and prone to errors. The goal was to automate Bluesky posts as part of the existing content automation workflow.

What I Tried First

The first approach was to use a generic API client library for Node.js to interact with the Bluesky API. However, this library didn't provide a straightforward way to handle authentication and post creation in a single step. I had to modify the library to fit the specific needs of the project.

The Implementation

The implementation involved updating several files:

content/2026/07/05/content-automation/bluesky_en.json

[
  {
    "text": "New content available on our blog!",
    "created_at": "2026-07-05T14:30:00.000Z",
    "lang": "en"
  }
]

content/2026/07/05/content-automation/medium_en.md

# The Frustrating Dance with Automation

As a full-stack developer, I've always been fascinated by the potential of automation to streamline repetitive tasks. My current project, content-automation, aims to automate the publishing of content across multiple platforms.

## The Bluesky Integration

The Bluesky integration required updating the `bluesky_en.json` file to include the new post data. I also had to modify the `metadata.json` file to reflect the changes.

### metadata.json

json
{
"pull_requests": 0,
"releases": 0,
"closed_issues": 0,
"medium_generated": true,
"substack_generated": true,
"bluesky_generated": true
}

## Key Changes

The key changes included:

*   Adding a new Bluesky post to the `bluesky_en.json` file
*   Updating the `medium_en.md` file to reflect the changes
*   Modifying the `metadata.json` file to include the Bluesky generation status

### Code Snippets

The following code snippet shows how I generated the Bluesky posts using a Node.js script:

javascript
const fs = require('fs');
const path = require('path');

const blueskyPosts = [
{
text: 'New content available on our blog!',
created_at: '2026-07-05T14:30:00.000Z',
lang: 'en',
},
];

const blueskyPostsJson = path.join(__dirname, 'bluesky_en.json');

fs.writeFileSync(blueskyPostsJson, JSON.stringify(blueskyPosts, null, 2));

## Key Takeaway

The key takeaway from this experience is the importance of modularizing the content automation workflow. By breaking down the process into smaller, manageable tasks, I was able to integrate Bluesky into the existing workflow without disrupting the entire system.

## What's Next

The next step is to automate the generation of Bluesky posts for other languages and platforms. I plan to explore using a more robust API client library for Node.js to simplify the integration process.

#vibecoding #buildinpublic #contentautomation #blueskyintegration

---

*Part of my [Build in Public](https://dev.to/zaerohell) series — sharing the real process of building SaaS projects from Playa del Carmen, México.*

*Repo: `zaerohell/content-automation` · 2026-07-06*

\#playadev #buildinpublic