Post scheduled content to Threads from a PostgreSQL content queue
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 6 nodes and runs on a schedule (every 4 hours). Along the way it connects Postgres.
How it runs
Trigger: On a schedule (every 4 hours).
- Fetch Queued Content (Postgres): run a query
- Check Content Readiness (If): checks a condition and branches into true / false
- Post Threads Container (HTTP Request): calls an HTTP API (POST)
- Publish Threads Content (HTTP Request): calls an HTTP API (POST)
- Update Publication Status (Postgres): run a query
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (4)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Postgres
n8n-nodes-base.postgres - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest
From the author
Quick overview This workflow runs every four hours to pull the next scheduled post from a PostgreSQL content queue and publish it to Threads via the Threads Graph API, then updates the database record to mark the content as published. How it works 1. Runs…