Automated Social Media Content Publishing Workflow

This workflow eliminates the “log in and post” ritual by connecting your WorqHat content calendar directly to each social platform. It:

• Publishes queued posts exactly at the scheduled minute
• Keeps status, publishing history, and assets in one database
• Prevents missed posts on nights, weekends, or holidays

Everything runs autonomously once the workflow is live.

Previous State

Spreadsheet calendar → manual checks every hour → copy/paste captions → upload assets per platform → mark the row as done.

Result: missed posts, timezone errors, no audit trail.

Target State

• Scheduler runs every 15 minutes
• Picks the next record whose publish_at timestamp has arrived
• Fires HTTP requests to each connected platform
• Marks the record as Published so it never reposts
• Returns a success payload for monitoring

Zero human intervention, consistent publishing cadence.

Workflow Breakdown

1. Time Based Runs

• Purpose: Cron trigger (*/15 * * * *) that wakes the pipeline every 15 minutes.
• Reasoning: Captures any post whose publish_at is now or slightly overdue; adjust cadence as needed.

2. Query Data

• Collection: Social_Media_Posts
• Filter: status == "Scheduled" AND publish_at <= NOW
• Limit: 1 (keeps the run linear and avoids bulk posting)
• Sort: Ascending on publish_at so the oldest overdue record goes first.
• Outcome: Returns either a single record (work to do) or [] (no work this cycle).

3. HTTP Request (per platform)

• Method: POST
• Example endpoint: https://api.twitter.com/2/tweets
• Headers: Authorization: Bearer {{env.TWITTER_API_KEY}}, Content-Type: application/json
• Body:

• Variations: Duplicate this node for LinkedIn, Instagram Graph API, Facebook Pages, Threads/Mastodon, etc. If a platform requires media IDs, upload first and inject the ID into the payload.

4. Update Data

• Selector: _id == {{nodes.query_data.output.records[0]._id}}
• Fields: status = "Published" (plus optional published_at, platform_response, error_message)
• Purpose: Ensures the same post is never picked again.

5. Return State

• Success payload:

• No-work scenario: swap the message for "No scheduled posts due." to keep logs clear.

Outcomes

• Guaranteed on-time publishing across every connected platform
• Central ledger of drafts → scheduled → published with zero guesswork
• Reusable pattern for launches, evergreen queues, or regional calendars
• Operators focus on content quality instead of calendar babysitting

Recommended Extensions

• Add a preview email or Slack message before publishing for stakeholder sign-off
• Store per-platform status (twitter_status, linkedin_status) plus retry counters
• Log raw API responses for analytics/audits
• Chain a follow-up workflow that fetches engagement metrics and updates the same record

Next Steps

• Create / verify the Social_Media_Posts collection with post_content, image_url, publish_at, status.
• Load upcoming campaigns into the collection.
• Configure HTTP Request nodes for each platform with the right auth tokens.
• Turn on the workflow and monitor the Return State output.

👉 Install this template in WorqHat and keep your social feeds on schedule 24/7.