Actions6
Overview
The Infobip SMS - Search Logs operation allows users to retrieve detailed logs of SMS messages sent via the Infobip platform. This is particularly useful for tracking message delivery, troubleshooting issues, auditing communications, and generating reports on SMS activity. Common scenarios include:
- Auditing all messages sent within a specific time frame.
- Filtering logs by sender, recipient, or status (e.g., delivered, pending).
- Investigating failed or undelivered messages using bulk or message IDs.
Practical Example:
A support team wants to review all SMS messages sent to a particular customer in the last week to verify delivery and troubleshoot any issues.
Properties
| Name | Type | Meaning |
|---|---|---|
| Bulk IDs | String | Comma-separated list of bulk IDs to filter logs for specific message batches. |
| Message IDs | String | Comma-separated list of individual message IDs to retrieve their logs. |
| Advanced Log Search Options | Collection | Additional filters for log search (see below for sub-properties). |
Advanced Log Search Options (Collection):
| Name | Type | Meaning |
|---|---|---|
| From | String | Sender ID (alphanumeric or numeric) to filter logs by sender. |
| To | String | Destination address (recipient phone number) to filter logs. |
| Status | Options | Filter by message status: ACCEPTED, DELIVERED, EXPIRED, PENDING, REJECTED, UNDELIVERABLE, Any |
| Sent Since | DateTime | Lower limit for sent date/time to filter logs. |
| Sent Until | DateTime | Upper limit for sent date/time to filter logs. |
| Limit | Number | Maximum number of results to return (minimum value: 1, default: 50). |
| Mobile Country Code | String | Filter by mobile country code (MCC). |
| Mobile Network Code | String | Filter by mobile network code (MNC). |
Output
The node returns an array of log entries in the json field. Each entry represents an SMS log record as returned by the Infobip API. The structure typically includes fields such as:
{
"bulkId": "string",
"messageId": "string",
"to": "string",
"from": "string",
"sentAt": "string (ISO8601 datetime)",
"doneAt": "string (ISO8601 datetime)",
"status": {
"groupName": "string",
"id": int,
"name": "string",
"description": "string"
},
"smsCount": int,
"price": {
"pricePerMessage": "string",
"currency": "string"
},
...
}
Note: The exact fields depend on the Infobip API response for
/sms/1/logs.
Dependencies
- External Service: Requires access to the Infobip SMS API.
- Credentials: An Infobip API key must be configured in n8n under the credential type
infobipApi. - Environment: No special environment variables are required beyond standard n8n configuration.
Troubleshooting
Common Issues:
- Invalid Credentials: If the Infobip API key is missing or incorrect, authentication errors will occur.
- Empty Results: If filters are too restrictive (e.g., wrong IDs, dates), no logs may be returned.
- API Rate Limits: Excessive requests may trigger rate limiting from Infobip.
Error Messages & Resolutions:
"Authentication failed": Check your Infobip API credentials in n8n."Invalid parameter": Ensure that Bulk IDs and Message IDs are correctly formatted (comma-separated strings)."Request failed with status code 400/401/403": Review your input parameters and permissions.