Actions6
Overview
This n8n node interacts with the Infobip SMS API, specifically for the "SMS" resource and the "Get Scheduled Messages" operation. It allows users to retrieve information about scheduled SMS message batches using a Bulk ID. This is useful for tracking or managing messages that have been scheduled but not yet sent.
Common scenarios:
- Monitoring the status of scheduled SMS campaigns.
- Auditing or reporting on pending bulk SMS sends.
- Integrating SMS scheduling insights into automated workflows.
Practical example:
A marketing team schedules a large batch of promotional SMS messages. Using this node, they can fetch details about the scheduled batch (using its Bulk ID) to confirm timing, recipients, or other metadata before the messages are dispatched.
Properties
| Name | Type | Meaning |
|---|---|---|
| Bulk ID | String | The unique identifier for the scheduled SMS batch whose details you want to retrieve. Required field. |
Output
The node outputs a JSON array where each item contains details about the scheduled SMS batch corresponding to the provided Bulk ID. The structure typically includes fields such as:
[
{
"bulkId": "string",
"sendAt": "ISO8601 timestamp",
"status": "string",
"numberOfMessages": number,
"totalSent": number,
"totalPending": number,
// ...other Infobip-specific fields
}
]
Note: The exact output fields depend on the Infobip API response for /sms/1/bulks.
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 required beyond standard n8n credential setup.
Troubleshooting
Common issues:
- Invalid Bulk ID: If the Bulk ID does not exist or is mistyped, the API will return an error or empty result.
- Authentication errors: Missing or incorrect Infobip API credentials will cause authentication failures.
- API rate limits: Excessive requests may trigger rate limiting by Infobip.
Error messages and resolutions:
"Missing required parameter 'bulkId'": Ensure the Bulk ID property is filled in and valid."401 Unauthorized": Check your Infobip API credentials in n8n."404 Not Found": The specified Bulk ID does not correspond to any scheduled batch; verify the ID.