Infobip

Work with Infobip SMS and telecoms API

Actions6

SMS Actions

Overview

The Infobip SMS - Dequeue Delivery Report operation retrieves delivery reports for sent SMS messages from the Infobip platform. This is useful for tracking the status of bulk or individual SMS messages, such as whether they were delivered, failed, or are still pending. Common scenarios include monitoring campaign effectiveness, troubleshooting message delivery issues, and maintaining compliance logs.

Practical examples:

After sending a marketing SMS campaign, use this node to fetch delivery statuses for each recipient.
Automatically check if critical notifications (e.g., OTPs, alerts) reached their intended recipients.
Integrate with CRM systems to update contact records based on SMS delivery outcomes.

Properties

Name	Type	Meaning
Bulk ID	String	The unique identifier for a batch of sent SMS messages to retrieve reports for. Use when you want to get the report for all messages in a specific bulk send.
Message ID	String	The unique identifier for an individual SMS message to retrieve its delivery report. Use when you want the status of a single message.
Limit	Number	The maximum number of results to return. Useful for paginating or restricting the size of the response. Default is 50.

Output

The output is a JSON array where each item represents a delivery report for an SMS message. Each report typically includes fields such as:

{
  "bulkId": "string",
  "messageId": "string",
  "to": "recipient_number",
  "from": "sender_id",
  "sentAt": "timestamp",
  "doneAt": "timestamp",
  "status": {
    "groupId": 3,
    "groupName": "DELIVERED",
    "id": 5,
    "name": "DELIVERED_TO_HANDSET",
    "description": "Message delivered to handset"
  },
  "error": {
    "id": 0,
    "name": "NO_ERROR",
    "description": "No error"
  }
}

Note: The actual structure may contain additional fields depending on the Infobip API response.

Dependencies

External Service: Requires access to the Infobip SMS API.
API Credentials: You must configure n8n with valid Infobip API credentials (infobipApi).
Environment: No special environment variables required beyond standard n8n credential setup.

Troubleshooting

Common Issues:

Invalid or missing Bulk ID/Message ID: If neither Bulk ID nor Message ID is provided, the API may return an error or empty result.
Authentication errors: Ensure your Infobip API credentials are correctly configured in n8n.
Limit too high/low: Setting an invalid value for Limit (e.g., less than 1) may cause errors or unexpected results.

Error Messages:

"Authentication failed": Check your Infobip API credentials.
"Invalid parameter: bulkId/messageId": Ensure you provide correct IDs as per your sent messages.
"Too many requests": You may be hitting rate limits; try reducing request frequency.