Pipedream Discord → n8n

10 Pipedream Discord actions and 2 event sources, and the n8n nodes they become. Converted nodes keep your configured values; expressions like {{steps.x.$return_value}} are rewritten to n8n expressions. Pipedream app slugs: discorddiscord_botdiscord_webhook.

Actions

Pipedream action	n8n	Fit	Notes
discord-send-message	Discord sendLegacy	Check output	Do not emit `resource` (hidden in webhook mode; router falls back to 'webhook'). `channel` is implied by the webhook URL in the credential. n8n sendLegacy has no thread_id option; workaround (unverified): append `?thread_id=<id>` to the credential's…
discord-send-message-advanced	Discord sendLegacy	Check output	PD with includeSentViaPipedream pushed an extra white embed with the Pipedream link; drop it. Webhook mode limitations as in discord-send-message (no thread_id).
discord-send-message-with-file	Discord sendLegacy	Check output	n8n uploads via multipart payload_json + files[i]; filename comes from the binary's fileName.
discord_bot-send-message	Discord message → send	Check output	threadID/username/avatarURL are sent by PD in the bot create-message body but Discord ignores them for bot messages (webhook-only fields) => effectively no-ops; to post into a thread with n8n put the thread id in channelId. includeSentViaPipedream appended…
discord_bot-send-message-with-file	Discord message → send	Check output	PD puts threadID/username/avatarURL into payload_json; ignored by Discord for bot messages. n8n builds multipart payload_json + files[i] like PD.
discord_bot-add-role	Discord member → roleAdd	Direct	Both call PUT /guilds/{guild}/members/{user}/roles/{role}. n8n `role` is a multiOptions array (loadOptions getRoles) — a raw role id string inside the array is accepted.
discord_bot-create-guild-channel	Discord channel → create	Check output	rolePermissions/memberPermissions (permission_overwrites) have no n8n option; if used, fall back to HTTP Request (POST https://discord.com/api/v10/guilds/{guildId}/channels, authentication predefinedCredentialType, nodeCredentialType discordBotApi, jsonBody…
discord_webhook-send-message	Discord sendLegacy	Direct	Same API call (POST webhook URL, JSON {content, username, avatar_url}). threadID (?thread_id query) not supported by n8n sendLegacy; workaround: append ?thread_id=<id> to the credential webhookUri (unverified) or HTTP Request. PD stringified non-string…
discord_webhook-send-message-advanced	Discord sendLegacy	Check output	See discord_webhook-send-message for threadID workaround.
discord_webhook-send-message-with-file	Discord sendLegacy	Check output	PD sent multipart with field `file`; n8n sends payload_json + files[0] (both accepted by Discord).

Triggers (event sources)

Pipedream trigger	n8n	Fit	Notes
discord-new-message	Schedule Trigger + polling	Partial	n8n has no Discord trigger node (verified: no Trigger under nodes/Discord). Recommend Schedule Trigger + Discord node (bot credential) resource 'message', operation 'getAll' on each channel, then dedupe by message id (e.g. Remove Duplicates node,…
discord_bot-new-message-in-channel	Schedule Trigger + polling	Partial	No n8n Discord trigger exists. Recommend Schedule Trigger (interval = PD timer) + Discord node (botToken) resource 'message', operation 'getAll' with guildId/channelId per channel, + Remove Duplicates node on message id; filter author.bot / bot id when…

Credentials

Create a Discord credential in n8n (type discordWebhookApi). Converted nodes reference it by name, so n8n links it on import when the names match. Pipedream connected accounts can't be exported and are deleted by April 30, 2027.

What "Fit" means

Direct: same operation, same inputs. Check output: the n8n node returns a different JSON shape, so later steps that read its result need a look. Partial: some options have no n8n equivalent. Mappings verified on 2026-10-13 against the Pipedream registry and n8n source.

Questions

Does n8n have a Discord node?+

Yes. 10 of the 10 Pipedream Discord actions listed here map to a native n8n node.

Will my Pipedream Discord connection move to n8n?+

No. Pipedream exports only an account ID, never the token, and deletes connected accounts by April 30, 2027. Create a Discord credential in n8n (type discordWebhookApi) and select it on the converted nodes.

Are Pipedream Discord triggers supported in n8n?+

n8n has no trigger node for these Discord events. Converted workflows use a Schedule Trigger that polls the API, or a Webhook node registered in Discord.

What happens to code steps that call the Discord API?+

Code steps keep working through a compatibility layer, and tokens read via this.<app>.$auth move to a secrets block in the Code node. Steps that use an npm SDK are rewritten to plain HTTP calls so they run on n8n Cloud.

Other apps

Airtable Asana Calendly ClickUp Dropbox Email (SMTP)GitHub Gmail Google Calendar Google Drive Google Gemini Google Sheets All apps →