Entry Point Node Parameters

The Entry Point node (entry-point) defines how to enter a scenario section: via transition from another section (Exit Point) or via HTTP/API (webhook). In Node Inspector (right panel) the following sections are available:

Trigger Type (entryTriggerType)

  • entry — entry from another section (transition from Exit Point node).
  • webhook — entry via HTTP request or deep link (Telegram, Viber, etc.).

Parameters for entry

  • Connector alias (connectorAlias) — unique identifier (UUID) used in the Exit Point node to transition to this section. Use a clear name to easily find this entry point when configuring Exit Point.

Tip: connectorAlias — used in Exit Point for transition; webhook — for HTTP requests and deep links.

Parameters for webhook

  • Connector alias (connectorAlias) — identifier for external calls.
  • Webhook URL — general URL for HTTP POST/GET requests.
  • Telegram URL — URL for Telegram deep link.
  • Viber URL — URL for Viber deep link.

URL Structure

URL is formed by the template:

call_node/{bot_id}/{node_id}/{channel}/{chat_id}?param1=val1&param2=val2
  • bot_id — bot identifier.
  • node_id — entry point node identifier.
  • channel — channel (telegram, viber, widget, etc.).
  • chat_id — chat identifier (optional).
  • Parameters param1, param2 are passed to the scenario context.

JSON Data

For advanced integrators — manual editing of jsonData for additional webhook or entry parameters.