Actions6
Overview
This node interacts with the Infobip SMS API to retrieve the status of scheduled SMS messages. Specifically, for the "SMS" resource and the "Get Scheduled Messages Status" operation, it fetches the current status of a batch of scheduled SMS messages using a provided Bulk ID. This is useful in scenarios where you have sent out bulk SMS campaigns and need to programmatically check their delivery or scheduling status.
Practical Example:
After scheduling a marketing campaign via SMS, you can use this node to monitor whether the messages are still pending, delivered, or failed by querying their Bulk ID.
Properties
| Name | Type | Meaning |
|---|---|---|
| Bulk ID | String | Bulk ID to fetch status of (required). |
Output
The output is a JSON object (or array) containing the status information for the specified Bulk ID. The structure directly reflects the response from the Infobip /sms/1/bulks/status endpoint. Typical fields may include:
{
"bulkId": "string",
"status": "PENDING" // or "DELIVERED", "FAILED", etc.
// ...other fields as returned by Infobip
}
- The exact fields depend on the Infobip API response.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Infobip SMS API.
- API Credentials: You must configure valid Infobip API credentials (
infobipApi) in n8n. - Environment: Ensure your n8n instance can reach the Infobip API endpoints.
Troubleshooting
- Invalid Bulk ID: If an incorrect or expired Bulk ID is provided, the node may return an error or an empty result. Double-check that the Bulk ID exists and is correct.
- Authentication Errors: If API credentials are missing or invalid, you may see errors such as "401 Unauthorized". Make sure your Infobip credentials are correctly set up in n8n.
- Network Issues: Connectivity problems between n8n and Infobip can cause timeouts or network errors. Ensure outbound HTTPS traffic to Infobip is allowed.