SMSNiaga icon

SMSNiaga

Consume SMSNiaga API for SMS messaging

Actions9

Sender ID → Delete

AI-generated

Overview

This node integrates with the SMSNiaga API to manage SMS messaging and related resources such as sender IDs, groups, and account information. Specifically, the Sender ID Delete operation allows users to delete an existing sender identifier from their SMSNiaga account. This is useful for cleaning up unused or obsolete sender IDs that are no longer needed for sending SMS messages.

Typical use cases include:

  • Removing a sender ID that was created for a temporary campaign.
  • Managing and maintaining a clean list of sender IDs to avoid confusion.
  • Automating cleanup processes in workflows where sender IDs are dynamically created and deleted.

Example: A marketing automation workflow might create a sender ID for a specific campaign and then delete it once the campaign ends using this node operation.

Properties

Name Meaning
Select Sender ID Name or ID Choose the sender ID to delete from a dropdown list loaded dynamically from your SMSNiaga account, or specify the sender ID UUID directly using an expression. This identifies which sender ID will be deleted.

Output

The output is a JSON array containing the response from the SMSNiaga API after attempting to delete the specified sender ID. Typically, this will include confirmation of deletion or details about the deleted sender ID.

If an error occurs (e.g., sender ID not found), the node outputs an error object with fields such as:

  • error: Description of the error.
  • statusCode: HTTP status code returned by the API.
  • timestamp: Time when the error occurred.
  • resource: The resource type ("senderId").
  • operation: The operation attempted ("delete").

No binary data is produced by this operation.

Dependencies

  • Requires an active SMSNiaga API key credential configured in n8n.
  • The node makes authenticated HTTP requests to the SMSNiaga API endpoint at https://manage.smsniaga.com/api.
  • Proper permissions on the API key to delete sender identifiers are necessary.

Troubleshooting

  • Authentication failed: If the API token is invalid or expired, the node will throw an authentication error. Ensure your API credentials are correct and have not expired.
  • Not found error: If the specified sender ID UUID does not exist, the API returns a 404 error. Verify the sender ID exists before attempting deletion.
  • Forbidden error: Insufficient permissions on the API key can cause a 403 error. Check your API key's access rights.
  • Rate limit exceeded: Sending too many requests in a short time results in a 429 error. Implement delays or retries in your workflow.
  • Validation errors: Improperly formatted sender ID UUIDs or missing required parameters will cause validation errors (422). Use the provided dropdown or valid UUID expressions.
  • General server errors: Temporary issues on the SMSNiaga side may cause 5xx errors. Retry later or contact SMSNiaga support.

Links and References

Discussion