Measurement (Google Analytics 4) loads only if you accept. Privacy
479 production automations architected and shipped since Feb 2025, for real clients across marketing, ops, sales, and finance.
Count and catalog date from src/data/automationsData/automations.json, generatedAt . Updated .
Seven categories of shipped workflows. Click a card to filter the full library below.
Deep-dive writeups with architecture, stack choices, and outcomes. These are the long-form case studies behind selected production systems — separate from the compact library cards below.
Search by name, brief, or tag. Click any card for the full workflow overview — hours saved, stack, and related builds.
Showing 479 of 479
Recurring architecture patterns across the library — with tag counts from the live snapshot.
62 workflows in this library are tagged RAG. They retrieve from a knowledge base, ground an LLM answer in your documents, then write the result back to a CRM, ticket, or chat. Use this when support, sales, or ops needs answers that match your actual policies — not generic model guesswork.
54 builds use multi-agent chains: one agent researches, another drafts, another validates or routes. That split keeps each step inspectable and reduces single-prompt failure modes. Reach for it when a task has clear sub-roles — research, writing, scoring — that should not live in one opaque call.
83 workflows scrape public pages or APIs, then enrich leads, competitor data, or content sources before landing in Airtable, Sheets, or a CRM. Businesses need this when growth depends on fresh external data and the team is stuck doing the same copy-paste ritual every week.
61 automations start from a webhook — form submit, Stripe event, CRM update, custom app ping — and fan out to the rest of the stack. This is the default when you want near-real-time handoffs between tools without polling or manual exports.
79 workflows are tagged Chatbot. They cover intake bots, internal assistants, and customer-facing Q&A that log context and escalate when confidence drops. Fit this when volume is high enough that humans should only touch exceptions.
203 workflows carry a Data Transformation tag — mapping fields, normalizing IDs, merging records, and shaping payloads between systems. Almost every reliable automation library needs this middle layer; without it, integrations break the first time a schema drifts.
Straight answers about the portfolio, n8n scope, pricing ranges, and how to engage.
This library catalogs 479 production n8n automations shipped for real clients between February 2025 and May 2026, spanning marketing, operations, sales, customer service, finance, leadership, and HR. Flagship case studies on this page go deeper on architecture and outcomes for selected builds.
An n8n automation library is a portfolio of workflows that connect apps, APIs, databases, and AI models to run business processes without manual handoffs. Each entry here is a shipped workflow — not a template catalog — with a brief describing what it does, how it is categorized, and when it was built.
Common fits include lead capture and enrichment, proposal and estimate generation, content and SEO pipelines, CRM updates, ticket triage, invoice and expense flows, web scraping with enrichment, RAG knowledge assistants, multi-agent research chains, and webhook-driven integrations between the tools a team already uses.
Engagements are scoped to complexity, integrations, and whether you need a single workflow or a connected system. Focused builds often land in the low-to-mid four figures; multi-workflow libraries, agent systems, and ongoing iteration typically move into five-figure project or retainer ranges. A short discovery call pins scope before any quote.
Most workflows run on n8n (self-hosted or cloud) and connect to tools like Airtable, Google Workspace, OpenAI and other LLM APIs, CRMs, form providers, and custom webhooks. Many include RAG retrieval, multi-agent chains, scraping, or chatbot interfaces depending on the job.
Start from the contact form on the home page or email william@spurlockstudios.com with the process you want automated, the tools involved, and any volume or SLA constraints. Share whether you need a one-off workflow, a multi-system library, or an ongoing automation partnership — that context shapes the first call.
Read the automation writeups on the blog, or bring a process you want off your team's plate.
