CHATBOTS

Nightly sync of pinned Discord rules into a Postgres FAQ table

Runs every night to read the pinned rules and FAQ posts across your channels, parse them into structured entries.

CategoryChatbots
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionFetch pinned messages from each channelDiscordDiscord
  • ActionParse pins into structured FAQ entriesOpenAI
  • ActionUpsert entries into Postgres knowledge basePostgreSQLPostgres
  • OutputPost sync summary to mod ops channelDiscordDiscord

What it does

Keeps the bot's grounding source fresh. Each night it walks the channels you list, reads their pinned messages, splits them into individual question-and-answer entries, and upserts those into a Postgres FAQ table. That way your answering bot always works from the latest rules without anyone re-importing content by hand.

When to use it

When moderators edit pinned rules directly in Discord and you need those edits reflected in the knowledge base that powers /ask or your auto-answer bot. This closes the gap between where mods write rules and where the bot reads them.

How it works

  1. 1A nightly schedule triggers the flow.
  2. 2The bot fetches pinned messages from each configured channel.
  3. 3An LLM call parses the raw pinned text into clean question, answer, and source-channel fields.
  4. 4The flow upserts each parsed entry into the Postgres knowledge_base table, replacing stale rows.
  5. 5A summary of inserted and updated counts is posted to the moderator ops channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DiscordCommunity channels + voice + bots.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.