RSSを66のSNSへ: Facebook、Instagram、X、LinkedIn、Telegramほか ブログ アフィリエイト お問い合わせ
ログイン 無料で始める
Updated: 2026-11-21
PostRSS for Tabletop RPG Groups: Session Recaps and Campaigns

Short answer: a tabletop role-playing group can use PostRSS to turn the entries of its campaign blog into posts on a Discord server, Tumblr, Mastodon and Bluesky. Write each session recap, schedule notice, piece of world lore and call for players as a separate entry with a category, connect the feed and use keyword filters so that spoilers stay on the private server while the public channels receive the stories and the recruitment posts. The game master writes the entries, and the networks follow without further work.

A tabletop campaign produces a surprising amount of writing. After each session someone summarises what happened, because players forget details between weekly games. The game master writes lore about the world, the players write journals in character, and someone draws a map or a portrait. Most of this stays in a shared document that nobody outside the table ever sees. At the same time, the group wants new players when someone leaves, and a public face that shows what a game with this table feels like. The campaign blog is the bridge: the material already exists, and a feed can send it to the places where players gather. PostRSS reads the feed and posts each new entry once. This guide shows how to set it up with the options that PostRSS offers today.

The campaign blog as the source

A simple blog is enough. Any platform that publishes an RSS or Atom feed will work, including WordPress, Ghost, Blogger and many wiki and campaign-management sites. If the blog runs on WordPress, the official PostRSS plugin can build a feed for chosen categories and create the target for you, and the integrations page shows how to find the feed address on other platforms. Each entry needs a title, a short text, a link and, ideally, a picture, such as a map, a portrait of a character or a photograph of the table.

Decide who writes. In some groups the game master does everything. In others a rotating scribe writes the recap, and a player keeps a character journal. A shared blog with several authors works well, and the feed collects all of it in one list.

Plan the kinds of entry

Five kinds of entry cover most of a campaign.

  • Session recaps: what happened, in a short, readable story, with a cliffhanger.
  • Schedule notices: the date of the next session, who is playing and where or on which platform.
  • Lore and world: the history of a city, a faction, a god, a monster that the group invented.
  • Art and maps: a picture with a caption, which suits visual networks.
  • Recruitment: a call for a new player, with the system, the tone, the schedule and what the table expects.

Give every entry a category that matches its kind, and add a second category for the campaign if the group runs more than one. Categories travel in the feed, and PostRSS can use them for keyword filters and for hashtags on networks where hashtags make sense.

Where role-players gather

The tabletop community has settled in a few places, and each has its own use.

  • A Discord server is the home of most groups. It is where players talk between sessions and roll dice online. PostRSS sends posts to Discord through a webhook that you create for one channel, and it is available from the Start plan.
  • Tumblr has a long tradition of fan art, lore and character blogs. PostRSS can post to Tumblr blogs, and it is available from the Start plan.
  • Mastodon and Bluesky have active communities of game masters and players, with hashtags for systems and for looking for a group. Both are available on the Free plan as its single target.
  • Pinterest boards suit maps, handouts and miniature painting, and they are available from the Professional plan.
  • Communities on Lemmy and PieFed are supported too and can serve as a place for discussion of systems and settings.

The pricing page shows which networks each plan includes. The Free plan has one target, so a group that wants Discord, Tumblr and Mastodon together needs a plan with at least three targets.

Keep spoilers where they belong

The central design question for a game group is who may read what. A recap that is fine for the players is a spoiler for someone who may join next month, and a lore entry that reveals the villain should stay hidden from characters, and from players who prefer surprise. Use the filters of PostRSS to separate the audiences.

A source can have an include filter, an exclude filter or both. Filters search the title, the description and the categories, ignore capital letters and match parts of words, and an exclude word always wins over an include word. Items that a filter removes are not posted and do not count against your monthly allowance. A practical scheme: tag spoiler-heavy entries with a category called spoilers, send everything to the private Discord channel and give the public sources an exclude filter for that word. The public channels then receive only the safe recaps, the art and the recruitment posts. The guide to include and exclude keyword filters explains the matching rules.

Recaps that people want to read

The recap is the entry that makes a campaign visible. PostRSS can build the post from the item title, the item description, the page title or your own fixed text, in nine combinations. A title that works like a chapter heading, such as Session 12: the bridge that was not there, gives the post a hook. A fixed label in front, such as Campaign log, makes the series recognisable on a feed. Keep the first lines punchy: the post shows the start of the entry, so put the hook there and the details after the link.

Many groups find that a short recap of three or four paragraphs gets read, while a long one does not. If the story is long, split it into a short public version and a longer private one, or link to the full text.

Schedule notices and reminders

The schedule is the most practical message of all. If sessions happen every Thursday at 19:30, a reminder at noon on the day catches the players who forgot. PostRSS lets you post at exact times on chosen days in your time zone, and it also offers posting windows, both on paid plans. Create a source for the notices and send it only to the Discord channel. Because PostRSS posts each feed item once, write each reminder as its own entry, for example from a template that changes only the date and the place. The article on exact times, windows and intervals describes the options.

