---
title: "How to configure webhook for the Start node"
description: "Instructions for configuring the Webhook trigger for the Start node in Scenario Builder — URL, parameters, CRM and form integration."
---

# How to configure webhook for the Start node?

The **Webhook** trigger runs the section when an HTTP request is received at the generated URL. Suitable for integration with CRM, website forms, and external APIs.

## When you need it

- A website form sends data to ConnectiveOne.
- A CRM or other system triggers the scenario via HTTP.
- An external service needs to run bot logic.

## What to know

- **Webhook URL** — the address the external system sends requests to. Generated by the platform after the scenario is published.
- **call_node** — the platform API endpoint for invoking a node. URL format: `.../call_node/{bot_id}/{node_id}`.
- **URL parameters** — you can pass `channel`, `chat_id`, and additional query parameters.

## Before you start

- [x] You are signed in with integrator or administrator rights.
- [x] You have a section with a Start node added.
- [x] The scenario is published — the webhook URL is generated after publishing (the node receives a permanent ID).

## Steps

### 1. Select Webhook trigger type

1. Select the Start node on the canvas.
2. In Node Inspector, in the **Trigger type** field, select **Webhook**.

### 2. Publish the scenario

1. Click **Save** and **Publish** the scenario.
2. After publishing, the webhook URL appears in the node settings.

### 3. Copy and use the URL

**Base URL** (no chat binding):

```
{platform_address}/kw/api/call_node/{bot_id}/{node_id}
```

**URL with chat binding** (for sending messages to a specific dialog):

```
{platform_address}/kw/api/call_node/{bot_id}/{node_id}/{channel}/{chat_id}?param1=val1&param2=val2
```

**Parameters:**

| Parameter | Description |
|-----------|-------------|
| bot_id | Bot ID |
| node_id | Start node ID (appears after publishing) |
| channel | Channel (telegram, viber, widget, etc.) — optional |
| chat_id | Customer chat ID — optional |
| param1=val1 | Additional query-string parameters |

**Example:**

```
.../call_node/18/3/telegram/313145?name=John&surname=Whale
```

### 4. Configure the external system

1. In the website form, CRM, or other system, set the webhook URL as the endpoint for sending data.
2. Use **POST** or **GET** method depending on integration requirements.
3. Pass additional parameters in the query string or POST body.

## What happens next

When an HTTP request is received at the URL, the section runs. Request data is available in the scenario context (parameters, request body).

## How to verify it works

- Ensure the scenario is published.
- Send a test request (e.g. via Postman or curl) to the URL.
- Ensure the URL is accessible externally (not blocked by firewall).

## Common issues

| Problem | Solution |
|---------|----------|
| Webhook not firing | Check that the scenario is published. Ensure the URL is correct and accessible externally. |
| 404 or route error | Verify `bot_id` and `node_id` in the URL. |
| Timeout | Ensure the external system is not blocking requests. |

## Related materials

- [What is the Start node](/en/scenariobuilder/explanation/what-is-start-node.md)
- [Configure Start node triggers](/en/scenariobuilder/how-to/configure-start-node-triggers.md)
- [Launch scenario via API call_node](/en/integrations/how-to/launch-scenario-via-call-node.md)