My workflow
Configured with HTTP Request. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Code
- Transform
- Web / API
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 |
|---|---|---|---|
| When clicking ‘Execute workflow’ | Trigger | Manual Trigger | See node parameters |
| Code in Python (Beta) | Code | Code | See node parameters |
| Company Input | Transform | Edit Fields | See node parameters |
| Get Financial Overview1 | Web / API | HTTP Request | See node parameters |
| Get Income Statement1 | Web / API | HTTP Request | See node parameters |
| Process Company Data1 | Code | Code | See node parameters |
| Google Search Patent | Web / API | HTTP Request | See node parameters |
| Process Patent Data1 | Code | Code | See node parameters |
| Process Financial Data1 | Code | Code | See node parameters |
| Generate Analysis1 | Code | Code | See node parameters |
| Generate Final Report1 | Code | Code | See node parameters |
| Merge | Transform | Merge | 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
My workflow
My workflow
Purpose and structure
This folder contains the My workflow workflow. Its executable nodes use code, httpRequest, manualTrigger, merge, 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
When clicking ‘Execute workflow’
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.