Message → Create
AI-generatedOverview
This n8n node allows you to send messages to an IRC (Internet Relay Chat) channel. It supports joining channels (with optional keys), sending different types of messages (privmsg, notice, or emote/action), and can optionally output raw IRC traffic logs for debugging. This node is useful for automating notifications, alerts, or chat interactions in IRC communities directly from your workflows.
Practical examples:
- Sending automated deployment notifications to a team’s IRC channel.
- Broadcasting alerts from monitoring systems to IRC.
- Posting custom messages or bot responses as part of a workflow.
Properties
| Name | Type | Meaning |
|---|---|---|
| Channel Name | String | The name of the IRC channel where the message will be sent. |
| Text | String | The content of the message to send. Supports multi-line input; each line is sent. |
| Join Channel | Boolean | Whether the node should join the channel before sending the message. |
| Channel Key | String | The key/password required to join the channel (only shown if "Join Channel" is true). |
| Message Type | Options | The type of message to send: Emote (/me action), Notice, or Privmsg (standard message). |
| Output Raw Logs | Boolean | If enabled, includes raw IRC traffic logs in the output for troubleshooting purposes. |
Output
The node outputs a JSON object with the following fields:
| Field | Description |
|---|---|
| account | The IRC account used for the connection. |
| nick | The nickname used during the session. |
| sentLines | An array of all message lines that were sent to the channel. |
| timesNickWasInUse | Number of times the chosen nickname was already in use and had to be changed. |
| error | Error information if an error occurred (only present if "Continue On Fail" is enabled). |
| log | (Optional) Raw IRC traffic logs, included only if "Output Raw Logs" is enabled. |
Note: No binary data is output by this node.
Dependencies
- IRC Server Credentials: Requires valid IRC credentials (nickname, ident, realname, host, ports, etc.) configured in n8n credentials under
ircApi. - External Services: Connects to an IRC server specified in the credentials.
- n8n Configuration: Ensure the IRC credential is set up in n8n and accessible to the workflow.
Troubleshooting
Common Issues:
Missing Credentials:
Error:No credentials got returned!
Resolution: Make sure the IRC credentials (ircApi) are properly configured in n8n.Connection Errors:
Error: Various errors related to connecting to the IRC server (e.g., authentication failure, network issues).
Resolution: Check IRC server address, port, and credentials. Verify network connectivity.Nickname In Use:
Field:timesNickWasInUsegreater than 0
Resolution: The chosen nickname was already taken on the server. Consider using a unique nickname.Channel Join Failure:
Symptom: Messages not delivered if the node fails to join the channel (e.g., wrong channel key).
Resolution: Double-check the channel name and key.Message Too Long:
Behavior: Messages longer than 410 characters are split into multiple lines automatically.