eTelecom Zalo Oa Trigger icon

eTelecom Zalo Oa Trigger

Handle Zalo Oa webhook events

Overview

This node acts as a webhook trigger for Zalo Official Account (OA) events, specifically integrated via the eTelecom API. It listens for incoming webhook events from a selected Zalo OA and outputs the event data to be used in an n8n workflow.

Common scenarios where this node is beneficial include:

  • Automating responses or workflows based on messages or interactions received on a Zalo Official Account.
  • Integrating Zalo OA events with other systems such as CRMs, ticketing tools, or marketing platforms.
  • Monitoring and logging activities happening on a Zalo OA in real-time.

For example, when a user sends a message to your Zalo OA, this node can trigger a workflow that processes the message content, stores it in a database, or sends an automated reply.

Properties

Name Meaning
Webhook URLs Hidden property storing the webhook URLs internally; not user-configurable.
Zalo Official Account Name or ID (oaId) Required selection of the Zalo Official Account to listen to. Options are dynamically loaded from the connected eTelecom API. You can choose from the list or specify an ID using an expression.

Output

The node outputs JSON data containing details about the webhook event received from the Zalo OA. The output structure includes:

  • headers: HTTP headers received with the webhook request.
  • body: The full payload of the webhook event.
  • event: The event name extracted from the payload (event_name field).
  • oaId: The ID of the Zalo Official Account configured in the node.
  • timestamp: The ISO string timestamp when the event was processed.

This structured output allows downstream nodes to easily access event metadata and payload for further processing.

The node does not output binary data.

Dependencies

  • Requires an API key credential to connect to the eTelecom API service.
  • The credential must provide a domain URL and a bearer token for authorization.
  • The node uses the eTelecom API endpoints to:
    • Fetch the list of available Zalo Official Accounts.
    • Register and unregister the webhook URL for the selected OA.
  • Proper configuration of the credential with valid API access is necessary for the node to function.

Troubleshooting

  • No credentials provided: The node requires a valid API authentication token to communicate with the eTelecom API. Ensure the credential is set up correctly in n8n.
  • Failed to fetch Zalo OAs: If the node cannot retrieve the list of Zalo Official Accounts, check the API token validity and network connectivity.
  • Webhook registration errors: Errors during webhook creation or deletion usually indicate issues with the API token or permissions. Verify the token scope and that the OA ID is correct.
  • Invalid API response: If the API returns unexpected data or parsing fails, confirm the API endpoint availability and response format.
  • Webhook URL mismatch: The node checks if the webhook URL is already registered. If the webhook is not triggering, verify that the URL configured in the Zalo OA matches the one generated by the node.

Links and References

Discussion