Skip to content

The moment it happens

Turn long text into an X thread

Paste a long piece of writing and it goes out as a numbered thread.

Runs
The moment it happens
Apps
X
AI
Yes, uses the built-in AI allowance
Access
tweet.write

Send this to your assistant

Create a ClickRuntime automation: give me a link where I can paste long text. Split it into a thread of tweets under 280 characters, numbered 1/, 2/ and so on, and post it to X.

Paste it into your assistant. It tells you what it will send or change before it runs live.

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Threads on X reach more people than single posts, but turning an essay or a launch announcement into a thread is fiddly. You split paragraphs by hand, count characters, number the posts, and then post the first and reply to yourself one by one. It takes thirty minutes, and one mistake means redoing the chain.

When you send text to the trigger link, ClickRuntime's built-in AI splits it into parts that each fit within 280 characters, keeping the sense of the original. The first post is published, and every remaining part is posted as a reply to the previous one, forming a chained thread.

Writers and founders who draft in a notes app or a document and want a one-step way to publish use it frequently. What used to be a half hour of manual posting becomes one request, whether the text is a story or a launch note.

What you get out of it

  • Long ideas reach a bigger audience

    A thread keeps readers on your content for longer and is more likely to be shared than a single post, which grows your reach from the same writing. Readers who stay through a thread are more likely to follow and reshare.

  • No character counting

    The AI keeps each part under the limit and breaks at natural points, so you avoid awkward splits in the middle of a sentence or a number. Natural breaks make a thread read better than one cut at an arbitrary character count.

  • The thread is chained correctly

    Each reply attaches to the previous post, so the sequence reads in order, instead of becoming a set of separate posts that readers have to piece together. Posts in the right order let readers follow the argument without hunting for the next part.

  • Publishing takes seconds

    Sending text to a link replaces half an hour of manual posting, so a launch thread can go out as soon as the announcement is approved. Speed matters for announcements that are only useful for a few hours.

  • Works from any tool

    Anything that can call the trigger link, such as a notes app shortcut or a form, can start a thread, so you can write wherever you prefer. That flexibility lets writers keep their usual tools and still publish on X.

How it works

What happens, step by step

  1. When you send a long piece of text to the automation's private link, it starts.

  2. AI splits the text into numbered parts that each fit within X's 280-character limit.

  3. The first part is posted on your X account.

  4. Each following part is posted as a reply to the one before, so they read as a single thread.

Before it runs live

  • Connect X
  • Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens
Turn long text into an X threadjust nowSucceeded
X · @acmeapp1/ We moved our whole billing system in a weekend. Here's what went wrong and what we'd do again. 2/ First, we froze all plan changes on Friday at 6pm...

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.
  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

  • Act only on the items that match your own rules, and skip the rest
  • Change what the AI looks for, or how it writes the result
  • Add another app, for example also send it to Slack
  • Combine it with other X steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.
thread_from_long_text.pyexample
from clickruntime import on_event, http, credentials, ai

@on_event
def handle(event):
    text = (event.json or {}).get("text", "")
    parts = ai.generate(
        "Split this text into a Twitter thread. Each part under 270 characters, keep the wording, "
        "one part per line, no numbering.\n\n" + text[:8000],
        max_output_tokens=1500,
    ).text.strip().splitlines()
    parts = [p.strip() for p in parts if p.strip()]
    auth = {"Authorization": "Bearer " + credentials.connection("x", "main")}
    previous = None
    for i, part in enumerate(parts, 1):
        tweet = {"text": f"{i}/ {part}"[:280]}
        if previous:
            tweet["reply"] = {"in_reply_to_tweet_id": previous}
        resp = http.post("https://api.x.com/2/tweets", headers=auth, json=tweet)
        resp.raise_for_status()
        previous = resp.json()["data"]["id"]
    return {"tweets": len(parts)}

FAQ

Common questions

How long can the input text be?
There is no fixed word count in the automation itself, but very long text turns into a very long thread, and X limits how many posts can be published quickly. For most uses, 500 to 1,500 words works comfortably.
Can I review the split before it is posted?
Yes. The run can email you the proposed parts for approval before anything is published. Tell your AI assistant to add that step if you want to check the break points and wording, particularly for company announcements.
Does it number the posts, like 1/7?
It can. Many people ask the AI to add numbering and a closing call to action on the last post. This is a setting in the instructions given to the AI, and you can change it before approving the automation.
What permissions does it need?
tweet.write. Nothing else in your accounts is used.
Does it need AI?
Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly AI allowance.
How many runs does it use?
One run for each event the app sends.
Can I change how it works?
Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

Set up “Turn long text into an X thread” from your assistant

Copy the prompt above, or connect your assistant first. Free plan, no credit card.