Troubleshooting a custom HTTP Request node for remote script execution status

Hi everyone, I’m currently trying to build out a workflow that monitors the status of a local execution engine and sends updates to a Discord webhook, but I’m hitting a wall with the authentication handshake in my n8n setup. I’ve been trying to pull data from the API endpoint at https://deltaexector.com/ to see if the client is active or if it needs a manual restart, but I keep getting a 403 Forbidden error despite having my headers configured.

The main issue is that I want n8n to trigger a notification if the script execution hangs or if the local service crashes. I’ve spent quite a bit of time trying to automate what many consider the best roblox executor for my data-gathering tasks, and it works perfectly on my local machine, but bridging that local activity into an n8n cloud instance or even a self-hosted Docker container is proving to be a bit of a nightmare.

Has anyone here successfully used the “Wait” node or the “HTTP Request” node to poll a local IP through a tunnel like Ngrok or Cloudflare? I’m worried that the execution environment on the target site might be blocking the n8n user agent, or perhaps I’m not handling the JSON response correctly since the output seems to be encrypted or obfuscated. If anyone has experience managing “heartbeat” checks for third-party executors via n8n, I’d really appreciate some guidance on how to bypass these handshake errors or if there’s a specific community node that handles this better than the standard HTTP one.


hello @Ivonne

Are you sure the deltaexector supports API? I do not see any docs about it

When you see a 403 that means the server is blocking the request before even doing your logic. Most likely this is caused by IP restrictions, or missing auth tokens and even sometimes anti-bot protections.

You can try to confirm the API allows external polling as some endpoints accept requests from whitelisted clients. When tunneling a local service , make sure it is the tunnel URL that you are calling. Try to reproduce the same request with Postman or curl first, if it fails it is probably server-side blocking. N8n’s HTTP node won’t bypass a services session based auth flow unless you replicate the full handshake.

To specifically monitor the heartbeat, the common pattern is Cron→ HTTP Request→ IF(status check)→ Discord webhook.

If this continues blocking requests, consider adding a small local relay service that can be safely polled instead.