Discord integration
Discord is on the map, not in the product yet.
Publish, indexing, and ranking updates arrive as rich embeds in your server, edited in place as status changes.
How it works
Discord connects with a channel webhook URL and nothing else: create a webhook in your channel's integration settings, paste the URL, done. We post pipeline events as rich embeds, and because we send with wait=true, Discord returns each message's ID, which lets us edit status messages in place. A page's indexing notice starts as 'indexing' and becomes 'indexed' in the same message instead of stacking a new line in the channel.
In the loop, Discord keeps the pipeline visible for teams and communities that live there, from indie hackers to agencies running client servers. Draft-ready notices, publish confirmations, indexing status, and ranking wins land in the channels you choose, formatted with embeds and linking back to the item in SearchHandled. It is notification only by design: acting on an item happens in SearchHandled, one click from the message.
Best forTeams and communities that run on Discord and want pipeline status visible in their server without another tab to check.
Setup, step by step
- In your Discord channel, open Edit Channel, then Integrations, then Webhooks, and create a webhook.
- Copy the webhook URL.
- Paste it into SearchHandled's Discord connector.
- Pick the event types the channel should receive.
- Send the test notification to confirm the embed lands.
Best practices
Guard the webhook URL
The URL is the entire credential: anyone holding it can post to your channel. We store it encrypted and never display it after setup, and Discord lets you delete and recreate the webhook in seconds if it leaks.
One webhook per channel, split by audience
A webhook posts to its own channel, so create one per channel you want and divide event types between connections. Review notices to the editors' channel, wins to the public one is a common split.
Let status messages edit in place
Indexing updates edit the original message rather than posting again, which keeps channels readable. A message that changed state is the feature working, not a glitch in your scrollback.
Name the webhook clearly in Discord
The webhook's name and avatar in Discord's settings are what members see as the poster. Naming it SearchHandled makes the feed self-explanatory to everyone in the server.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
The webhook URL is a channel-scoped secret
No token or login protects webhook posting; possession of the URL is full permission to post to that channel, so a leaked URL means unwanted messages.
How we handle itThe URL is stored encrypted and hidden after setup, and rotation is easy: delete the webhook in Discord, create a fresh one, and paste the new URL into the connector.
discord.com/developers
No interactivity without a full bot
Webhooks can post and edit messages but cannot offer buttons that trigger actions or respond to commands, so approving a draft from inside Discord is not possible.
How we handle itEvery embed links directly to the relevant item in SearchHandled, so the action is one click away. We chose the webhook's simplicity over a bot's permissions surface deliberately.
discord.com/developers
Embed and payload limits
Discord caps messages at 10 embeds and 6,000 characters across embed content, so oversized notifications would be rejected.
How we handle itOur embeds are compact summaries with links to the full detail, sitting far below the limits by design, so payload rejections do not occur in practice.
discord.com/developers
Questions teams ask
- Why did a message in the channel change after it was posted?
Status messages edit in place. We post with wait=true, which returns the message ID, and when a page moves from indexing to indexed we update the original embed instead of posting a duplicate.
- Can we approve drafts from inside Discord?
Not directly, since webhooks have no interactive components. Each message links straight to the item in SearchHandled, where approval is one click with full context.
- What if the webhook URL gets exposed?
Delete the webhook in Discord's channel settings, which kills the URL instantly, then create a new one and paste it into the connector. Notifications resume immediately.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Discord matters moves it up the rollout.