Taximail icon

Taximail

Send Email, SMS, OTP via Taximail API with AI content generation or check status/verify OTP

Overview

The node integrates with the Taximail API to perform various messaging operations including sending emails, SMS, OTP (One-Time Password) via SMS, verifying OTP codes, and checking the status of sent messages. The "Check Status" operation specifically allows users to query the delivery or processing status of a previously sent message by providing its unique Message ID.

This node is beneficial in scenarios where you need to track whether an email or SMS has been successfully delivered or processed. For example, after sending a transactional email or an OTP SMS, you can use this operation to confirm the message status before proceeding with further workflow steps.

Practical example:

  • After sending an OTP SMS to a user, use the "Check Status" operation with the returned Message ID to verify if the OTP message was delivered successfully.
  • Monitor the status of important transactional emails to ensure they reach recipients.

Properties

Name Meaning
Message ID The unique identifier of the message whose status you want to check. This ID is obtained from the response when the message was originally sent.

Output

The output JSON object includes the full response from the Taximail API regarding the message status. It contains fields such as:

  • operation: The string "check_status" indicating the performed operation.
  • message_id: The Message ID used for the status check.
  • Other fields returned by the Taximail API about the message status (e.g., delivery state, timestamps, error info).

No binary data is output by this operation.

Example output structure (simplified):

{
  "operation": "check_status",
  "message_id": "your_message_id_here",
  "status": "delivered",
  "timestamp": "2024-06-01T12:00:00Z",
  ...
}

Dependencies

  • Requires an API key credential for authenticating requests to the Taximail API.
  • The node uses HTTP requests authenticated via this API key.
  • No additional environment variables are required beyond the configured API credential.

Troubleshooting

  • Common issues:
    • Providing an invalid or expired Message ID will likely result in an error or no meaningful status data.
    • Network or authentication failures may cause the request to fail.
  • Error messages:
    • If the operation is unknown or unsupported, the node throws an "Unknown operation" error.
    • If the API request fails, it throws an "Operation failed" error with details.
  • Resolution tips:
    • Ensure the Message ID is correctly copied from the original send operation's response.
    • Verify that the API key credential is valid and has necessary permissions.
    • Check network connectivity and Taximail service status.

Links and References

Discussion