Public webhook relay
UnknownWhat this workflow does
This workflow has 13 nodes and runs on a schedule (every 10 seconds). Along the way it connects @Horka (community). It also calls webhook.site over HTTP.
How it runs
Trigger: On a schedule (every 10 seconds).
- Local Webhook Address (Edit Fields (Set)): sets 1 field: webhook
- Retrieve Last Processed (Key Value Storage): read
- Retrieve Auth Token (Key Value Storage): read
- Merge: merges the data from its input branches
- If: checks a condition and branches into true / false
- Unprocessed Requests (Code): runs custom JavaScript code
- Get Latest Requests (HTTP Request): calls an HTTP API
- Get Auth Token (HTTP Request): calls webhook.site (POST)
- Latest Update Time (Code): runs custom JavaScript code
- Store Auth Token (Key Value Storage): uses Key Value Storage
…plus 2 more steps. See the full node list below.
Services it uses
HTTP calls to: webhook.site
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that @horka is verified or supports 3.0 (used in Store Auth Token, Store Last Processed, Retrieve Auth Token).
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Merge
n8n-nodes-base.merge - Edit Fields (Set)
n8n-nodes-base.set - Key Value Storage
@horka.tv/n8n-nodes-storage-kv.keyValueStorage - If
n8n-nodes-base.if
From the author
Disclaimer This template only works on n8n local instances! How it Works This workflow allows you to to receive webhooks from the public web and have your local workflow catch them, without any remote proxy. It is very useful for running quick tests without…