Tweet Automation System

Personal automated tweet scheduling and posting system.

Features

• Tweet Scheduling: Schedule single tweets and threads via API
• Automated Posting: Vercel cron job runs every 30 minutes to post ready tweets
• Queue Management: GitHub-based queue system for tweet storage
• Security: Authentication middleware with rate limiting
• Monitoring: Operational metrics and health monitoring

API Endpoints

• GET /api/tweets/test - System test endpoint (dev/staging only)
• GET /api/tweets/status - Queue status and system health
• POST /api/tweets/schedule - Schedule new tweets
• GET /api/tweets/metrics - Operational metrics
• GET /api/cron/tweet-scheduler - Cron job endpoint (automated)

Environment Variables

Required environment variables:

• TWEET_API_SECRET - API authentication secret
• GITHUB_TOKEN - GitHub personal access token
• GITHUB_REPO_OWNER - GitHub username
• GITHUB_REPO_NAME - Repository name for tweet queue
• TWITTER_API_KEY - Twitter OAuth 1.0a Consumer Key
• TWITTER_API_SECRET - Twitter OAuth 1.0a Consumer Secret
• TWITTER_ACCESS_TOKEN - Twitter OAuth 1.0a Access Token
• TWITTER_ACCESS_TOKEN_SECRET - Twitter OAuth 1.0a Access Token Secret
• TWITTER_CLIENT_ID - Twitter API client ID
• TWITTER_CLIENT_SECRET - Twitter API client secret
• CRON_SECRET - Vercel cron job authentication secret

Deployment

Deploy to Vercel with automatic cron job scheduling.

vercel --prod

Environment variables can be transferred from existing project using:

vercel env pull .env.production

© 2025 Personal Tweet Automation System