---
title: Trigger a Link’nX scenario from an HTTP URL (GET webhook)
description: Create a Link’nX HTTP trigger, copy its private URL and have another system call it with GET to start the associated scenarios.
canonical: https://wiki.can-nx.com/en/guides/link-trigger-http/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: HTTP trigger, called with GET by a system that can reach the gateway"
---

# Trigger a Link’nX scenario from an HTTP URL (GET webhook)

Context: Link’nX web: HTTP trigger, called with GET by a system that can reach the gateway

The **HTTP** trigger in Link’nX creates a private URL at the gateway’s address. When an authorized system calls this URL with the **GET** method, the associated scenarios receive an execution request.

Intended for installers and administrators who connect another system to a Link’nX scenario. To send a request yourself from a scenario, use an [HTTP action](https://wiki.can-nx.com/en/guides/link-action-http/) instead.

## Before you start

- The calling system can reach the gateway at the address shown in the form. For access from another network or from the Internet, ask support for the appropriate procedure before changing the network configuration.
- The actions of the associated scenarios are ready: calling the URL can request their execution.

## Create the HTTP trigger

1. In **Triggers**, click **Add**, then choose **HTTP** in **Select a trigger type**, **Protocols** group.
2. Fill in **Name**, required, 64 characters maximum. Fictitious example: “Reception call”.
3. In **URL**, enter only the endpoint name, after the prefix already displayed. Fictitious example: **reception-call**. This field is required and must not contain any slash **/**: do not paste a full URL into this part.
4. Click the floppy disk at the bottom right, then wait for the [creation confirmation](https://wiki.can-nx.com/en/guides/link-trigger-edit/).

## Associate the trigger with the scenario

[Associate the trigger with the scenario](https://wiki.can-nx.com/en/guides/link-compose-scenario/), configure its actions and conditions, save, then check the scenario’s activation.

If several scenarios use this trigger, a call may concern all of them. Check the [linked scenarios](https://wiki.can-nx.com/en/guides/link-related-scenarios/) before reusing a URL.

## Copy the URL into the calling system

1. Reopen the HTTP trigger and click the two-sheets icon, to the left of the **URL** field, whose tooltip is **Copy**.
2. After **URL copied to clipboard**, enter the URL in the configuration of the authorized system and check the copy. Keep this URL private.
3. Configure this system to call the copied URL with the **GET** method.

## Check the result

Perform a test only when you are ready to accept the planned actions on the installation. Then observe the expected result on the devices and see [the scenario history](https://wiki.can-nx.com/en/guides/link-history/). The response to the call is not enough to confirm that each device carried out its command: the scenario’s conditions and activation state still need to be checked.

## Edit or duplicate an HTTP trigger

To change the endpoint name, open the trigger, change **URL**, save, then confirm the affected scenarios if the window appears. Copy the new URL and update the calling system: calls to the old endpoint must no longer be used for this trigger.

If you duplicate an HTTP trigger for independent use, choose a distinct endpoint before saving.

## Troubleshooting

| Message or symptom | Action |
| --- | --- |
| **Issue with the field 'URL'. It requires a value.** | Fill in the endpoint |
| **The URL must not contain a slash (/)** | Remove the slashes and check that you have not pasted the full address |
| The call has no effect | First check that the copied URL matches the saved trigger and that the calling system can reach the address shown. Then check the associated scenario, its activation, its conditions and its delays |

Do not repeat calls to diagnose a lack of reaction. If the problem persists, contact support@can-nx.com with the product, the context, the trigger name, the time and the result of the call, without sending the full private URL.