Auto-post platform-optimized content to X and Threads with late API and Google Sheets
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 15 nodes and runs on a schedule (cron 0 */8 * * *). Along the way it connects Google Sheets. It also calls getlate.dev over HTTP.
How it runs
Trigger: On a schedule (cron 0 */8 * * *).
- Get Topic (Google Sheets): uses Google Sheets
- Short link (Bitly): uses Bitly
- Get Img (HTTP Request): calls an HTTP API
- Rename Img (Code): runs custom JavaScript code
- Upload IMG (HTTP Request): calls getlate.dev (POST)
- Set Tweets (Edit Fields (Set)): sets 2 fields: tweet, tweet2
- Set Thread (Edit Fields (Set)): sets 1 field: tweet
- If: checks a condition and branches into true / false
- If: checks a condition and branches into true / false
- Post Twitter (HTTP Request): calls getlate.dev (POST)
…plus 2 more steps. See the full node list below.
Services it uses
HTTP calls to: getlate.dev
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 (8)
- Google Sheets
n8n-nodes-base.googleSheets - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - No Operation, do nothing
n8n-nodes-base.noOp - Bitly
n8n-nodes-base.bitly
From the author
X (Twitter) and Threads (by Meta) both have different maximum character lengths. Different X and Threads Content Auto Poster This n8n template demonstrates how to post different content optimized for X (Twitter) and Meta Threads using the Late API. You can…