Actions42
- Message Actions
- Chat Actions
- Account Actions
- Campaign Actions
- Contact Actions
- Group Actions
- OTP Actions
- SMS Actions
- Validation Actions
Overview
The node integrates with the Zender API to manage SMS messages and campaigns. Specifically, for the SMS - Delete Received operation, it deletes a received SMS message identified by its unique message ID. This is useful in scenarios where you want to programmatically remove SMS messages from your received inbox, such as cleaning up old or processed messages.
Practical example:
- Automatically delete received SMS messages after processing their content in a workflow to keep the inbox clean.
- Remove spam or unwanted SMS messages based on certain criteria within an automated process.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the SMS message to delete. This is a required numeric value specifying which received SMS message will be deleted. |
Output
The output is a JSON object representing the response from the Zender API after attempting to delete the specified received SMS message. It typically contains status information about the deletion request, such as success confirmation or error details.
No binary data output is involved in this operation.
Example output structure (conceptual):
{
"status": "success",
"message": "Received SMS message deleted successfully",
"id": 12345
}
Dependencies
- Requires an active connection to the Zender API via an API key credential configured in n8n.
- The node uses HTTP requests authenticated with this API key to perform operations.
- No additional external dependencies are needed beyond the configured API access.
Troubleshooting
Common issues:
- Invalid or missing Message ID: Ensure the Message ID provided exists and is correct.
- Authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Network or API endpoint issues: Check connectivity and that the base URL for the Zender API is reachable.
Common error messages:
"error": "Message not found"— The specified Message ID does not exist or is already deleted."error": "Unauthorized"— API key is invalid or expired."error": "Bad Request"— Parameters sent to the API are incorrect or incomplete.
Resolution tips:
- Double-check the Message ID input.
- Re-authenticate or update the API key credential.
- Review API documentation for correct parameter usage.
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.
Links and References
- Zender API Documentation (general reference for API endpoints and parameters)
- n8n Documentation on HTTP Request Node (for understanding how HTTP calls are made)