My workflow 7
Configured with HTTP Request, Postgres, Respond To Webhook, Switch, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Code
- Data store
- Transform
- Routing
- 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 |
|---|---|---|---|
| Webhook: Receive Transcript | Trigger | Webhook | See node parameters |
| Validate Input | Code | Code | See node parameters |
| DB: Insert earnings_call | Data store | Postgres | executeQuery |
| Set Call Context | Transform | Edit Fields | See node parameters |
| Process Section Response | Code | Code | See node parameters |
| DB: Insert transcript_section | Data store | Postgres | executeQuery |
| Route by Section Type | Routing | Switch | See node parameters |
| Process Guidance Response | Code | Code | See node parameters |
| Process Risk Response | Code | Code | See node parameters |
| Process QA Response | Code | Code | See node parameters |
| DB: Insert guidance_signal | Data store | Postgres | executeQuery |
| DB: Insert risk_admission | Data store | Postgres | executeQuery |
| DB: Insert qa_pressure | Data store | Postgres | executeQuery |
| DB: Log Agent Run | Data store | Postgres | executeQuery |
| Fetch All Signals for Summary | Data store | Postgres | executeQuery |
| Process Summary Response | Code | Code | See node parameters |
| DB: Insert call_summary | Data store | Postgres | executeQuery |
| DB: Mark Call Complete | Data store | Postgres | executeQuery |
| Final Response | Code | Code | See node parameters |
| Webhook Response | Web / API | Respond To Webhook | See node parameters |
| Groq: Generate Call Summary | Web / API | HTTP Request | POST |
| Groq: Parse Transcript Sections | Web / API | HTTP Request | POST |
| Groq: Extract Guidance Signals | Web / API | HTTP Request | POST |
| Groq: Extract Risk Admissions | Web / API | HTTP Request | POST |
| Groq: Map QA Pressure | Web / API | HTTP Request | POST |
| Execute a SQL query | Data store | Postgres | executeQuery |
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
groqApihttpHeaderAuthpostgres
Workflow notes
My workflow 7
My workflow 7
Purpose and structure
This folder contains the My workflow 7 workflow. Its executable nodes use code, httpRequest, postgres, respondToWebhook, set, switch, webhook. 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
Webhook: Receive Transcript
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.