Discord

Pinwren posts to Discord through a channel webhook — no bot to run.

Set it upCopy Anchor Link

What a message looks likeCopy Anchor Link

Each event is one message with a short headline — New feedback: Marketing site #142 Checkout button does nothing — and an embed in Pinwren's accent colour:

• Title: project, number and title (Marketing site #142 — Checkout button does nothing), linking to the item in the dashboard.
• Description: the feedback, or for comment.created the comment.
• Fields: Kind, Status and Priority, plus Reporter and Page when known.
• Timestamp: when the event happened.

Safe with untrusted textCopy Anchor Link

• Mentions are disabled for every message (allowed_mentions: { parse: [] }), and @ is broken with a zero-width space, so @everyone in a report neither pings nor even looks like a mention.
• Markdown characters (*, _, ~, `, |, >, #, -, brackets, <, :) are backslash-escaped, so text can't format the message or fake a link.
• Long text is cut to Discord's limits (about 3,900 characters for the description).

Good to knowCopy Anchor Link

• The webhook URL is a credential: Pinwren stores it encrypted and only ever shows it masked after you save (https://discord.com/…abcd). Anyone with it can post to the channel — delete the webhook in Discord if it leaks, and paste the whole new URL to change it.
• Deliveries retry and are logged like webhooks, and switch off after three days of continuous failure. Send test event and the delivery log show the status code and an error category only, never Discord's response.
• Pinwren posts only to public addresses and doesn't follow redirects; a Discord-compatible receiver on a private network needs PINWREN_OUTBOUND_ALLOWLIST.
• comment.created includes internal notes; leave it out for channels outside your team.