Actions2
- SMS Actions
Overview
This node integrates with the Netgsm API to perform SMS-related operations. Specifically, for the "SMS Status Query" operation under the "SMS" resource, it allows users to query the status of a previously sent SMS message by providing its unique job ID. This is useful in scenarios where you want to track delivery or processing status of messages sent through Netgsm.
Practical examples include:
- Checking if an SMS was successfully delivered.
- Monitoring the progress or failure of bulk SMS jobs.
- Integrating SMS status updates into automated workflows for notifications or logging.
Properties
| Name | Meaning |
|---|---|
| Jobid | The unique identifier (job ID) of the SMS message whose status you want to query. This is required to retrieve the current status of that specific SMS. |
Output
The node outputs JSON data containing the status information of the queried SMS job. The exact structure depends on the Netgsm API response but typically includes fields such as delivery status, timestamps, and any error codes or messages related to the SMS job.
If the node supports binary data output, it would generally be used for attachments or media related to SMS, but based on the provided code and operation, this node focuses on JSON status responses only.
Dependencies
- Requires an active Netgsm API key credential configured in n8n to authenticate requests.
- Network access to
https://api.netgsm.com.tris necessary. - The node uses HTTP POST requests with JSON payloads to communicate with the Netgsm API.
Troubleshooting
- Missing or invalid Jobid: The operation requires a valid job ID. Ensure the "Jobid" property is correctly set and corresponds to an existing SMS job.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Network issues: Confirm that your environment can reach the Netgsm API endpoint.
- Unexpected API responses: Check the API documentation for possible changes or rate limits that might affect the status query.