# Post to Discord from n8n with an AI agent

Source: https://postgale.com/guides/n8n/discord

Yes, an n8n workflow can post to Discord through Postgale. Attach an MCP Client Tool node pointed at https://postgale.com/mcp to an n8n AI Agent node (or call the REST API from an HTTP Request node) with a Postgale API key, connect your Discord account in Postgale once, and the agent can channel messages with attachments and embeds, edits and deletes. A person can be required to approve every post, reply and message before it goes out.

## Can n8n post to Discord?

Postgale is the secure layer for AI agents on social media. MCP (Model Context Protocol) is the open standard that lets AI assistants such as Claude and Cursor use outside tools. An MCP server is what they connect to. n8n does not reach Discord on its own; with Postgale connected it gets tools for the Discord accounts you connected and nothing else.

| Task | What Postgale does |
| --- | --- |
| Publish | Text up to 2000 characters, up to 10 attachments and up to 10 rich embeds (title, description, fields, images, colors); a custom name and avatar per message; silent delivery; scheduling. |
| Edit | Change the text of a message it posted. |
| Delete | Remove a message it posted. |

## What do you need?

- A Discord server where you have the Manage Webhooks permission.
- A Postgale workspace, and a sign-in or an API key for the agent.
- Optional files on a public HTTPS URL (upload them with `upload_media`): up to 10 MB each.
- n8n, set up as below (Workflows with the HTTP Request or MCP Client Tool node).

## Step 1: connect your Discord channel

