Publish scheduled posts to LinkedIn or X from a Google Sheet queue
Write or generate posts in a sheet with a date and time each. Your assistant sets up an automation that publishes them when they're due and marks each row as posted.
- When
- Every 15 minutes
- Uses
- Google Sheets, LinkedIn
- 09:00✓ Post queue → LinkedIn · SucceededLast run09:00 · 1 posted
Can ChatGPT or Claude post to LinkedIn or X on a schedule?
An assistant can write posts, but it can't publish them at 9:00 next Tuesday. With ClickRuntime connected, the assistant sets up an automation that reads a queue in Google Sheets on a schedule and publishes each due post through the LinkedIn or X API with your connected account, then marks the row as posted.
Why the assistant can’t do this on its own
- Publishing at a set time needs something running at that time. A chat isn't.
- Posting needs a lasting sign-in to LinkedIn or X. ClickRuntime keeps the OAuth connection and refreshes it.
- A queue needs memory of what's been posted. The sheet's status column and the automation's state make sure each post goes out once.
Set it up from your AI assistant
The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.
- Step 1Connect ClickRuntime to your assistantAdd ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
- Step 2Paste the promptStart a new chat and paste: “Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.” Change the details (times, channels, addresses) to yours.
- Step 3Read the draftThe assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
- Step 4Connect accounts and save keysThe assistant asks you to connect Google (and pick the Post queue sheet) and to add LinkedIn as an app with its own OAuth details in the ClickRuntime dashboard, then sign in with the account to post as. For X, the same with an X developer app that has write access.
- Step 5Test itThe assistant adds a test row due now with text you approve, runs the automation once, and shows you the post link written back to the sheet. You can delete the test post afterwards.
- Step 6Turn it onThe assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
- Step 7Check it in the ClickRuntime dashboardEach run shows how many due posts it found and published. Runs that find nothing due are quick and aren't counted toward your monthly runs. Failures, such as an expired sign-in, show on the run with the error and send you an email.
“Create a ClickRuntime automation: every 15 minutes, read my Post queue sheet (columns: When, Text, Status). Publish each row whose When has passed and whose Status is empty to my LinkedIn profile, then set Status to the post link.”
Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.
What the assistant writes
A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.
- Times in the When column are ISO dates with a timezone, such as 2026-11-18T09:00+01:00.
- Each row is remembered in state as soon as it's posted, so a failure while writing back to the sheet doesn't post twice.
- At most five posts go out per run, so a backlog doesn't flood your feed.
- LinkedIn's Posts API is versioned; the assistant checks the current version header against LinkedIn's docs when it builds this.
A schedule, not a trigger link
Use a schedule. Every 15 minutes means posts go out within 15 minutes of their time; every 5 minutes is the shortest interval.
To publish the moment a row is approved, use a trigger link called from a button or a Sheets script instead.
Limits
- Each network's own API rules apply: X API access depends on your X developer plan, and LinkedIn company pages need the right page role and app permissions.
- Images and video need extra upload calls; the example posts text only.
- Posting happens through your own OAuth app for each network, added in the ClickRuntime dashboard.
Troubleshooting
LinkedIn returns 403.
The app lacks the permission to post as that member or page, or the sign-in expired. Reconnect the account in the ClickRuntime dashboard and check the app's products in LinkedIn's developer portal.
Posts went out at the wrong time.
The When column has no timezone, so it was read as UTC. Add the offset, or ask the assistant to read times in your timezone.
X says the request is not permitted.
Your X app needs read and write access, and the account must be reconnected after changing it.
What you can add next
The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.
- Built-in AI
Draft next week's posts with AI into the queue for you to approve
“Add to my post queue automation: every Friday, write five draft posts about our product updates into the queue with Status “draft”, and only publish rows I set to “ready”.”
- Any app or API
Cross-post the same row to X with a shorter version
“Change my post queue automation so each row is also posted to X, shortening the text to fit if needed.”
- Built-in AI
Rewrite each post for the network: longer for LinkedIn, shorter for X
“Change my post queue automation so it adapts the text per network: keep LinkedIn as written, and write a shorter version for X.”
- Trigger links
Turn each new blog post into a queued social post
“Add a trigger link to my post queue automation: when our CMS publishes a blog post, add a row with a short post and the link, due tomorrow at 9:00.”
- Memory between runs
Never post the same link twice within 30 days
“Change my post queue automation so it remembers posted links and skips a row if the same link went out in the last 30 days.”
- Schedules
A Monday email of what's queued for the week
“Add to my post queue automation: every Monday at 8, email me the posts due this week.”
- Multi-step logic
Spread posts out so no more than two go out per day
“Change my post queue automation so it never publishes more than two posts on the same day, moving extras to the next free slot.”
Questions about scheduled social posts
Can ChatGPT post to LinkedIn automatically?
With ClickRuntime connected, ChatGPT can set up an automation that posts to LinkedIn at set times through LinkedIn's API, using an account you connect in the ClickRuntime dashboard.
Can it post to X?
Yes, through the X API with an X developer app that has write access. What you can post depends on your X API access.
Do I have to write the posts?
You can, or the built-in AI can draft them into the sheet for you to approve first. See the Extend it list.
Can it post images?
The networks' APIs support images with an extra upload step. Ask your assistant to add it; the image must be available at a public HTTPS link.
What does it cost?
One run per check that publishes something. Checks that find nothing due finish quickly and aren't counted.
Other use cases
Scheduled tasks in ChatGPT and Claude
“Create a ClickRuntime automation: every weekday at 9, fetch yesterday's orders from our Shopify store and post the total to #sales in Slack.”
See the use case →Run code every hour
“Create a ClickRuntime automation: every hour, check our public API's /health endpoint and Slack #alerts if it returns anything but 200.”
See the use case →Webhook automation
“Create a ClickRuntime automation: when someone submits our Typeform, add their answers to a message in #leads.”
See the use case →Cron jobs without a server
“Create a ClickRuntime automation: every night at 2am UTC, call POST https://api.example.com/tasks/reindex with my ADMIN_TOKEN and email me if it doesn't return 200.”
See the use case →AI agent automations
“Create a ClickRuntime automation: every morning at 8, summarize new GitHub issues labelled 'bug' on our repo and post them to #eng.”
See the use case →Monitoring and alerts
“Create a ClickRuntime automation: every 5 minutes, check https://api.example.com/health and Slack #oncall if it fails twice in a row.”
See the use case →Stateful automations
“Create a ClickRuntime automation: every hour, check this product page and email me only when the price drops below the lowest price you've seen.”
See the use case →AI triage and summaries
“Create a ClickRuntime automation: every 15 minutes, label new support emails as billing, bug or other and post billing ones to #billing.”
See the use case →Website change alerts
“Create a ClickRuntime automation: every hour, check https://acme.com/pricing. Only look at the pricing table, not the whole page. When it changes, email me a short summary of what changed. Don't email me when nothing changed.”
See the use case →Price drop alerts
“Create a ClickRuntime automation: every 2 hours, check the price on https://shop.example.com/products/monitor-27. Email me when it drops below $280. Tell me only once per drop, and include the lowest price seen so far.”
See the use case →Uptime checks
“Create a ClickRuntime automation: every 5 minutes, check https://app.example.com/health. It's down if the status isn't 200, it takes longer than 5 seconds, or the body doesn't contain "ok". After 2 failures in a row post to #ops in Slack, and post again when it's back up with how long it was down.”
See the use case →RSS feed alerts
“Create a ClickRuntime automation: every 30 minutes, check https://www.postgresql.org/news.rss. Post each new item to #eng in Slack with its title, link and a one-line summary. Never post the same item twice. On the first run, don't post old items.”
See the use case →Job post alerts
“Create a ClickRuntime automation: every 2 hours, check the Greenhouse job boards for the companies acme and betaco. Email me new jobs that are product design roles open to remote work in Europe. Include title, location and link. Never send the same job twice.”
See the use case →Brand mention alerts
“Create a ClickRuntime automation: every 30 minutes, search Reddit and Hacker News for "Acme CRM". Post each new mention to #mentions in Slack with the title, link and a label: question, complaint, praise or other. Never post the same thread twice.”
See the use case →Daily Slack message
“Create a ClickRuntime automation: every weekday at 9:00 Europe/Berlin, post to #team in Slack: a good-morning line, the number of open issues labelled Bug in our Linear team ENG, and the 3 oldest ones with links.”
See the use case →Daily news digest
“Create a ClickRuntime automation: every day at 7:30 Europe/London, collect new items from these feeds: <feed URLs>. Pick the 5 most important for someone following AI policy in the EU, and email me a digest with a two-sentence summary and link for each. Don't include anything I was sent before.”
See the use case →Weekly metrics to Google Sheets
“Create a ClickRuntime automation: every Monday at 7:00 America/New_York, add a row to the KPIs tab of my sheet “Company metrics” with the week start date, last week's Stripe revenue (succeeded charges minus refunds), number of new customers and number of refunds.”
See the use case →Morning briefing
“Create a ClickRuntime automation: every weekday at 7:00 Europe/Lisbon, read today's events from my work Google Calendar, get today's forecast for Lisbon, and email me a short briefing: the weather in one line, each meeting with time and who's in it, what I should prepare, and my free blocks of 30 minutes or more.”
See the use case →Slack channel summary
“Create a ClickRuntime automation: every weekday at 17:30 America/Chicago, read today's messages and thread replies in #product, and post to #product-digest a summary with three parts: decisions made, open questions, and action items with who owns them.”
See the use case →Inbox summary each morning
“Create a ClickRuntime automation: every weekday at 7:30 America/Los_Angeles, read the emails that arrived in my Gmail inbox since the last summary. Email me a summary in three groups: needs a reply, FYI, and newsletters or notifications. One line per email with the sender. Skip anything I already read.”
See the use case →Form submissions to Google Sheets
“Create a ClickRuntime automation: when someone submits my Typeform contact form, add a row to the Leads tab of my Leads spreadsheet with the date, name, email, company and message. Check the Typeform signature so only real submissions are added.”
See the use case →Form leads to your CRM
“Create a ClickRuntime automation: when my website form posts a lead (name, email, company, message), create or update the contact in HubSpot by email, set lifecycle stage to lead, and add the message as a note on the contact.”
See the use case →Handle Stripe webhooks
“Create a ClickRuntime automation: when Stripe sends checkout.session.completed, post the customer email and amount to #sales in Slack. Check the Stripe signature and handle each event only once.”
See the use case →React to GitHub events
“Create a ClickRuntime automation: when a new issue is opened in acme/app, read the title and body and add one label: bug, feature or question. Check GitHub's webhook signature.”
See the use case →Sort Gmail automatically
“Create a ClickRuntime automation: every 15 minutes, look at new messages in my Gmail inbox and add one label: Invoice, Customer, Newsletter or Needs reply. Email me straight away when a customer message sounds urgent.”
See the use case →Recurring reminders
“Create a ClickRuntime automation: on the last weekday of every month at 10:00 London time, post “Reminder: send this month's invoices” to #finance in Slack.”
See the use case →Stale pull request reminders
“Create a ClickRuntime automation: every weekday at 9:30 Berlin time, find pull requests in acme/app and acme/api that are not drafts, have been open more than 24 hours and have no review yet. Post them to #eng in Slack with the title, age, author and requested reviewers. Post nothing if there are none.”
See the use case →Sync data between apps
“Create a ClickRuntime automation: every 30 minutes, find records in my Airtable Customers table that changed since the last run, and create or update the HubSpot contact with the same email, copying name, company and plan.”
See the use case →Summarise customer feedback
“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”
See the use case →Daily standup in Slack
“Create a ClickRuntime automation for our async standup: every weekday at 9:30 Berlin time, post “Standup: what did you do yesterday, what's next, anything blocking?” in #team. At 12:00, read the replies in that thread and post a short summary in the thread, listing blockers first and who hasn't replied.”
See the use case →
Set up your first automation in ChatGPT or Claude
Free plan. No credit card.