Summary
Design and implement automated social media workflows using the existing orchestration framework. Workflows should be able to tweet, retweet, and reply on X/Twitter, and post or reply on LinkedIn — triggered from internal events such as new releases, major merged PRs, or curated announcements — with an approval step before anything goes public.
Problem
Social media posts around releases and major updates are currently done manually, are inconsistent, and often miss the window when a topic is buzzing. Automating this via the workflow framework lets the team capture every release moment and maintain a steady content cadence without per-post manual effort.
Solution
Build two workflow definitions (X/Twitter and LinkedIn) that:
- Listen for internal triggers (GitHub release event, major PR merge, or a manual "announce this" trigger)
- Draft the post content (using the LLM inference layer)
- Route for human approval before publishing
- Post/reply/retweet via the respective platform API
Workflow A — X / Twitter
Triggers
- New GitHub release published
- PR merged with label
announce or major
- Manual trigger with a topic/URL payload
Actions
- Draft a tweet (280 chars) using the release notes or PR description as context
- Optionally draft a thread (2–3 tweets) for bigger releases
- Retweet / quote-tweet a related external post if provided
- Reply to a specific tweet ID if triggered with one
Approval gate
- Post draft + preview to a private Slack/Discord channel or internal dashboard
- Require explicit approval (reaction or button click) before the tweet goes out
- If no approval within X hours, draft expires without posting
Implementation
Workflow B — LinkedIn
Triggers
- Same as X (release, major PR, manual)
- Can also trigger on blog post publication
Actions
- Draft a LinkedIn post (longer form, 1–3 paragraphs) from the same source content
- Reply to a specific LinkedIn post/comment if triggered with a post ID
Approval gate
- Same pattern as X — draft goes to approval channel before publishing
Implementation
Shared infrastructure
Acceptance criteria
Related
- Orchestration framework: tinyhumansai/openhuman orchestration layer
- Workflow builder: tinyhumansai/tinyflows
- Discord release notifications: openhuman #4841
Summary
Design and implement automated social media workflows using the existing orchestration framework. Workflows should be able to tweet, retweet, and reply on X/Twitter, and post or reply on LinkedIn — triggered from internal events such as new releases, major merged PRs, or curated announcements — with an approval step before anything goes public.
Problem
Social media posts around releases and major updates are currently done manually, are inconsistent, and often miss the window when a topic is buzzing. Automating this via the workflow framework lets the team capture every release moment and maintain a steady content cadence without per-post manual effort.
Solution
Build two workflow definitions (X/Twitter and LinkedIn) that:
Workflow A — X / Twitter
Triggers
announceormajorActions
Approval gate
Implementation
twitter_postworkflow node: takes text + optional media, posts tweet, returns tweet IDtwitter_replyworkflow node: takes tweet ID + text, posts replytwitter_retweetworkflow node: takes tweet ID, retweets or quote-tweetsWorkflow B — LinkedIn
Triggers
Actions
Approval gate
Implementation
linkedin_postworkflow node: takes text + optional URL/media, creates postlinkedin_replyworkflow node: takes post URN + text, posts commentShared infrastructure
approval_gateworkflow node that sends a draft to a configured channel and waits for a human approval signal before continuing (used by both A and B)Acceptance criteria
announce-labelled PR merge triggers the same flowRelated