DEV Community: ox3adie1

How I Built a Niche File Converter for Turkish Lawyers

ox3adie1 — Tue, 07 Apr 2026 16:36:14 +0000

Ever heard of a .udf file? Probably not — unless you're a Turkish lawyer.

The Problem

Turkey has one of the world's most comprehensive digital judiciary systems called UYAP (National Judiciary Informatics System). It connects all courts, prosecutors, lawyers, and even prisons across the country.

The catch? UYAP's document editor saves files in a proprietary format called UDF (UYAP Document Format). These .udf files can only be opened with the UYAP Document Editor — a program that only runs on computers connected to the UYAP network.

This means hundreds of thousands of lawyers struggle to:

Share court documents with clients
Read case files on their phones
Archive documents in a universal format
Print documents outside the courthouse

The Solution

I built convertudftopdf.com — a free, browser-based UDF to PDF converter.

Key Technical Decisions

1. 100% Client-Side Processing

Legal documents are sensitive. No file should ever touch a server. The entire conversion happens in the browser using JavaScript.

2. Stack

JSZip for extracting UDF archive contents
jsPDF for PDF generation with Turkish character support
Noto Serif font embedded for proper Turkish characters
Cloudflare Pages for hosting (free, fast, global CDN)

3. Turkish Character Support

This was the trickiest part. Turkish has special characters that many PDF libraries don't handle well. I embedded Noto Serif font variants to ensure perfect rendering.

4. Batch Processing

Lawyers often need to convert dozens of files. The tool supports multi-file selection with drag-and-drop, converting all files sequentially and offering a ZIP download.

The Ultra-Niche Advantage

Here's the interesting business insight: when your product serves an ultra-niche market, you might be the only solution. There's essentially zero competition for "UDF to PDF conversion" because:

The market is too small for big companies to care
Understanding the format requires domain knowledge of Turkish legal tech
The user base is geographically concentrated

This means even basic SEO puts you at the top of search results for your target keywords.

Results

The site launched recently and is already getting organic traffic from Turkish lawyers searching for UDF conversion solutions. The conversion happens entirely in the browser, so server costs are essentially zero (just static hosting on Cloudflare Pages).

Try It

If you're curious (or happen to be a Turkish lawyer):

Converter: convertudftopdf.com
English guide: What is UDF?

Lessons Learned

Niche is powerful — Being the only solution in a specific space beats being one of thousands in a broad space
Privacy as a feature — Client-side processing isn't just a technical choice, it's a trust signal for legal professionals
Understand your users — Turkish lawyers need Turkish language support, mobile compatibility, and zero friction
Static sites scale infinitely — When processing happens client-side, your hosting costs don't increase with users

Have you built something for an ultra-niche market? I'd love to hear about it in the comments!

How I Ended Up Building a Stable Async Processor for n8n (and Turned It Into a PRO Tempate)

ox3adie1 — Sat, 15 Nov 2025 19:20:58 +0000

How I Built a Stable Asynchronous Batch Processor for n8n (And Why the Default Loops Weren’t Enough)

Async API workflows in n8n get messy fast.

Timeouts, rate limits, unstable endpoints, CRM sync delays, retries…

I kept running into the same problems over and over.

So I built a modular, safe, reusable async batch processor — and this post explains the pattern.

1. The Core Problem

Normal loops in n8n fail when you push large datasets:

Random HTTP timeouts
APIs enforcing strict rate limits
Retry logic is inconsistent
Long chains become unmaintainable
Webhook-based CRMs randomly drop requests

I needed something predictable and production-safe.

2. The Architecture (High-level)

This pattern has 5 independent responsibilities:

SplitInBatches → Iteration controller
API Request Wrapper → Safe executor
Retry Engine → Idempotent retries
Dynamic Wait Node → Rate-limit aware sleeps
Unified Output Contract → Consistent structure

A clean pipeline:

Items → Split → Safe Execution → Retry → Dynamic Wait → Output

yaml

3. Safe HTTP Executor (Core Logic)

json

{
"status": "success",
"duration": 128,
"response": { "id": 123 }
}
yaml

This guarantees:

No broken items
No partial failures
Normalized contract for every loop
Predictable behavior in AI agents, CRMs, and bulk API workflows

4. Retry Engine

Retries are based on:

Timeout detection
HTTP error classes
API vendor signals
Exponential wait pattern
Circuit-breaker protection

A simplified sample:

json

{
"retry": {
"attempt": 2,
"max": 3,
"reason": "429 rate limit"
}
}
yaml

5. Dynamic Wait Engine

Instead of using the static Wait node:

Wait 1 second → Still rate limited → Fail.

diff

Dynamic Wait computes:

Vendor’s retry-after value
Backoff curve
High-load protection

Example:

json

{
"waitMs": "={{ $json.rateWait }}"
}
yaml

6. Normalized Output Contract

Every item returns:

json

{
"status": "success",
"duration": 128,
"response": { "id": 123 }
}
yaml

7. PRO JSON Template (Preview Only)

Short preview (full version is much larger):

json

{
"name": "Async Batch Processor — Core",
"nodes": [
{
"id": "SplitInBatches",
"type": "splitInBatches",
"parameters": { "batchSize": 10 }
},
{
"id": "DynamicWait",
"type": "wait",
"parameters": {
"duration": "={{$json.rateWait}}"
}
}
]
}
yaml

8. What the PRO Version Adds

Full JSON template
Modular clean blocks
Retry-safe HTTP node
Dynamic wait engine
Request isolation
Usage guide
Best practices
Production-ready architecture

Faster debugging.

Enterprise-grade stability.

9. Download the Full PRO Template

👉 PRO version (import-ready):

https://workflowslab.gumroad.com/l/batch-processor-template

Includes:

Full JSON (1500+ lines)
Retry-safe executor
Modular blocks
Rate-limit engine
Usage guide
Best practices

10. Need a Custom Recommendation?

If you want a custom suggestion for your use case (CRM, bots, agents, billing, integrations), send me a message — I’ll recommend the best workflow.

Thanks for reading!

I’ll publish more production-ready n8n patterns soon.