receive schedule events and get auth token and get latest requests
Configured with HTTP Request, Key Value Storage, Schedule Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Code
- Transform
- Data store
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Get Auth Token | Web / API | HTTP Request | POST |
| Unprocessed Requests | Code | Code | See node parameters |
| Get Latest Requests | Web / API | HTTP Request | See node parameters |
| POST to n8n | Web / API | HTTP Request | POST |
| Merge | Transform | Merge | See node parameters |
| Local Webhook Address | Transform | Edit Fields | See node parameters |
| Latest Update Time | Code | Code | See node parameters |
| Store Auth Token | Data store | Key Value Storage | See node parameters |
| Store Last Processed | Data store | Key Value Storage | See node parameters |
| Retrieve Auth Token | Data store | Key Value Storage | read |
| Retrieve Last Processed | Data store | Key Value Storage | read |
| If Auth Token Exists | Routing | If | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Public Webhook Relay
Public Webhook Relay
How it Works
Utilizes webhook.site to receive public webhook requests and relays them to your local n8n workflow
How to Use
- To use with local key-value store:
Go to settings > community nodes and enter
@horka.tv/n8n-nodes-storage-kvto install the key-value store node - To use with a different storage method: Replace the four key-value nodes with a temporary storage option of your choice (Airtable, Notion, Firebase, etc). This is required to save data between runs.
- Set Schedule Trigger with a polling interval (default is every 10 seconds).
- Set your local workflow address in Local Webhook Address.
How to Test
- Set the workflow to Active.
- After workflow executes at least once, you can check the input to Get Latest Requests for your auth token.
- Run this command:
curl -X POST -H "Content-Type: application/json" -d '{"foo":"bar"}' https://webhook.site/[THE AUTH TOKEN YOU JUST GOT] - Now check Executions and confirm that the workflow ran all the way to the end. Confirm in Unprocessed Requests that your data was retrieved (data[0].content should be equal to {"foo":"bar"})
- Now check your other local workflow and confirm that it was triggered with the correct data packet
{"foo":"bar"}. - You're done!
Caveats
At present, the relay expects a POST with form/json data. If you wish to relay raw data or GET requests, please alter the Unprocessed Requests and POST to n8n nodes accordingly.
receive schedule events and get auth token and get latest requests
receive schedule events and get auth token and get latest requests
Purpose and structure
This folder contains the receive schedule events and get auth token and get latest requests workflow. Its executable nodes use code, httpRequest, if, keyValueStorage, merge, scheduleTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Http/0588_HTTP_Schedule_Create_Webhook.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- 1. Retrieve existing or get new auth token for webhook.site
- 2. Check if any new requests to webhook that came later than the last checked request
- 3. Relay the request to the local n8n workflow set in *Local Webhook Address*
- 0. Set this to your local workflow address (Production URL or Test URL in your Workflow Trigger node)