Infobip icon

Infobip

Work with Infobip SMS and telecoms API

Actions6

Overview

This node allows you to send SMS messages using the Infobip SMS API. It is designed for workflows that require automated sending of text messages, such as notifications, alerts, two-factor authentication codes, or marketing campaigns. The node supports advanced scheduling and delivery options, making it suitable for both simple and complex messaging scenarios.

Example use cases:

  • Sending appointment reminders to customers.
  • Notifying users about system events or outages.
  • Delivering promotional messages to a list of recipients.
  • Scheduling SMS campaigns to be sent at specific times or within certain time windows.

Properties

Name Type Meaning
Message string Content of the message being sent. This is the actual text that will be delivered to recipients.
From string The sender ID, which can be alphanumeric or numeric (e.g., CompanyName). This appears as the sender on the recipient's device.
To string Comma-separated destination phone numbers. Each number must include the country code but not the international dialing prefix (00/+). Example: 41793026727.
Advanced collection Advanced SMS Options, including scheduling, callbacks, transliteration, and delivery time windows.
└ Schedule Message At dateTime Date and time when the message should be sent (in browser's local time). Allows scheduling messages for future delivery.
└ Notification Callback URL string URL to receive delivery reports via webhook. Infobip will POST delivery status updates to this endpoint.
└ Additional Callback Data string Custom client data (JSON, up to 4000 characters) to be sent with the callback notification.
└ Transliteration options Script conversion for the message text. Useful for replacing unsupported characters. Options: BALTIC, CENTRAL_EUROPEAN, CYRILLIC, GREEK, NON_UNICODE, SERBIAN_CYRILLIC, TURKISH.
└ Delivery Days multiOptions Days of the week when delivery is allowed. At least one day must be selected.
└ Delivery Hours From string Start time (HH:mm, UTC) for allowed delivery window. Must be used with "Delivery Hours To" and "Delivery Days". Minimum 1 hour difference required.
└ Delivery Hours To string End time (HH:mm, UTC) for allowed delivery window. Must be used with "Delivery Hours From" and "Delivery Days". Minimum 1 hour difference required.

Output

The output is an array of JSON objects representing the response from the Infobip API for each message sent. The structure typically includes:

[
  {
    "bulkId": "string",
    "messages": [
      {
        "to": "recipient_number",
        "status": {
          "groupId": 1,
          "groupName": "PENDING",
          "id": 7,
          "name": "PENDING_ENROUTE",
          "description": "Message sent to next instance"
        },
        "messageId": "unique_message_id"
        // ...other fields depending on Infobip's API response
      }
    ]
    // ...other fields
  }
]
  • bulkId: Identifier for the batch of messages sent.
  • messages: Array containing details for each recipient, including their number, status, and messageId.
  • Other fields may be present based on Infobip's API response.

Note: No binary data is produced by this operation.

Dependencies

  • External Service: Requires an active Infobip account and access to the Infobip SMS API.
  • API Key: You must configure n8n credentials for infobipApi (API key or username/password as per your Infobip account).
  • n8n Configuration: Ensure the Infobip credential is set up in n8n under Credentials.

Troubleshooting

Common Issues:

  • Invalid Phone Numbers: If the "To" field contains incorrectly formatted numbers, the API may reject the request.
  • Missing Required Fields: Omitting required properties like "From", "To", or "Message" will result in errors.
  • Scheduling Errors: If "Delivery Hours From" and "To" are not at least 1 hour apart, or if "Delivery Days" is missing when specifying delivery hours, the API may return validation errors.
  • Authentication Errors: Incorrect or missing Infobip credentials will cause authentication failures.

Error Messages & Resolutions:

  • "401 Unauthorized": Check your Infobip API credentials in n8n.
  • "400 Bad Request": Review input parameters for missing or invalid values, especially phone number formats and required fields.
  • "Invalid delivery time window": Ensure "Delivery Hours From" and "To" are set correctly and at least 1 hour apart, and that "Delivery Days" is specified.

Links and References

Discussion