How to post to a Discord channel from n8n

Post to a Discord channel from n8n, step by step

About six minutes, on the free plan. You need permission to manage the Discord channel (server owner or admin).

1. Create a free PostWire account

   Open postwire.io/dashboard.html, type your email and press Create my free account. PostWire emails you a link to confirm the address; connecting accounts and publishing unlock once it is confirmed. No password and no card (free plan: 1 business, 10 posts a month, 5 AI drafts a day (about 20 a month), 2 networks per post, 3 scheduled posts at a time — every network connects free, no card).

2. Copy the channel's webhook URL

   In Discord, open the channel → Edit Channel → Integrations → Webhooks → New Webhook → Copy Webhook URL. The link looks like https://discord.com/api/webhooks/<id>/<token>; its name and avatar are what members see as the author of the posts.

3. Connect Discord

   In the dashboard open Accounts, press Connect on Discord and paste the link. There is no sign-in screen. PostWire checks that it is a Discord webhook and asks Discord whether it exists before saving it, so a link copied without its end is refused right there.

4. Copy your API key

   In the dashboard, open API & MCP and press Copy key on the API key card. It is sent as Authorization: Bearer pw_live_… (the X-API-Key header also works). Keep it server-side.

5. Install the PostWire node

   In n8n: Settings → Community nodes → Install, enter n8n-nodes-postwire (version 0.4.3 on npm on Oct 28, 2026), then add a PostWire API credential with the key and press Test, which checks the key at once. Where community nodes cannot be installed, the HTTP Request node further down does the same job.

6. Configure Post → Publish

   Networks: Discord (add Telegram, Bluesky or LinkedIn to send the news there too). Content: Smart Distribute: Write a Native Post per Network, with the Idea from the previous node (e.g. {{ $json.name }} is out: {{ $json.body }}): the Discord draft is short and friendly, in a community tone, emojis and links welcome, under 2,000 characters. To send your own words, set Content to Same Text on Every Network. Media: None, or URL / Binary File for an image or a video. Options → Dry Run checks everything without publishing.

7. Or one HTTP Request node

   POST to the REST API with header Authorization: Bearer pw_live_…. per_platform.discord.text is the message; photo_url or video_url (a public https link) goes into the message, where Discord shows its preview:

   POST https://postwire.io/api/post
   Authorization: Bearer pw_live_…
   Content-Type: application/json
   
   {
     "platforms": ["discord", "telegram"],
     "per_platform": {
       "discord": { "text": "🚀 {{ $json.name }} is out!\n\n{{ $json.highlights }}\n\nRelease notes: {{ $json.html_url }}" },
       "telegram": { "text": "{{ $json.name }} is out.\n\n{{ $json.highlights }}\n\n{{ $json.html_url }}" }
     },
     "idempotency_key": "release-{{ $json.id }}"
   }

8. Read the result, or schedule it

   The result lists Discord with ok and the id of the message; if Discord refuses it, the result carries what happened and the fix. To publish later, use Post → Schedule with When: At a Specific Time (up to 365 days ahead) or In the Next Free Queue Slot (or POST /api/schedule with run_at). A scheduled post is sent by PostWire's servers at its time, whether or not n8n is running then.

With a GitHub or RSS trigger, put the release id or the item's guid in Options → Idempotency Key (or idempotency_key): PostWire refuses a second post with the same key for 24 hours, so a retried execution announces once. A whole workflow, from the trigger to the post, is laid out in n8n social media automation.