Automated Social Posts from GitHub README/CHANGELOG Updates - n8n Workflow

• Developers and development teams needing to automate release communication.
• Technical content managers seeking reliable n8n templates for dev marketing.
• Users interested in integrating core logic flow control and AI within a single n8n workflow.
• Open-source maintainers who want automatic announcement posts for code updates.

Keeping social media updated about repository changes can be time-consuming. This robust n8n workflow eliminates that overhead. It initiates via an n8n trigger whenever code is pushed to a specified GitHub branch. Crucially, the workflow includes a check to proceed only if the README.md or CHANGELOG.md files were modified, ensuring relevance.

Once triggered, the automation fetches the full contents of both documentation files. It then passes this rich context to an advanced AI model (GPT-4o-mini) configured within the n8n node structure. The AI generates tailored, platform-specific content for Twitter/X (short, linked) and LinkedIn (professional, long-form). This entire process, managed by this detailed n8n workflow, ensures immediate, high-quality, and contextually accurate social media announcements for every major update.

The entire process is controlled by a sequence of specialized n8n node configurations:

1. Start: The n8n workflow begins with the Webhook n8n trigger, configured to listen for GitHub push events.


2. Filtering: The If n8n node immediately filters the payload, executing the rest of the flow only if README.md or CHANGELOG.md were added or modified in the commit.


3. Data Fetching: Two concurrent GitHub n8n nodes retrieve the raw content of the README.md and CHANGELOG.md files from the repository identified in the webhook payload.


4. Preparation: Extract from File n8n nodes convert the binary file output into clean, usable text strings.


5. Aggregation: The Merge and Aggregate n8n nodes combine the separate README and CHANGELOG texts into a single item, ready to be processed by the language model.


6. AI Generation: The Basic LLM Chain n8n node, leveraging the OpenAI Chat Model (GPT-4o-mini) and a Structured Output Parser, processes the documentation. It follows a detailed prompt to extract key features, project names, update type (new project vs. update), and repository URLs, returning a strict JSON object containing the finalized twitter and linkedin post texts.


7. Publishing: The generated output feeds into the final publishing n8n nodes: Post tweet (Twitter/X) and LinkedIn, completing the social media automation process.

To deploy this powerful n8n workflow and start using these n8n templates, follow these setup steps:

1. Import: Copy the JSON workflow definition and paste it into your n8n instance via the 'New' menu -> 'Import from JSON'.


2. Configure Webhook: Activate the initial Webhook n8n trigger. Copy the generated test or production URL.


3. GitHub Setup: In your GitHub repository, go to Settings -> Webhooks. Add a new webhook using the URL copied from n8n. Configure it to send only the Push event, using application/json as the content type.


4. Credentials: Set up the required credentials for the following services:

1. Activation: Once all credentials and connections are established across the n8n node structure, set the n8n workflow to 'Active'.

This n8n workflow relies on several key n8n node types to manage logic, data fetching, and AI interaction:

Webhook (n8n trigger):
Function: Serves as the primary n8n trigger, initiating the n8n workflow upon receiving a POST request from GitHub.
Key Configuration: Path is set to a unique ID (e.g., 70b80513-b93c-4749-9a06-e78d4f1f2d23).
If (n8n node):
Function: Implements core logic flow control, checking if README or CHANGELOG files were involved in the push event payload. This prevents unnecessary executions.
Key Configuration: Condition uses a custom expression to iterate over commit files (added, modified, removed) for inclusion of 'changelog'.
GitHub (n8n node):
Function: Fetches the actual content of the README.md and CHANGELOG.md files, dynamically retrieving the repository name from the webhook input (={{ $json.body.repository.name }}).
Basic LLM Chain (n8n node):
Function: The central AI processing unit. It inputs the aggregated README/CHANGELOG text and applies a complex system prompt to generate highly structured social media content.
Key Configuration: Uses the OpenAI Chat Model and Structured Output Parser to ensure the output is a validated JSON object with twitter and linkedin fields.
Twitter (n8n node):
Function: Posts the generated short-form content to Twitter/X.
Key Configuration: Text is set dynamically to ={{ $json.output.twitter }}.
LinkedIn (n8n node):
Function: Posts the generated long-form content as a Person update to LinkedIn.
* Key Configuration: Text is set dynamically to ={{ $json.output.linkedin }}.