Finding new players

Most groups lose a player now and then, and finding a good replacement is hard. A recruitment entry on the blog, posted to Mastodon, Bluesky and a Page or board where gamers look, reaches people who are actively searching. Write it clearly: the system, the setting, the style of play, the day and time, whether the group is online or in person, the age range and what you expect from a player. Add a picture and a way to apply. Keep the entry on the blog after the position is filled, with a note, so that the link does not go to an error. Because the feed carries a new entry once, publish a fresh entry whenever you need to recruit again.

Hashtags for the hobby

Hashtags help strangers find a group on networks where tags are used. PostRSS can add your own fixed hashtags and can turn the categories of the item into hashtags. For a game group, the name of the system, a general tag for tabletop games and a tag for the style are enough. On Facebook and LinkedIn at most five hashtags in total are used, with yours first. Hashtags are not added on chat tools such as Discord. The article on automatic, custom and random hashtags explains the options.

Show the archive to newcomers

A campaign that has run for a year has dozens of recaps, and a newcomer who reads the first few understands the world faster than from any briefing. When you open a new channel, it starts empty. Set a start date for a source and turn on catch-up, and PostRSS also posts older items that were never published. Keep the limit per update low, so that the story is released at a readable pace. The guide to catching up older feed items describes the setting. Reading the story from the beginning can be a pleasant way to follow a campaign.

A sample setup

TargetFilterTimingPurpose
Private Discord channelEverything, including spoilersAs entries are publishedPlayers
Public Discord channelRecaps and art, no spoilersDaytime windowCommunity
Tumblr blogLore, art and recaps, no spoilersSteady daytime windowFans and newcomers
Mastodon and BlueskyRecaps and recruitmentDaytime windowPlayers looking for groups

A campaign week in the feed

On Thursday night the group plays. On Friday the scribe writes the recap and the game master adds a map of the place they visited. The recap is posted to the private channel at once, with its spoiler category, and the public version appears on Tumblr and Mastodon in the daytime window the next day. On Monday the game master publishes a lore entry. On Thursday at noon the reminder reaches the Discord channel. In a week the group wrote three short entries and spent no time posting.

Credit, consent and a friendly tone

A campaign blog is a shared work, and the players are the co-authors of the story. Ask each player whether they are happy to have their character, nickname and art shared publicly, and agree a simple rule for credit: artists are named, and the writer of the recap signs it. Keep real names out of public posts unless a player wants them there. Write in a warm tone that invites newcomers, and avoid in-jokes that need ten sessions of context. A public post is a shop window, and the best window for a game group is one that shows people having a good time around a table, with a clear way to join them.

Systems, settings and searchability

People search for games by system and by setting, so repeat those words in titles and categories where it feels natural. A recap titled Session 12 in a lighthouse campaign with a fantasy system is more findable than one titled Session 12. Keep the vocabulary consistent from one entry to the next. Consistency also helps the filters, because they match words in the title, the description and the categories, and a stable set of category names makes the routing rules easy to read and to change later.

Mistakes to avoid

  • Sending spoiler entries to public channels without an exclude filter.
  • Using artwork that belongs to someone else without permission or credit.
  • Expecting one entry to be posted every week. PostRSS posts each item once.
  • Revealing real names or addresses of players in a recruitment post.
  • Posting the whole archive in one day on a new channel.
  • Not reading the report after the first month.

関連記事

The bottom line

For a tabletop group, PostRSS turns a campaign blog into a living record: recaps, lore, art and recruitment are written once and reach the right channels. Use categories and an exclude filter to guard the spoilers, exact times for reminders and the report to check that everything went out. The options are on the features page, and the plans are on the pricing page.

FAQ

Can PostRSS keep spoilers off public channels?

Yes. Give spoiler entries a category and add it to the exclude filter of the public sources. An exclude word always wins over an include word.

Can I post session recaps to Discord?

Yes. PostRSS sends posts to Discord through a webhook that you create for one channel. Each item arrives as a post with its title, link and picture.

Does PostRSS post to Tumblr?

Yes. Tumblr blogs are supported from the Start plan, so fan art and lore entries can be posted there from the feed.

Can the group get a session reminder every week?

Yes, with a separate entry for each reminder. PostRSS posts each feed item once, so write each reminder as its own entry, for example from a template.

Which plan fits a small gaming group?

The Free plan lets you test one target. For Discord, Tumblr and Mastodon together you need at least three targets, which starts with Professional.

New guides, once a month

What changed in the networks, what broke, and how to fix it before it costs you reach.

We send a confirmation e-mail first. Unsubscribe any time.

私たちのチームが作るほかのツール

PostRSSを手がけるInternet Solutionsが開発。どの製品も、それぞれの形で時間を節約します。