n8n-nodes-guni

A community node for n8n that lets you send SMS and MMS via the Guni API.

Features

• Send promotional or notification SMS
• Send promotional or notification MMS (with media URL)
• Dynamic sender ID selection from your Guni account

Installation

Install from npm (self-hosted n8n):

npm install n8n-nodes-guni

Or search for Guni SMS & MMS in the n8n community nodes panel.

Credentials

To use this node you need a Guni API token.

1. Sign up for a Guni account (if you don't have one).
2. Generate an API token from your Guni dashboard.
3. In n8n, add a new Guni API credential and paste your token.

The node validates the token automatically when you save the credential.

Want to send using your business name? Set up a sender ID.

Operations

SMS

• Send SMS — Send text messages to one or multiple phone numbers.
  • Campaign type: Promotional or Notification.
  • Sender ID: Choose from your account's sender IDs.
  • Unicode support: Optionally allow Unicode characters.

MMS

• Send MMS — Send multimedia messages with a media URL.
  • Campaign type: Promotional or Notification.
  • Sender ID: Choose from your account's sender IDs.
  • On success, output includes messageId (campaign/bulk id), status, sentTo, message, media, and campaignType.

Usage

1. Add the Guni SMS & MMS node to your workflow.
2. Select the operation (Send SMS or Send MMS).
3. Choose your Sender ID.
4. Choose the Campaign Type.
5. Enter your message text (or pass it from a previous node).
6. For MMS, also provide a Media URL.
7. Provide input data with contacts:

SMS example:

{
  "contacts": ["61439554019", "61439543139"],
  "message": "Hello, this is a test SMS"
}

MMS example:

{
  "contacts": ["61439543031", "61439551969"],
  "message": "Hello, this is a test MMS",
  "media": "https://example.com/image.png"
}

8. Execute the workflow.

Compatibility

• Minimum n8n version: 1.0.0
• Tested with n8n 1.x and 2.x

Upgrading from 2.0.x

• Failed sends are real errors: API and validation failures now fail the node (with NodeApiError / NodeOperationError) instead of returning an output item with success: false. Use n8n's Continue On Fail (node settings) or an Error Workflow if you need the old "soft failure" behavior.
• Item linking: Successful outputs include pairedItem so downstream nodes and expressions resolve the correct input item.
• Authentication: The node now uses httpRequestWithAuthentication with the IAuthenticateGeneric credential pattern, aligning with n8n best practices.

Version history

• 2.2.1 — Fixed MMS output: messageId and status are populated from the API response (queueResponse.addedBulk).
• 2.2.0 — Production API URL, continueOnFail() support, contacts parameter for standalone use, sender ID lookup optimized, group: ['output'], codex category updated to Communication, n8n scanner verified.
• 2.1.0 — n8n-standard auth (httpRequestWithAuthentication), pairedItem linking, proper NodeApiError/NodeOperationError, subtitle, UX copy aligned with n8n guidelines, GitHub Actions publish with provenance.
• 2.0.x — Prior stable line.
• 1.0.2 — Initial release.

Resources

• n8n community nodes documentation
• Guni API documentation
• Guni help center

License

MIT