How estimateflake2/red-m-linkedin-post works
This is a one-file automation app that creates and optionally publishes a weekly #redMonday LinkedIn post. Its main workflow gathers Houston event information, selects the next future event when available, generates and saves post text, then publishes it unless run in dry-run mode. The README documents the overall workflow and fallback behavior; the source excerpt shows the HTTP integrations and post-generation logic, but omits parts of the main orchestration and saving code.
Main entry points: red_monday_bot.py CLI workflow
Components 12
Event discovery
- Houston calendar
red_monday_bot.py - redM calendar site
- Event extraction
red_monday_bot.py - Upcoming event selection
red_monday_bot.py
Post generation
- Post prompt
red_monday_bot.py - Groq generation
red_monday_bot.py - Groq API
Post delivery
- CLI workflow
red_monday_bot.py - Generated post file
- LinkedIn publishing
red_monday_bot.py
Other components
- Operator
- LinkedIn API
Connections 12
- Operator → CLI workflow: runs
README.md - CLI workflow → Houston calendar: checks calendar
README.md - Houston calendar → redM calendar site: fetches page
red_monday_bot.py - Houston calendar → Event extraction: parses events
README.md - Event extraction → Upcoming event selection: provides events
README.md - CLI workflow → Post prompt: requests post
README.md - Upcoming event selection → Post prompt: supplies next event
README.md - Post prompt → Groq generation: builds messages
red_monday_bot.py - Groq generation → Groq API: requests completion
red_monday_bot.py - Groq generation → Generated post file: saves generated text
README.md - CLI workflow → LinkedIn publishing: publishes unless dry-run
README.md - LinkedIn publishing → LinkedIn API: creates post
red_monday_bot.py