n8n Workflow: Post Scheduled Threads Updates from PostgreSQL Queue

Auto-publish scheduled Threads updates from your PostgreSQL queue—every 4 hours

This n8n workflow automatically checks your PostgreSQL content queue for the next scheduled post and publishes it to Threads via the Threads Graph API. After publishing, it updates the same database record to mark the content as published and stores the publish timestamp.

What this workflow does

• Schedules execution every four hours using an n8n Schedule Trigger.
• Queries PostgreSQL for the oldest record where status is scheduled, returning post_text and optional image_url.
• Stops if no queued content is found, preventing empty Threads posts.
• Creates a Threads post container using the Threads Graph API:
  • Uses IMAGE when image_url is present.
  • Uses TEXT otherwise.
• Publishes the created container through the Threads Graph API.
• Updates PostgreSQL to set status to published and stores published_at.

Use cases

• Automate a content calendar for a brand: queue posts in PostgreSQL and publish to Threads on schedule.
• SaaS operators managing social distribution: centralize drafting/scheduling in a database, then publish automatically.
• Automation engineers standardizing publishing pipelines: keep one queue and let n8n handle Threads delivery.

Technical details

• Node/stack: Schedule Trigger, IF, PostgreSQL, HTTP Request, Sticky Note.
• PostgreSQL table expectation: content_queue with columns id, post_text, image_url, status, scheduled_at, published_at.
• Threads integration: Replace YOUR_THREADS_ACCESS_TOKEN in both HTTP requests with a valid Threads access token with publish permission.
• Database logic: fetches the next oldest scheduled item, publishes, then updates status and timestamp.