SMSNiaga icon

SMSNiaga

Consume SMSNiaga API for SMS messaging

Actions9

Sender ID → Create

AI-generated

Overview

This node integrates with the SMSNiaga API to manage SMS messaging and related resources. Specifically, for the Sender ID - Create operation, it allows users to create a new sender identifier that can be used as the "from" name or number when sending SMS messages. This is useful for businesses or services that want to brand their SMS communications with a recognizable sender name.

Common scenarios include:

  • Registering a new sender ID representing a company or service name.
  • Setting a default sender ID to be used automatically for outgoing SMS.
  • Adding descriptive information to help identify sender IDs in the system.

Practical example:
A marketing team wants to send SMS campaigns using their company name as the sender. They use this node to create a sender ID named "MyCompany" with a description "Main marketing sender" and set it as the default sender ID.

Properties

Name Meaning
Name of Sender ID Name The unique name for the sender identifier (e.g., your company name). Required for creation.
Description Optional text describing the sender ID to help identify it later.
Is Default Boolean flag indicating if this sender ID should be set as the default for SMS messages.

Output

The output is a JSON object representing the newly created sender identifier as returned by the SMSNiaga API. It typically includes fields such as the sender ID's unique identifier, name, description, default status, and metadata like creation timestamps.

If an error occurs, the output may contain an error object with details including the HTTP status code, error message, timestamp, and the resource and operation involved.

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 https://manage.smsniaga.com/api/sender_identifiers.
  • Proper network access to the SMSNiaga API endpoint is necessary.

Troubleshooting

  • Authentication failed: If the API token is invalid or expired, the node will throw an authentication error. Verify and update the API credentials.
  • Validation errors: Occur if required properties are missing or invalid (e.g., empty sender ID name). Ensure all required fields are correctly filled.
  • Rate limiting: Too many requests in a short time may cause rate limit errors. Implement delays or reduce request frequency.
  • Server errors: Temporary issues on SMSNiaga's side may result in 5xx errors. Retry after some time.
  • Bad request: Improperly formatted data or invalid parameters will cause errors. Double-check property values and formats.

When errors occur, enabling "Continue On Fail" allows processing subsequent items without stopping the workflow.

Links and References

Discussion