Server channels
Plan Discord in the same workspace as the rest of your channels.
Discord
Give community updates the same care as social posts
Choose the server destination, prepare announcements or forum posts, attach media safely, and keep community replies in the shared inbox when permissions allow.
Discord publishing flow
Channel version
ValidatedTomorrow 09:30
Discord
Delivery state visibleForums and threads
Shape the native format before it reaches the publishing queue.
Community inbox
Keep access, delivery, and provider state visible to the team.
Plan Discord with the rest of the campaign
Start from the shared brief and Brand Soul, then give this channel the timing, copy, and creative treatment it needs.
- Keep the source idea connected to every channel version
- Review the destination and schedule before delivery
- Use one calendar for the complete campaign
Discord plan01
1Server channels
2Forums and threads
3Community inbox
Workspace state Reviewable
Publish formats that belong on Discord
BlendDuck keeps native settings where they matter and applies platform validation before the provider receives the request.
- Text and announcement messages
- Supported attachments
- Forum posts and thread replies
Supported workflow02
1Least-privilege bot permissions
2Safe mention handling
3Channel and thread validation
Workspace state Reviewable
Know what is ready, what shipped, and what needs attention
Connection grants and provider responses stay separate from optimistic UI, so the team can act on the exact missing permission or failed target.
- Message and thread URLs
- Read-history readiness
- Inbox delivery state
Operational evidence03
1Connection checked
2Content validated
3Delivery recorded
Workspace state Reviewable