Taximail icon

Taximail

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

Actions5

Overview

This 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.

Common scenarios for using the "Check Status" operation include:

  • Verifying whether an email or SMS has been successfully delivered.
  • Tracking message processing states in workflows that depend on message confirmation.
  • Auditing or logging message statuses for compliance or troubleshooting.

For example, after sending an email or SMS through this node, you can use the "Check Status" operation with the returned Message ID to confirm if the message was delivered or if it encountered any issues.

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 sending a message. It is required to query the status.

Output

The output JSON object contains the full response from the Taximail API regarding the message status. Key fields include:

  • operation: The string "check_status" indicating the performed operation.
  • message_id: The Message ID used to query the status.
  • Additional fields as returned by the Taximail API describing the current status of the message (e.g., delivery state, timestamps, error messages).

No binary data is output by this operation.

Example output structure (simplified):

{
  "operation": "check_status",
  "message_id": "some_message_id",
  "status": "delivered",
  "delivered_at": "2024-06-01T12:34:56Z",
  "error": null
}

Dependencies

  • Requires an API key credential for HTTP Basic Authentication to access the Taximail API.
  • The node uses the Taximail API endpoint for transactional messages to check status.
  • No additional environment variables are needed beyond the configured API credentials.

Troubleshooting

  • Common Issues:

    • Providing an invalid or expired Message ID will result in errors or empty status responses.
    • Missing or incorrect API credentials will cause authentication failures.
    • Network connectivity issues may prevent successful API calls.

  • Error Messages:

    • If the operation fails due to API errors, the node throws an error with a message prefixed by "Operation failed".
    • Unknown operation errors should not occur if the node is configured correctly but indicate misconfiguration if they do.

  • Resolution Tips:

    • Ensure the Message ID is copied exactly from the send operation's response.
    • Verify that the API credentials are valid and have sufficient permissions.
    • Check network connectivity and firewall settings allowing outbound HTTPS requests to the Taximail API.

Links and References

Discussion