Opportunity Matcher v2
Configured with Email Send, HTTP Request, Schedule Trigger, Write Binary File. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Code
- Routing
- Files / media
- Messaging
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 |
|---|---|---|---|
| Weekly schedule | Trigger | Schedule Trigger | See node parameters |
| Fetch Anthropic board | Web / API | HTTP Request | See node parameters |
| Fetch Figma board | Web / API | HTTP Request | See node parameters |
| Normalize records | Code | Code | See node parameters |
| Score and route (the intelligence) | Code | Code | See node parameters |
| Decision = PURSUE or NETWORK? | Routing | If | See node parameters |
| Generate briefs | Code | Code | See node parameters |
| Save digest files | Files / media | Write Binary File | See node parameters |
| Email the digest | Messaging | Email Send | See node parameters |
| Log the failure | 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
Error handling
Error handling
- HTTP nodes: retry 3x with backoff, then the error branch fires ("Continue (using error output)").
- Error branch logs the failure and falls back to the cached Assignment 3 file — the digest still ships, flagged as cached.
- Code nodes: try/catch per record; malformed items go to quarantine, never crash the run.
- Missing fields default (company demand 0.5, empty text) and are noted in the run report. See ERROR-HANDLING.md for the full table.
Opportunity Matcher v2
Opportunity Matcher v2
Purpose and structure
This folder contains the Opportunity Matcher v2 workflow. Its executable nodes use code, emailSend, httpRequest, if, scheduleTrigger, writeBinaryFile. 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
Weekly schedule
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.