Contact person: Business Client

Phone:Show

Email:Show

Location: United Kingdom

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"n8n Workflow Developer: Voice-to-Insight Automation System

Project Overview
Build a production-ready n8n workflow that captures voice recordings, transcribes them locally using Whisper, analyzes the content through OpenRouter (Claude, Gemini, OpenAi models all used) with customizable prompts, and stores everything in a structured Obsidian vault following PARA folder methodology.

This is a simple architecture with sophisticated prompts project. Your job is building the reliable infrastructure. I handle the prompt engineering.

Technical Stack

Required:

n8n (self-hosted on Ubuntu VPS)
[login to view URL] (local transcription, [login to view URL] model)
Claude API (Anthropic, I have account)
Obsidian vault (local markdown files)
Webhook triggers (voice file upload)

Environment:

Ubuntu 22.04 LTS VPS (4GB RAM, already provisioned)
n8n already installed (can provide access)
Git for version control
Expecting environment variables for API keys

Scope of Work

Core Deliverables
1. N8N Workflow (9 nodes)
Node structure:

Webhook receiver (accepts audio file + optional metadata)
Local Whisper transcription
Context router (determines Project/Area/Resource/Archive)
Claude API call (with customizable system prompt)
PARA-structured file storage
Daily synthesis trigger (cron)
Experiment generator (evening run)
Feedback collector
Weekly maintenance (cron)

2. Obsidian Vault Structure
Following PARA methodology:
/0-Inbox (raw captures)
/1-Projects (active, time-bound)
/2-Areas (ongoing responsibilities)
/3-Resources (reference knowledge)
/Patterns-Library
/Analytical-Lenses
/Prompt-Evolution
/4-Archives (completed items)
With appropriate templates and linking.

3. Prompt Management System

Markdown files for each prompt (I'll edit these)
n8n reads prompts from files (not hardcoded)
Clear naming convention
Version control friendly

4. Context Weighting Logic
Simple algorithm that:

Weights recent captures higher (exponential decay)
Prioritizes active projects over areas
Respects explicit priority tags
Calculates relevance scores

5. Maintenance Automation

Weekly summary generation
Context aging and archival
Project status updates
Pattern library updates

Documentation Requirements
Technical Docs:

n8n workflow architecture diagram
Data flow documentation
API integration details
Error handling approach
Environment variables list

User Docs:

Video walkthrough (15 minutes, clear audio)
Written guide for editing prompts
Guide for duplicating workflow for new contexts
Troubleshooting common issues
Backup and recovery procedures

Code Quality:

Inline comments for complex logic
Error handling on all external calls
Logging for debugging
Retry logic on API failures
Clear variable naming

Quality Standards

Code Standards

Environment variables for all secrets
No hardcoded values that should be configurable
Graceful error handling (continue workflow where possible)
Idempotent operations (safe to re-run)
Clear separation of concerns

Testing Requirements

Test with various audio file formats
Test with missing/corrupted files
Test API failure scenarios
Test storage failures
Verify weekly/daily triggers work

Performance Requirements

Transcription: <2 minutes for 10-minute audio
API calls: timeout after 30 seconds with retry
File operations: handle up to 100 captures/day
Cron jobs: complete in <5 minutes

Handover Requirements

Clean git repository with clear commit history
All dependencies documented with versions
Clear README with setup instructions
Environment template (.[login to view URL])
Health check endpoint for monitoring

Budget & Timeline
Fixed Price: $600 USD
Timeline: 3 weeks from project start
Milestones:

Week 1: Core workflow (nodes 1-5) + basic docs
Week 2: Automation (nodes 6-9) + testing
Week 3: Documentation + handover sessions

Payment:

30% on milestone 1 completion
40% on milestone 2 completion
30% on final acceptance

Support Expectations
During Build (included):

Daily async updates on progress
Quick response to technical questions (<24 hours)
Willingness to iterate on feedback

Post-Delivery (included):

3 live sessions (30 min each):

Session 1: Walkthrough and initial Q&A
Session 2: Week 1 check-in and adjustments
Session 3: Month 1 review and optimization


2 weeks of bug fix support
Handover documentation

What Makes You a Great Fit
Must Have:

Proven n8n experience (show portfolio with similar workflows)
API integration expertise (Claude/OpenAI/Anthropic)
Linux/VPS comfort (Ubuntu, cron, file systems)
Markdown/plaintext experience (Obsidian or similar)

Nice to Have:

[login to view URL] or local ML model experience
Second brain/PKM system knowledge
Previous voice automation work
Git workflow proficiency

Communication Style:

Direct, technical communication
Clear documentation habits
Comfortable with async work
Proactive problem-solver

Red Flags (Don't Apply If...)

You want to use no-code solutions instead of proper infrastructure
You can't provide code samples or portfolio
You're not comfortable with Unix/Linux environments
You need hand-holding on basic concepts
You pad timelines to fill budget

Why This Project Is Different
For You:

Clean, well-defined scope
Technically interesting (not just another CRUD)
Client knows what they want
Clear success criteria
Room for technical decision-making within constraints
Portfolio piece that shows real automation skills

What I Bring:

Technical clarity (I understand the stack)
Prompt engineering expertise (you don't need to understand this part)
Quick feedback cycles
Respect for your expertise
Realistic expectations

Application Requirements
To Apply, Include:

Portfolio Link

n8n workflows you've built (screenshots or video)
Similar automation projects
Any voice processing work


Technical Questions Response

How would you handle [login to view URL] local transcription in n8n?
What's your approach to retry logic on API calls?
How do you manage secrets in n8n workflows?


Timeline Estimate

Your breakdown of the 3-week timeline
Any assumptions you're making
What could extend timeline


One Clarification Question

What's the first thing you'd need clarified to start?



Format: Plain text, no generic templates
Selection Criteria
Evaluating on:

Portfolio quality (60%)
Technical responses (30%)
Communication clarity (10%)

Not evaluating on:

Lowest price (budget is fixed)
Fastest timeline (quality over speed)
Years of experience (skills over tenure)

Legal & Logistics

IP Rights: You transfer all code to me on payment
Confidentiality: Standard NDA (I'll provide)
Communication: Freelancer Platform
Time Zone: I'm in Southern Africa (CAT/SAST), flexible on your hours

Questions Welcome
Ask in your application or before. Good questions help me pick the right person.

What Happens After You're Selected
Week 0:

Kickoff call (30 min)
VPS access provided
Git repo created
Environment setup confirmed

Week 1-3:

Daily async updates (your time zone)
Code review at each milestone
Quick feedback cycles
Test on my system

Week 4:

Handover sessions
Documentation review
Final acceptance testing
Payment completion

Success Looks Like

I can duplicate the workflow without asking you questions
System runs reliably for 30 days without intervention
Editing prompts requires zero n8n knowledge
Documentation enables future developers to extend
You're proud to show this in your portfolio


Apply with confidence if you're the right fit. Skip if you're not—saves us both time." (client-provided description)