Node-RED is a free, open-source flow tool that runs on your own hardware or server. There is no account and no middleman: DynamiHost sends the scan.created event straight to your Node-RED instance every time one of your dynamic codes is scanned, and your flow takes it from there.

What you need

  • A DynamiHost plan with webhooks: Trial, Pro or Business. If the Webhooks page in your dashboard shows a locked message, your plan does not include webhooks yet.
  • A running Node-RED instance that is reachable at a public HTTPS address. DynamiHost cannot deliver to localhost or other private addresses, and endpoint URLs on private networks are rejected when you save them.

Step 1: Get a webhook URL from Node-RED

  1. In the Node-RED editor, add an HTTP In node to a flow and set its method to POST.
  2. Give it a path you will recognise, for example /dynamihost-scans. The node's URL is your instance's address plus that path.
  3. Add an HTTP Response node after it, set to return status 200, and wire the flow together. DynamiHost treats any 2xx answer as a successful delivery and anything else as a failure to retry.
  4. Click Deploy. The URL is only live once the flow is deployed.

Protect the instance itself (Node-RED's editor password and HTTPS) before exposing it: anyone who finds the path can post to it, so verify the signature as described below if the flow does anything important.

Step 2: Add the URL in DynamiHost

  1. Open Webhooks in the dashboard and click Add endpoint.
  2. Paste the full URL of your HTTP In node and select the scan.created event.
  3. Save, then copy the signing secret shown once for the endpoint. A Function node can verify it: the Integrations page in the dashboard has a ready-made Node snippet for the check, and the incoming headers are on the message Node-RED passes along.

Step 3: Test the connection

On the Webhooks page, click Send test on your new endpoint. Add a Debug node to your flow and watch the sample payload arrive in the debug sidebar. Then scan one of your codes with your phone and watch the real event follow.

What arrives

Every delivery is the scan.created event: the code's id, short code and name, the scan time, and, when known, the country, city, device, operating system, browser and referrer. The full payload format, signature verification, retries and the automatic disable rule are covered in Webhooks: get notified on every scan in this help centre.

Automation ideas

  • Switch a smart light, relay or display in your venue when a code is scanned, through MQTT or a local API node.
  • Append scans to a local file or database for offline reporting.
  • Forward scans to another internal system that is not reachable from the internet, with Node-RED as the bridge.