Discord Connector

Most communities are chat-first now, especially on Discord. That is great for energy, terrible for memory.

This recipe is for communities that already live in Discord but want Storyden to be the long-term brain for links, references, and "wait where did we post that?" moments.

This recipe is intended to spark a bit of the creative juices. The plugin example code is fairly simple and ripe for stealing, editing and improving! If you're a developer or have one on speed dial, you can have a custom bot for your community set up quickly!

Chat First, Memory Second

The real plugin code lives here:

• Discord connector manifest
• Discord connector implementation

The current implementation is fully usable and serves as a neat example of some Storyden plugin capabilities:

• it subscribes to EventThreadPublished
• it posts published threads into discord
• it registers discord slash commands: /latest, /save, /search
• it calls Storyden APIs through plugin-provisioned API access (manifest access)

If you want the runtime model details, start with Extending Storyden, Plugin Model, Manifest, and Security.

The Real Problem It Solves

If your community is active, this pattern solves boring but annoying problems:

• great links disappear in fast-moving channels
• the same questions get answered repeatedly
• newcomers cannot find old "golden answers"
• moderators become human search engines

You can see why this matters in The power of a community-driven knowledgebase and Links.

What Each Command Does

/latest

/latest fetches the most recent published thread and posts a short summary.

• API used: Thread List
• Code path: handleCommand -> fetchLatestThread

/save

/save scans recent messages in the channel where the command was run, finds the most recent URL, and saves it as a Storyden Link.

Current behavior in code:

1. Read recent channel messages (newest first).
2. Extract first valid URL from the latest matching message.
3. Submit URL to Link Create.
4. Return saved link details back to Discord.

• API used: Link Create
• Code path: handleSave -> findLatestChannelURL

/search

/search queries Storyden's Link index and returns matching links.

Current behavior in code:

1. Accept query string from slash command option.
2. Call Link List with q.
3. Return top link results in Discord.

• API used: Link List
• Code path: handleSearch

Event Flow: Published Threads

When a new thread is published, the plugin receives EventThreadPublished, fetches thread details, and posts to the configured Discord channel.

• Event contract: Manifest events_consumed
• RPC reference: Host to Plugin event
• API used for thread details: Thread Get
• Code path: handleThreadPublished

Plugin Contract You Actually Need

Everything here is grounded in current plugin contracts:

• event subscriptions in events_consumed
• API identity and permission requests in access
• operator-provided config fields in configuration_schema
• runtime messaging via Host-to-Plugin RPC and Plugin-to-Host RPC

This example plugin currently expects these config fields:

• discord_token
• channel_id

Source of truth: plugin manifest

Safety and Scope

• request only the API permissions you truly need in manifest access.permissions
• keep Discord token and RPC token handling aligned with plugin security guidance
• choose external mode for fast local development

Outcome

The community keeps chatting where they already are.

Storyden quietly accumulates a searchable, durable link memory in the background.

No culture change campaign required. Just a good connector.