ZenderInstall

Overview

The node interacts with the Zender SMS API to perform various SMS-related operations. Specifically, for the SMS resource and Get Single operation, it retrieves a single SMS message by its ID and type (sent or received). This is useful when you want to fetch detailed information about a specific SMS message, such as its content, status, timestamps, sender/recipient details, etc.

Common scenarios include:

• Auditing or reviewing a particular SMS message.
• Fetching message details for logging or reporting.
• Integrating SMS message data into workflows for further processing or notifications.

Example: You have an SMS message ID from a previous step or external system and want to retrieve its full details to decide on next workflow actions.

Properties

Output

The output is a JSON object containing the details of the requested SMS message. The exact structure depends on the API response but typically includes fields such as:

• Message ID
• Sender and recipient phone numbers
• Message content/text
• Timestamp of sending or receiving
• Status or delivery information
• Any metadata related to the SMS message

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating with the Zender API.
• The node makes HTTP GET requests to the Zender API endpoint /get/sms.message with query parameters id (message ID) and type (sent or received).
• The base URL and API secret are obtained from the configured credentials.
• No additional environment variables are required beyond the API credential setup.

Troubleshooting

• Invalid Message ID or Type: If the provided message ID does not exist or the type does not match any message, the API may return an error or empty result. Verify the ID and type values.
• Authentication Errors: Ensure the API key credential is correctly configured and has permissions to access SMS messages.
• Network Issues: Connectivity problems can cause request failures. Check network access to the Zender API endpoint.
• API Rate Limits: Excessive requests might be throttled by the API. Implement retry logic or reduce request frequency if needed.
• Error Handling: If the node is set to continue on fail, errors will be returned in the output JSON under an error field for each failed item.

Links and References

• Zender API Documentation (general reference for API endpoints and usage)
• n8n documentation on HTTP Request Node for understanding underlying HTTP calls (conceptual)

This summary focuses solely on the static analysis of the node's execute method for the SMS resource and Get Single operation, based on the provided source code and property definitions.