Actions42
- Message Actions
- Chat Actions
- Account Actions
- Campaign Actions
- Contact Actions
- Group Actions
- OTP Actions
- SMS Actions
- Validation Actions
Overview
This node integrates with the Zender API to manage SMS messages and campaigns. Specifically, for the SMS - Delete Sent operation, it deletes a sent SMS message identified by its unique message ID. This is useful for cleaning up or managing sent message records in your SMS system.
Common scenarios include:
- Removing mistakenly sent SMS messages from the system.
- Managing storage by deleting old or irrelevant sent SMS records.
- Automating cleanup tasks after certain workflows.
Example: You have an automated workflow that sends SMS notifications and later needs to delete specific sent messages based on business logic or user requests.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique numeric ID of the SMS message to delete. |
Output
The output JSON contains the response from the Zender API after attempting to delete the sent SMS message. It typically includes status information indicating whether the deletion was successful or if there were any errors.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Zender API.
- The node uses HTTP GET requests with query parameters to interact with the Zender API endpoints.
- The base URL and API secret are obtained from the configured credentials.
Troubleshooting
Error: Invalid or missing Message ID
Ensure the "Message ID" property is provided and corresponds to an existing sent SMS message.Error: Authentication failed
Verify that the API key credential is correctly configured and has sufficient permissions.Error: Message not found
The specified message ID may not exist or might already be deleted. Confirm the ID is correct.Network or timeout errors
Check network connectivity and the availability of the Zender API service.
If the node is set to continue on fail, errors will be returned in the output JSON under an error field instead of stopping execution.
Links and References
- Zender API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding how HTTP calls work within n8n nodes