Tech_Stack_Directional_Signal_Agent
Configured with Form Trigger, HTTP Request. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Code
- 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 |
|---|---|---|---|
| Form Trigger | Trigger | Form Trigger | See node parameters |
| Company Input | Code | Code | See node parameters |
| GitHub GraphQL | Web / API | HTTP Request | POST |
| Process Repos + Language Analysis | Code | Code | See node parameters |
| Fetch Commit Activity | Code | Code | See node parameters |
| Velocity Analysis | Code | Code | See node parameters |
| Build Groq Prompt | Code | Code | See node parameters |
| Groq AI Analysis | Web / API | HTTP Request | POST |
| Score + Claims Schema | Code | Code | See node parameters |
| Generate Dashboard | Code | Code | See node parameters |
| Export HTML File | Code | Code | See node parameters |
| Code | 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
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
Tech_Stack_Directional_Signal_Agent
Tech_Stack_Directional_Signal_Agent
Purpose and structure
This folder contains the Tech_Stack_Directional_Signal_Agent workflow. Its executable nodes use code, formTrigger, httpRequest. 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
Form 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.