Workflow A — Extract & Store Raw Data
Configured with Execute Workflow, HTTP Request, Postgres, Schedule Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Code
- Data store
- Routing
- Subworkflow
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 |
| Fetch TechCrunch | Web / API | HTTP Request | See node parameters |
| Fetch VentureBeat | Web / API | HTTP Request | See node parameters |
| Fetch HackerNews | Web / API | HTTP Request | See node parameters |
| Fetch ArXiv | Web / API | HTTP Request | See node parameters |
| Fetch Reddit | Web / API | HTTP Request | See node parameters |
| Parse TechCrunch | Code | Code | See node parameters |
| Parse VentureBeat | Code | Code | See node parameters |
| Parse HackerNews | Code | Code | See node parameters |
| Parse ArXiv | Code | Code | See node parameters |
| Parse Reddit | Code | Code | See node parameters |
| Store TechCrunch | Data store | Postgres | executeQuery |
| Store VentureBeat | Data store | Postgres | executeQuery |
| Store HackerNews | Data store | Postgres | executeQuery |
| Store ArXiv | Data store | Postgres | executeQuery |
| Store Reddit | Data store | Postgres | executeQuery |
| Verify — Count Stored Items | Data store | Postgres | executeQuery |
| Check — New Items Exist? | Routing | If | See node parameters |
| Trigger — Start Workflow B | Subworkflow | Execute Workflow | See node parameters |
| Log — Skip | Code | Code | 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
postgres
Workflow notes
Trigger — Start Workflow B
ADD YOUR DETAILS: Replace WORKFLOW_B_ID with Workflow B numeric ID.
Workflow A — Extract & Store Raw Data
Workflow A — Extract & Store Raw Data
Purpose and structure
This folder contains the Workflow A — Extract & Store Raw Data workflow. Its executable nodes use code, executeWorkflow, httpRequest, if, postgres, scheduleTrigger. 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
Nik Bear Brown; rights confirmed 2026-10-19 MIT; preserve source notices.