// 02 — Service detail
Most editorial teams spend 40% of their week on tasks that should be three lines in n8n. I build the workflows, deploy them to your stack, and document them so your team owns the result — not me.
// 01 — How it goes
A typical engagement, week-by-week.
Two days shadowing your editorial / SEO / ops team. Tag every recurring task by hours and impact.
Three to seven workflows, scoped with inputs, outputs, edge cases, and the human review point.
Built in your instance, hooked to your stack. Versioned. Test runs against real data.
Loom walkthroughs, written runbooks, a Slack alert for every failure. Then I'm gone.
// 02 — Examples
Six workflows I've shipped in the last twelve months. Yours will look different — these are the shape.
Brief lands in Notion → workflow generates first draft → routes to assigned editor → publishes to CMS on approval.
Pulls Search Console data, summarises winners/losers vs. last week, posts to Slack every Monday 9am.
Form submission → Clearbit enrichment → CRM write → Slack DM to owner with a one-pager.
Identifies pages that lost >20% of traffic, generates an updated brief, queues for editor.
On every new publish, scans 200 most-relevant existing pages and proposes link insertions.
Tags incoming press / partnership / sales emails, drafts a reply, files in the right folder.
// 03 — Under the hood
For the technically curious — a real (sanitised) n8n config from a recent build.
Tell me. I'll send back a one-page sketch of the workflow that would kill it.