1. Create a Postgale workspace and open Dashboard → Accounts → Discord.
2. On Discord, pick the server and the channel and authorize. Discord creates a webhook for Postgale in that channel.
3. Back in Postgale the channel is listed under Connected accounts, ready to publish.
4. Connect your AI tool: add `https://postgale.com/mcp` in [ChatGPT](https://postgale.com/guides/chatgpt), [Claude](https://postgale.com/guides/claude) or [Cursor](https://postgale.com/guides/cursor) and sign in to Postgale, or create a key under Dashboard → API keys for [n8n](https://postgale.com/guides/n8n) or your own code.

An agent can also start the connection itself: the `connect_account` tool (or `GET /api/v1/connect/discord`) returns a link for the server admin to open. The agent never gets a token.

## Step 2: connect n8n to Postgale

| Use | Node | When |
| --- | --- | --- |
| Fixed steps | HTTP Request | Your workflow knows what to post (a new blog post, a product update, a form submission). Call `POST /api/v1/posts` with the content and the account ids. |
| An agent decides | MCP Client Tool attached to an AI Agent node | The model reads the input (an inbox, a brief, a trigger) and chooses among Postgale’s tools: list accounts, upload media, create or schedule posts, read and reply to comments and messages. |

## How do I set up the MCP Client Tool node?

1. In Postgale, open Dashboard → API keys, create a key and copy it (it starts with `sk_` and is shown once). Connect the social accounts the agent may use under Dashboard → Accounts.
2. Add an AI Agent node with your model, and attach an MCP Client Tool node to it.
3. In the MCP Client Tool node set the endpoint to `https://postgale.com/mcp`, the transport to HTTP streamable, and authentication to a Bearer or Header Auth credential carrying `Authorization: Bearer sk_…`.
4. Leave the tool list on “all” to start, or select only the read-only tools until you trust the workflow.
5. Give the agent a system prompt that states the account ids it may use and whether it must save drafts or may schedule.

> Ask your agent: “You manage the Northline accounts in Postgale (ids in the context). For each new blog post in the input, draft one Instagram caption with the cover image and one Threads post, save them as drafts, and reply with the Postgale post ids.”

## How do I set up the HTTP Request node?

1. In Postgale, open Dashboard → API keys, create a key and copy it (it starts with `sk_` and is shown once). Connect the social accounts the agent may use under Dashboard → Accounts.
2. In n8n create a credential of type Header Auth with name `Authorization` and value `Bearer sk_…` (your key).
3. Add an HTTP Request node: method POST, URL `https://postgale.com/api/v1/posts`, authentication Header Auth with that credential, body type JSON:

HTTP Request body (JSON):
```json
{
  "content": "{{ $json.caption }}",
  "scheduledFor": "{{ $json.publishAt }}",
  "platforms": [
    {
      "accountId": "acc_instagram",
      "platformSpecificData": {
        "mediaUrl": "{{ $json.imageUrl }}"
      }
    },
    {
      "accountId": "acc_threads"
    }
  ]
}
```

1. Get the account ids once with a GET to `https://postgale.com/api/v1/accounts` using the same credential.
2. Optional: send an `x-request-id` header built from your trigger id, so a re-run of the workflow returns the same post instead of a duplicate.
3. To know when the post is live, add a Webhook node and register its URL in Postgale (Dashboard → Webhooks); Postgale sends post.published or post.failed, signed with HMAC-SHA256.

## What can I ask the agent to do on Discord?

Check the connection first: “Which Discord accounts are connected in Postgale?” Then, in plain language:

> Ask your agent: “Post the release notes to #announcements on Discord as an embed with the version number and the screenshot attached.”

> Ask your agent: “Schedule a Discord message for Monday at 9am reminding the server about the community call.”

> Ask your agent: “Delete the Discord message we posted by mistake an hour ago.”

POST /api/v1/posts (Discord):
```json
{
  "content": "Release 2.4 is out",
  "platforms": [
    {
      "accountId": "acc_dc",
      "platformSpecificData": {
        "mediaUrl": "https://media.example.com/screenshot.png",
        "embeds": [
          {
            "title": "Changelog",
            "description": "Faster sync and dark mode.",
            "fields": [
              {
                "name": "Version",
                "value": "2.4",
                "inline": true
              }
            ],
            "image": {
              "url": "attachment://screenshot.png"
            }
          }
        ]
      }
    }
  ],
  "publishNow": true
}
```

## Which Discord rules does Postgale enforce?

- Text is limited to 2000 characters, embeds to Discord’s field limits and 6000 characters in all; a post over a limit is refused before it reaches Discord.
- Files are uploaded by Postgale within Discord’s default limits: 10 MB per file, 10 files per message.
- @everyone and @here do not ping unless the post asks for it explicitly.
- When Discord asks to slow down, Postgale waits the time Discord gives before retrying.
- If the webhook is deleted in Discord, the account is marked as needing reconnection and your webhook hears about it.

## How do I keep a person in the loop?

- Approval: tick “Hold posts from this app for approval” when you sign in, or in the Postgale dashboard require approval for the API key the agent uses (or for the whole workspace, or one account). Posts then wait as pending approval; comment replies and moderation, direct messages, WhatsApp sends and edits to live posts wait in the same queue. A person approves, edits or rejects each one in Dashboard → Approvals; the agent’s own key or sign-in cannot approve.
- Tool annotations: every Postgale tool declares whether it only reads, writes, or publishes or sends live, deletes or spends. Clients that honour annotations ask before destructive tools run.
- Audit log: every write the agent makes is recorded with the key or the connected app, the action and the time.
- Revoking: each sign-in appears under Dashboard → Connected apps and each key under Dashboard → API keys; either can be revoked at any time.

## What can’t an agent do on Discord through Postgale?

- Read messages, reply in threads or react. A webhook can only post, edit and delete its own messages.
- Read views, reactions or member counts. Webhooks get no analytics.
- Post files over 10 MB, even in boosted servers.

## Questions

### Can an n8n AI agent post to Discord?

Yes, an n8n workflow can post to Discord through Postgale. Attach an MCP Client Tool node pointed at https://postgale.com/mcp to an n8n AI Agent node (or call the REST API from an HTTP Request node) with a Postgale API key, connect your Discord account in Postgale once, and the agent can channel messages with attachments and embeds, edits and deletes. A person can be required to approve every post, reply and message before it goes out.

### Does an n8n AI agent see my Discord password or tokens?

No. The account owner signs in on Discord’s own authorization page once, and Postgale stores the resulting channel webhook encrypted. An n8n AI agent only holds a Postgale API key or sign-in, which you can revoke at any time.

### Can I approve what an n8n AI agent sends to Discord before it goes live?

Yes. Turn on approval for the API key it uses, the account or the whole workspace. Posts, replies and messages then wait in the Postgale dashboard until a person approves, edits or rejects them; an n8n AI agent’s own access cannot approve.

### Can an n8n AI agent schedule Discord posts?

Yes. Ask for a date and time; Postgale stores the post as scheduled and publishes it then, and reports the result (post.published or post.failed) on your webhook and in get_post.

## Related

- [n8n guide](https://postgale.com/guides/n8n)
- [Discord for AI agents](https://postgale.com/integrations/discord)
- [n8n and Instagram](https://postgale.com/guides/n8n/instagram)
- [n8n and Facebook](https://postgale.com/guides/n8n/facebook)