Gemini + Google Sheets: fresh X posts, no repeats
Posting on X sounds simple until you’re doing it every day. You reuse a line by accident, forget what you already posted, or you spend your “creative” time rewriting the same idea in slightly different words.
This Gemini X posts automation hits marketing managers first because consistency is the job. Founders and agency operators feel it too, because missed posts quietly cost attention and leads.
This workflow creates fresh posts every couple of hours, mixes in promos from Google Sheets, and logs everything so duplicates don’t slip through. You’ll see what it does, what you need, and how it behaves in the real world.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Gemini + Google Sheets: fresh X posts, no repeats
flowchart LR
subgraph sg0["Scheduled Run Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Scheduled Run Trigger", pos: "b", h: 48 }
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Delay Jitter Script"]
n2["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Select Tweet Template"]
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "Ad or Template Check", pos: "b", h: 48 }
n4@{ icon: "mdi:robot", form: "rounded", label: "Compose Promo Tweet", pos: "b", h: 48 }
n5@{ icon: "mdi:robot", form: "rounded", label: "Compose Standard Tweet", pos: "b", h: 48 }
n6@{ icon: "mdi:brain", form: "rounded", label: "Gemini Chat Model", pos: "b", h: 48 }
n7@{ icon: "mdi:database", form: "rounded", label: "Retrieve Promo Sheet", pos: "b", h: 48 }
n8@{ icon: "mdi:database", form: "rounded", label: "Update Promo Log", pos: "b", h: 48 }
n9@{ icon: "mdi:database", form: "rounded", label: "Fetch Tweet Log", pos: "b", h: 48 }
n10@{ icon: "mdi:database", form: "rounded", label: "Append Tweet Log", pos: "b", h: 48 }
n11@{ icon: "mdi:swap-vertical", form: "rounded", label: "Map Tweet Text", pos: "b", h: 48 }
n12["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/x.dark.svg' width='40' height='40' /></div><br/>Publish Tweet Post"]
n3 --> n4
n3 --> n5
n2 --> n3
n11 --> n12
n5 --> n11
n10 -.-> n5
n8 -.-> n4
n9 -.-> n5
n7 -.-> n4
n1 --> n2
n0 --> n1
n4 --> n11
n6 -.-> n5
n6 -.-> n4
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n4,n5 ai
class n6 aiModel
class n3 decision
class n7,n8,n9,n10 database
class n1,n2 code
class n1 disabled
classDef customIcon fill:none,stroke:none
class n1,n2,n12 customIcon
The Problem: Staying Consistent Without Posting the Same Thing
When you post on X manually, the hardest part is not writing one good tweet. It’s writing the 40th one. Ideas start to blur, you lean on familiar phrases, and suddenly you’ve posted the same hook twice in two weeks. Then there’s promotion. You want to sell, but you also don’t want your feed to become a billboard. So you “do it later,” and later becomes never. Meanwhile, there’s no reliable history unless someone keeps a log (and honestly, nobody does that for long).
It adds up fast. Here’s where it breaks down in day-to-day work.
- You end up spending about 30 minutes a day just deciding what to post, even before writing.
- Old tweets get recycled accidentally, which makes your account feel stale to repeat viewers.
- Promos are inconsistent because “pull a promo, write it, post it” is a surprising amount of friction.
- Without a history log, it’s hard to improve anything because you can’t see patterns in what you shipped.
The Solution: Automated X Posting With Rotation + Logging
This n8n workflow runs on a schedule (every 2 hours) and creates a new post for X automatically. First, it adds a little timing “jitter” so your posts don’t look like they’re stamped out by a machine. Then it selects a proven content template and decides which path to take: a normal value post most of the time, or a promo post some of the time pulled from your Google Sheet. Gemini drafts the tweet text, n8n maps it into the final format, and X publishes it. After publishing, the workflow appends the tweet to your “past tweets” sheet so the next runs can avoid repeating ideas.
It starts with a scheduled trigger. Google Sheets provides promo inventory and stores your tweet history. Gemini does the writing, and n8n handles the logic so you keep the right balance of content and promotion.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you want to post every 2 hours, which is 12 posts a day. Manually, even a “quick” cycle of pick an angle (5 minutes), write and edit (10 minutes), and make sure it’s not a duplicate (5 minutes) is about 20 minutes per post. That’s roughly 4 hours a day. With this workflow, you spend maybe 15 minutes once to update your promo sheet and tweak templates, then each run is automatic (plus normal AI processing time in the background). Most teams get several hours back every week, and the posting streak stops being fragile.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets to store promos and past tweets
- X (Formerly Twitter) to publish tweets via OAuth
- Gemini API key (get it from Google AI Studio)
Skill level: Intermediate. You’ll connect accounts, confirm sheet columns, and tweak one or two text prompts.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A schedule kicks it off. n8n runs every 2 hours, and a small delay jitter can be added so posts don’t always land at the exact same minute.
The workflow decides what kind of post to create. A quick check routes the run into a standard “value tweet” path most of the time, or into a promo path when it’s time to sell.
Gemini drafts the tweet using templates. For standard tweets, it selects from proven structures like Hook–List–Takeaway, 80/20, or a contrast post. For promos, it pulls a row from the Google Sheets “promo” tab, then writes a post around that offer while keeping your tone consistent.
X publishes and Google Sheets records it. The tweet text is mapped into the final field, posted to X, then appended to the “posts” tab (your tweet history) so future runs can avoid duplicates. Promos also update “last_posted” so the sheet rotates instead of hammering the same offer.
You can easily modify the post mix (70/30) to match your launch weeks or quieter periods. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
This workflow starts on a timed schedule and can optionally add random jitter before selecting tweet templates.
- Add and open Scheduled Run Trigger.
- Set the schedule rule to run every 2 hours (hours interval =
2). - Connect Scheduled Run Trigger to Delay Jitter Script.
- Open Delay Jitter Script and confirm the JavaScript Code includes the random delay logic in the
0–120minute window.
Step 2: Select the Tweet Template and Route Promo vs Standard
After the delay, the workflow picks a tweet template or promo selection and routes the flow accordingly.
- Open Select Tweet Template and confirm the JavaScript Code includes the templates array and the
adsflag logic. - Ensure Select Tweet Template outputs
tweetandadsas shown inreturn [{ json: { tweet, ads} }];. - Open Ad or Template Check and verify the condition checks
={{ $json.ads }}with operator true. - Confirm the routing: Select Tweet Template → Ad or Template Check → Compose Promo Tweet (true) or Compose Standard Tweet (false).
Step 3: Connect Google Sheets and Logging Tools
Promo selection and tweet history are handled through Google Sheets tools connected to the AI agents.
- Open Retrieve Promo Sheet and set Document to your spreadsheet ID (replace
[YOUR_ID]). - Set Sheet Name for Retrieve Promo Sheet to the desired sheet (currently cached as
Sheet). - Open Update Promo Log and confirm Operation is
updatewith columns mapping: name to={{ $fromAI('name', 'name of the row', 'string') }}and last_posted to={{$now.format('dd/MM/yyyy')}}. - Open Fetch Tweet Log and confirm it points to the tweet log sheet (currently
gid=0). - Open Append Tweet Log and confirm Operation is
appendwith columns Date =={{$now.format('dd/MM/yyyy')}}and PAST TWEETS =={{ /*n8n-auto-generated-fromAI-override*/ $fromAI('PAST_TWEETS', ``, 'string') }}. - Credential Required: Connect your googleSheetsOAuth2Api credentials in Retrieve Promo Sheet, Update Promo Log, Fetch Tweet Log, and Append Tweet Log.
Step 4: Set Up the AI Tweet Generators
Two AI agents generate tweets depending on whether the run is a promo or standard template.
- Open Compose Promo Tweet and confirm Text is
=You must get the list of contents from google sheets and choose one that has not recently been posted. - Open Compose Standard Tweet and confirm Text is
={{ $json.tweet }}and Has Output Parser is enabled. - Ensure Gemini Chat Model is connected as the language model for both Compose Promo Tweet and Compose Standard Tweet.
- Credential Required: Connect your googlePalmApi credentials in Gemini Chat Model.
- Verify that Retrieve Promo Sheet and Update Promo Log are connected as AI tools to Compose Promo Tweet, and Fetch Tweet Log and Append Tweet Log are connected as AI tools to Compose Standard Tweet.
Step 5: Map Tweet Output and Publish to Twitter
Both promo and standard tweet branches converge, map the final text, and publish to Twitter.
- Ensure both Compose Promo Tweet and Compose Standard Tweet connect to Map Tweet Text.
- Open Map Tweet Text and set the assignment Tweet to
={{ $json.output }}. - Open Publish Tweet Post and set Text to
={{ $json.Tweet }}. - Credential Required: Connect your twitterOAuth2Api credentials in Publish Tweet Post.
output from the AI agent, the tweet will publish as empty. Confirm the AI outputs a single plain-text tweet.Step 6: Test and Activate Your Workflow
Validate each branch and confirm tweets and logs are created correctly before enabling scheduled runs.
- Click Execute Workflow to run a manual test from Scheduled Run Trigger.
- Confirm Select Tweet Template outputs either
ads=trueor a template name intweet. - Verify a tweet is produced by either Compose Promo Tweet or Compose Standard Tweet, then mapped in Map Tweet Text.
- Check Google Sheets to ensure Update Promo Log or Append Tweet Log updated/inserted rows as expected.
- Confirm Publish Tweet Post succeeds and posts the final text.
- When satisfied, switch the workflow to Active to run on schedule.
Common Gotchas
- X (Formerly Twitter) credentials can expire or lack write permissions. If it stops posting, check the connected account in n8n credentials and re-authorize with posting access.
- If you’re using Wait-like behavior through delay jitter or you notice slow AI responses, processing times vary. Bump up the delay or add a little buffer if downstream nodes fail on empty responses.
- Gemini prompts are often too generic out of the box. Add a few “rules” for voice, banned phrases, and length early, or you’ll be manually editing posts forever.
Frequently Asked Questions
About 30 minutes if your Sheets and accounts are ready.
No. You’ll connect X and Google Sheets, then tweak a few settings and prompts.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Gemini API usage, which is usually a few cents per day at this cadence.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s one of the first things worth changing. Update the probability check in the “Ad or Template” logic (the workflow uses a random rule like “Math.random() < 0.3” for about 30% promos). Common tweaks include switching to 20% promos when you’re building trust, running 40% during a launch, and adding your own promo fields in the Google Sheets “promo” tab so the AI can mention the right product details.
Usually it’s expired OAuth or missing write access on the connected X app. Reconnect the X credential in n8n, then confirm the account can publish (not just read). Also check that your n8n instance time zone matches your expectations, because “it posted at the wrong time” often looks like “it didn’t post.”
A 2-hour schedule is only about 12 tweets a day, so it’s well within typical n8n limits.
Often, yes, because this isn’t a simple “app A to app B” zap. You have branching logic (promo vs. standard), template selection, history logging, and an AI writing step, and n8n handles that kind of flow cleanly. Self-hosting is another big deal if you post frequently, since you’re not paying per tiny action the way many tools charge. On the other hand, Zapier or Make can feel faster to click together if you only want one daily post and no logging. If you’re unsure, Talk to an automation expert and get a recommendation based on your volume.
Set this up once, and your X presence stops depending on your mood or your calendar. The workflow handles the repetition so you can focus on the messages that actually move customers.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
