Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
Parameter
Type
Default
Values / limits
webhookUrl
string
""
-
content
string
""
-
message
string
-
-
username
string
""
-
avatarUrl
string
""
-
embeds
array
[]
-
embeds[].title
string
""
-
embeds[].description
string
""
-
embeds[].url
string
""
-
embeds[].color
string
""
-
embeds[].timestamp
boolean
false
-
embeds[].footer
string
""
-
embeds[].footerIconUrl
string
""
-
embeds[].imageUrl
string
""
-
embeds[].thumbnailUrl
string
""
-
embeds[].authorName
string
""
-
embeds[].authorUrl
string
""
-
embeds[].authorIconUrl
string
""
-
embeds[].fields
array
[]
-
embeds[].fields[].name
string
""
-
embeds[].fields[].value
string
""
-
embeds[].fields[].inline
boolean
false
-
attachments
array
[]
-
attachments[].sourceMode
enum
"manual"
manual, node, file
attachments[].source
string
""
-
attachments[].mimeType
string
-
-
attachments[].name
string
-
-
Configuration help
webhookUrl Webhook URL
Create one in Discord: channel settings → Integrations → Webhooks.
username Override username
Overrides the Discord webhook display name for this message.
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
Send rich Discord webhook messages with plain content, file attachments, embeds, fields, images and dynamic expressions.
Usage and specifics
This node posts through a Discord webhook URL. Configure the message, name, avatar and embeds. Treat the webhook URL as a secret.
Technical type :
discord. Runtime :nodulz.Credentials and prerequisites
Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the credentials guide for access and rotation.
Parameters
Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.
webhookUrlstring""contentstring""messagestringusernamestring""avatarUrlstring""embedsarray[]embeds[].titlestring""embeds[].descriptionstring""embeds[].urlstring""embeds[].colorstring""embeds[].timestampbooleanfalseembeds[].footerstring""embeds[].footerIconUrlstring""embeds[].imageUrlstring""embeds[].thumbnailUrlstring""embeds[].authorNamestring""embeds[].authorUrlstring""embeds[].authorIconUrlstring""embeds[].fieldsarray[]embeds[].fields[].namestring""embeds[].fields[].valuestring""embeds[].fields[].inlinebooleanfalseattachmentsarray[]attachments[].sourceModeenum"manual"manual,node,fileattachments[].sourcestring""attachments[].mimeTypestringattachments[].namestringConfiguration help
webhookUrlWebhook URL
usernameOverride username
avatarUrlOverride avatar URL
Examples
Initial configuration
Initial catalog configuration example, to adapt before running. Keep secrets in credentials.
{ "webhookUrl": "", "content": "", "username": "", "avatarUrl": "", "embeds": [] }Verification
Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.
See also : Expressions and data, Executions, Node catalog.