Nqdev: EsmsVN Trigger icon

Nqdev: EsmsVN Trigger

Webhook to receive status updates from eSMS

Nqdev: EsmsVN Trigger

AI-generated

Overview

This node acts as a webhook trigger designed to receive status updates from the eSMS service. It listens for incoming HTTP requests sent by eSMS, allowing workflows in n8n to react automatically to these updates. Typical use cases include monitoring SMS delivery statuses or other event notifications provided by the eSMS platform.

For example, when an SMS message's status changes (e.g., delivered, failed), eSMS sends a webhook request to this node, which then triggers downstream workflow actions such as logging the event, notifying users, or updating databases.

Properties

Name Meaning
Due to Telegram API limitations, you can use just one Telegram trigger for each bot at a time Informational notice about Telegram API constraints (not directly related to eSMS).
Trigger On Specifies which types of updates to listen for. Currently supports only "All updates".
Additional Fields Optional extra settings:
- Logging Request: Enable or disable logging of incoming requests (boolean).

Output

The node outputs JSON data representing the body of the incoming webhook request from eSMS. This JSON contains the status update details or other relevant information sent by the eSMS service.

The output structure is:

[
  {
    /* The full JSON payload received from eSMS webhook */
  }
]

No binary data output is produced by this node.

Dependencies

  • Requires an active eSMS account and proper configuration of webhook URLs on the eSMS platform to send updates.
  • Needs an API key credential for authentication with eSMS (configured in n8n credentials).
  • No additional external dependencies beyond standard webhook handling.

Troubleshooting

  • Common issues:

    • Webhook not triggering: Ensure that the webhook URL generated by this node is correctly registered in the eSMS dashboard.
    • Missing or invalid credentials: Verify that the API key credential is properly set up and has necessary permissions.
    • Receiving no data: Confirm that eSMS is sending updates and that the "Trigger On" property includes the desired update types.

  • Error messages:

    • Since the webhook creation and deletion methods are stubbed to always succeed, errors mostly arise from misconfiguration outside the node (e.g., network issues, incorrect webhook URL).
    • If the node does not receive any data, check connectivity and webhook registration on the eSMS side.

Links and References

Discussion