Skip to content

Every 30 minutes

Add new blog posts to my Buffer queue

When a new article appears in a blog's RSS feed, a post with its title and link is added to the Buffer queue of the chosen channels, and an email confirms what was queued.

Runs
Every 30 minutes
Apps
Buffer
AI
Not needed
Access
API key

Send this to your assistant

Create a ClickRuntime automation: every 30 minutes, check the RSS feed at https://blog.example.com/feed for new articles and add a post with the title and link to my Buffer queue for LinkedIn and X, then email me what was queued.

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

Publishing an article and then remembering to share it on every channel is a two-step job, and the second step is the one that slips. Posts go out late, or only on the network the author happens to use.

This automation watches your blog's RSS feed and adds a post with the title and link to your Buffer queue for the channels you choose as soon as a new article appears. Buffer then publishes it in your normal posting slots.

You get an email each time something is queued, so you can open Buffer and tweak the wording before it goes out.

What you get out of it

  • Every article shared

    New posts reach your social channels without a manual step.

  • Uses your schedule

    Posts fill your existing Buffer slots instead of going out at random times.

  • No back-catalogue flood

    Only articles published after setup are queued.

  • Room to edit

    The email lets you adjust wording in Buffer before publishing.

  • Any RSS feed

    Works with WordPress, Ghost, Substack and other feeds.

How it works

What happens, step by step

  1. Every 30 minutes, ClickRuntime reads your blog's RSS feed.

  2. It picks out articles it has not seen before.

  3. For each, it adds a post with the title and link to the Buffer queue of each channel you chose.

  4. Buffer publishes them in your next open slots, and you get an email listing what was queued.

Before it runs live

  • Connect Buffer

What you get

RunsEvery 30 minutes
Add new blog posts to my Buffer queuetoday, 9:00Succeeded
Email · 1 blog post added to BufferQueued on LinkedIn and X: "How we cut our delivery times in half this autumn" https://blog.example.com/delivery-times Buffer will publish it in the next open slot for each channel.

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
  • Add an AI step, for example to summarize, sort or draft a reply
  • Add another app, for example also send it to Slack
  • Combine it with other Buffer 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.
add_new_blog_posts_to_my_buffer_queue.pyexample
import xml.etree.ElementTree as ET
from clickruntime import on_trigger, credentials, http, notify, state, report_fetched

FEED = "https://blog.example.com/feed"
CHANNEL_IDS = ["linkedin-channel-id", "x-channel-id"]  # from Buffer's channels query

def buffer(query, variables=None):
    resp = http.post("https://api.buffer.com", json={"query": query, "variables": variables or {}},
                     headers={"Authorization": f"Bearer {credentials.secret('BUFFER_API_KEY')}"})
    resp.raise_for_status()
    return resp.json()["data"]

@on_trigger
def run(event):
    root = ET.fromstring(http.get(FEED).content)
    items = [(i.findtext("guid") or i.findtext("link"), i.findtext("title"), i.findtext("link"))
             for i in root.iter("item")]
    seen = state.get("seen")
    if seen is None:  # first run: remember what's there, don't flood the queue
        state.set("seen", [i[0] for i in items])
        return {"queued": 0}
    new = [i for i in items if i[0] not in seen]
    report_fetched(len(new))
    for _, title, link in reversed(new):
        for ch in CHANNEL_IDS:
            buffer("mutation($input: CreatePostInput!) { createPost(input: $input) { ... on PostActionSuccess { post { id } } "
                   "... on MutationError { message } } }",
                   {"input": {"channelId": ch, "text": f"{title}\n{link}", "schedulingType": "automatic", "mode": "addToQueue"}})
    if new:
        notify.email_me(f"{len(new)} blog post{'s' if len(new) > 1 else ''} added to Buffer",
                        "\n\n".join(f"\"{t}\"\n{l}" for _, t, l in new) +
                        "\n\nBuffer will publish each in the next open slot for each channel.")
    state.set("seen", (seen + [i[0] for i in new])[-500:])
    return {"queued": len(new)}

FAQ

Common questions

Will it post my whole back catalogue on the first run?
No. The first run only records the articles already in the feed. From then on, only new articles are queued.
When do the posts go out?
They are added to the queue, so Buffer publishes them in each channel's next open posting slot, following the schedule you set in Buffer.
Can it write a different message for each network?
Yes. Ask your assistant to have AI write a short intro per channel, for example a longer one for LinkedIn and a shorter one for X.
What permissions does it need?
API key. Nothing else in your accounts is used.
Does it need AI?
No. It runs without AI, so it doesn't use your plan's AI allowance.
How many runs does it use?
One run each time it checks. Checks that find nothing new and stop right away aren't counted.
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 “Add new blog posts to my Buffer queue” from your assistant

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