← All N8N workflows
AI & researchCodeHTTP RequestMergeRespond To WebhookSchedule Trigger

Mycroft Agent 5 — Research Footprint Monitor

Configured with HTTP Request, Respond To Webhook, Schedule Trigger, Supabase, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TriggerCron TriggerSchedule TriggerTriggerManual Pipeline WebhookWebhookCodeFetch WatchlistCodeWeb / APIScholar: NVIDIAHTTP RequestWeb / APIScholar: AMDHTTP RequestWeb / APIScholar: IntelHTTP RequestWeb / APIScholar: GoogleHTTP RequestWeb / APIScholar: AppleHTTP RequestWeb / APIScholar: MicrosoftHTTP RequestWeb / APIScholar: MetaHTTP RequestTransformMerge Scholar ResultsMergeCodeParse Scholar DataCodeWeb / APIWikipedia: NVIDIAHTTP RequestWeb / APIWikipedia: AMDHTTP RequestWeb / APIWikipedia: IntelHTTP RequestWeb / APIWikipedia: GoogleHTTP RequestWeb / APIWikipedia: AppleHTTP RequestWeb / APIWikipedia: MicrosoftHTTP RequestWeb / APIWikipedia: MetaHTTP RequestTransformMerge Wikipedia ResultsMergeCodeParse Wikipedia DataCodeTransformCombine SignalsMergeCodeCalculate FootprintScoresCodeCodeAggregate for GroqCodeWeb / APIGroq: Footprint AnalystHTTP RequestCodeParse Groq ResponseCodeCodeSignal AssemblerCodeData storeUpsert to SupabaseSupabaseCodeGenerate ReportCodeData storeStore Report inSupabaseSupabaseWeb / APIPipeline ResponseRespond To Webhook

Node categories in this workflow

  • Trigger
  • Code
  • Web / API
  • Transform
  • Data store

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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Cron TriggerTriggerSchedule TriggerSee node parameters
Manual Pipeline WebhookTriggerWebhookSee node parameters
Fetch WatchlistCodeCodeSee node parameters
Scholar: NVIDIAWeb / APIHTTP RequestSee node parameters
Scholar: AMDWeb / APIHTTP RequestSee node parameters
Scholar: IntelWeb / APIHTTP RequestSee node parameters
Scholar: GoogleWeb / APIHTTP RequestSee node parameters
Scholar: AppleWeb / APIHTTP RequestSee node parameters
Scholar: MicrosoftWeb / APIHTTP RequestSee node parameters
Scholar: MetaWeb / APIHTTP RequestSee node parameters
Merge Scholar ResultsTransformMergeSee node parameters
Parse Scholar DataCodeCodeSee node parameters
Wikipedia: NVIDIAWeb / APIHTTP RequestSee node parameters
Wikipedia: AMDWeb / APIHTTP RequestSee node parameters
Wikipedia: IntelWeb / APIHTTP RequestSee node parameters
Wikipedia: GoogleWeb / APIHTTP RequestSee node parameters
Wikipedia: AppleWeb / APIHTTP RequestSee node parameters
Wikipedia: MicrosoftWeb / APIHTTP RequestSee node parameters
Wikipedia: MetaWeb / APIHTTP RequestSee node parameters
Merge Wikipedia ResultsTransformMergeSee node parameters
Parse Wikipedia DataCodeCodeSee node parameters
Combine SignalsTransformMergeSee node parameters
Calculate Footprint ScoresCodeCodeSee node parameters
Aggregate for GroqCodeCodeSee node parameters
Groq: Footprint AnalystWeb / APIHTTP RequestPOST
Parse Groq ResponseCodeCodeSee node parameters
Signal AssemblerCodeCodeSee node parameters
Upsert to SupabaseData storeSupabaseupsert
Generate ReportCodeCodeSee node parameters
Store Report in SupabaseData storeSupabaseSee node parameters
Pipeline ResponseWeb / APIRespond To WebhookSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

Mycroft Agent 5 — Research Footprint Monitor

Mycroft Agent 5 — Research Footprint Monitor

Purpose and structure

This folder contains the Mycroft Agent 5 — Research Footprint Monitor workflow. Its executable nodes use code, httpRequest, merge, respondToWebhook, scheduleTrigger, supabase, 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

Cron Trigger, Manual Pipeline Webhook

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.

More in AI & research