Actions63
- 1. Manager Actions
- 2. Mouse Actions
- 3. Keyboard Actions
- 4. Browser Control Actions
- 5. Element Actions
- 6. Image Actions
- 7. Others Actions
- 8. Email Actions
- 9. Developer Actions
- 10. General Debug Actions
9. Developer → get_active_code
AI-generatedSummary
Publishes an MQTT request for the Developer get_active_code action, which retrieves the HTML of the active frame so you can inspect the rendered page while building selectors. Configure the destination topic and remote debugging port; optionally include selected input fields and wait for an MQTT response before continuing.
Inputs
- Topic (required) — MQTT topic used to publish the request, such as a device-specific topic or a functional namespace.
- Remote Port (required) — CDP port used to route the request to the intended client session. The default reads
remote_debugging_portfrom the incoming item; the UI also documentsremote_portas an equivalent key and127001for a local session. - QoS — MQTT delivery level: 0 (at most once), 1 (at least once, default), or 2 (exactly once).
- Include Input Items — When enabled, attaches incoming item data to
payload.inputItems. Use the accompanying field selector to choose fields; nested paths and array indexes are supported. Defaults to false. - Wait For Response — When enabled, waits for an MQTT response before returning output. Defaults to false, so the request is published without waiting.
- Response Timeout (sec) — Maximum wait for a response, in seconds; shown when waiting is enabled. Defaults to 60.
- Delay Next Step (ms) — Delay before the node proceeds. Runs after the response when waiting is enabled, or after publishing otherwise. Defaults to
rand(200,1000).
Output shape
One or more n8n items containing the MQTT response when waiting is enabled; otherwise the node publishes the request and proceeds without waiting for a response.
The supplied source view omits implementation bodies, so it does not establish the exact response fields or whether input items are preserved in the output.
