Infobip

Overview

The Infobip SMS - Dequeue Received Messages operation retrieves a list of received SMS messages from the Infobip platform. This node is useful for workflows that need to process inbound SMS, such as customer support systems, automated responses, or logging incoming communications. For example, you could use this node to fetch new SMS replies from customers and trigger follow-up actions in your workflow.

Properties

Output

The output is an array of JSON objects, each representing a received SMS message. Each object typically contains fields such as:

{
  "results": [
    {
      "messageId": "string",
      "from": "string",
      "to": "string",
      "text": "string",
      "receivedAt": "string",
      // ...other Infobip-specific fields
    }
  ]
}

• The exact structure depends on the Infobip API response, but generally includes sender, recipient, message content, and timestamps.

Dependencies

• External Service: Requires access to the Infobip SMS 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 Credentials: If your API key or credentials are incorrect, the node will fail to connect to Infobip.
  • API Limits: Exceeding the allowed limit or making too many requests may result in errors or rate limiting.
  • Empty Results: If there are no new received messages, the output array will be empty.

• Error Messages:

  • "Authentication failed": Check your Infobip API credentials in n8n.
  • "Invalid parameter: limit": Ensure the Limit property is set to a positive integer (minimum value is 1).
  • "Network error": Verify network connectivity and Infobip service status.

Links and References

• Infobip SMS API Documentation
• n8n Credentials Setup Guide
• Infobip Node GitHub Repository