LAS G Concept

Guides · LAS AutoPost

How to turn an RSS feed into scheduled social posts

By Lawal Ayo, founder of LAS G Concept · Updated October 31, 2026 · 4 min read

This guide walks through the most common way to use LAS AutoPost: you have a blog or website with an RSS feed, and you want every new article to appear on your social channels without copying and pasting. It covers connecting a channel, adding the feed, previewing what will happen, setting rules, choosing how captions are written and checking that it is healthy. It takes about fifteen minutes the first time.

Before you start

You need a LAS AutoPost account (sign-up uses a Google account, and a new account starts on the Free plan, which allows 3 destinations and 2 feeds), a website that publishes an RSS, Atom or JSON feed, and an account on at least one channel you can connect. The easiest channels to start with are Telegram, Discord, Bluesky and Mastodon, because they do not need any outside app approval.

Step 1. Connect a destination

A destination is a channel AutoPost publishes to. Open Destinations and add one:

  • Telegram: create a bot with @BotFather, add the bot as an administrator of your channel, then enter the bot token and the channel name (for example @yourchannel).
  • Discord: in the channel's Integrations settings, create a webhook and paste its URL.
  • Bluesky: create an app password in Bluesky's settings and use it with your handle. Never use your main password.
  • Mastodon: create an application in your instance's Development settings with permission to write statuses and media and read accounts, then paste the token.

Press Test connection. This uses read-only requests, such as asking Telegram who the bot is, so it never posts anything while checking. Credentials are encrypted before they are stored and are never sent back to your browser.

Step 2. Add the feed

Open Feeds and add the feed address. If you paste your website's address by mistake, AutoPost tells you the feed link it found. Before saving, use Preview first. It reads the feed and simulates the first check without saving anything, so you see exactly which posts would be created and what the text would look like for each platform.

Then decide what the first run should do. The default is next new item only: the existing back catalogue is recorded but not posted, so your channels are not flooded with old articles the moment you connect. You can instead choose to post the most recent item or the most recent few.

Step 3. Set the rules

Rules decide how much and when AutoPost posts. The useful ones are:

  • Immediate or queue. Immediate posts as soon as an item is found; queue spaces posts out.
  • Max per check. Caps how many items are posted per check; the rest wait for the next check.
  • Daily limit and minimum gap. Measured in your workspace time zone (Africa/Lagos by default).
  • Quiet hours. For example no posts from 22:00 to 06:00. The window can pass midnight.
  • Include and exclude keywords. Match whole words, and also match the article's categories. Use them to keep a feed on topic.
  • Prefix, suffix and hashtags. Fixed text added to each post, plus automatic hashtags built from the article's categories.
  • Tracked links. Optionally add UTM parameters, and use AutoPost short links so clicks can be counted.

Step 4. Choose how the caption is written

Each feed has an AI caption setting. Off uses a plain template (title, link, hashtags). Suggest asks the AI to write a caption but sends it to Drafts where you approve, edit or reject it. Auto lets the AI hook replace the summary and posts without review. If you are new, start with Suggest until you trust the voice. The AI follows the workspace's Brand Brain (voice, audience, banned words, default hashtags and call to action). Its output is checked: links that were not in the article are stripped, numbers that are not in the source are rejected, and banned words are refused. If anything fails, the template text is used, so a post is never blocked by the AI.

Step 5. Check the result

After saving, press Check now. The feed page shows the last success, the last HTTP status, how many errors in a row there have been and a stopped updating flag if the newest item is older than the limit (72 hours by default). The item history shows where each item was posted, with the job status and a link to the post. If you use short links, the Links page counts human clicks separately from bots and link-preview crawlers.

Common problems

  • Nothing was posted. Check the first-post setting (the backlog is skipped by default), quiet hours and the daily limit.
  • A destination says "Reconnect needed". The platform rejected the saved token. Reconnect it from the Destinations page; queued jobs for that destination wait instead of failing.
  • The same article appeared twice. AutoPost keys items by both the feed's identifier and the link, so this should not happen from a normal feed. If an article was edited, it is reposted only if Repost edits is on (off by default).
  • A post was cut short. Each platform has its own length limit (Telegram 4096 characters, Discord 2000, Bluesky 300, Mastodon 500). Links are never truncated; the text before them is shortened.

Next, read Plan a weekly posting schedule, or go back to the LAS AutoPost overview.


Written by Lawal Ayo. Spotted something out of date? Tell us and we will fix it. See our editorial standards.

More guides