Teedian: AI Content Operations Engine for Make.com, n8n, Notion
Editorial teams spend roughly 60% of their time on operations. Status updates. Briefing docs. Approval pings. Cross-posting the same article to five platforms. Pulling last week’s numbers into a spreadsheet so someone can decide what to write next. The other 40% is the actual work: voice, story, editing, judgment.
Teedian is the AI content operations engine that flips those numbers. It orchestrates the content pipeline (briefings, drafting, approval, cross-posting, performance tracking) using Claude as the text engine inside Make.com and n8n workflows your team already runs. No new monolithic SaaS. No platform lock-in. The ops layer runs in automation tools you control, and humans stay on voice.
This page covers what Teedian does, what sits inside the engine, why the stack looks the way it does, and how it plugs into an existing editorial workflow.
The problem editorial teams face
A typical editorial team of five to twenty people runs a content calendar across a blog, LinkedIn, a newsletter, and two or three syndication destinations. Every piece needs a briefing, a draft, one or two review passes, publishing, and cross-posting with canonical links pointed at the right URL. Then someone has to check reach and engagement next week so the calendar can adjust.
Most teams handle this with some mix of Notion databases, a shared inbox, Slack threads, and a Google Sheet for metrics. The tools are fine. The work between them is where hours disappear. Editors paste the same brand context into a dozen prompts. Writers rebuild the same briefing format every Monday. Someone cross-posts manually and forgets the canonical URL. Metrics live somewhere nobody looks until the quarterly review.
The failure mode is not creative. It is operational. Teams do not need a better writer. They need the ops layer between the tools to stop eating their week.
What Teedian does
Teedian is an ai content operations engine. In one sentence: it orchestrates briefings, drafting, approval, cross-posting, and performance tracking with Claude doing the heavy text work inside Make.com and n8n scenarios.
The orchestration is the product. Claude is the text model, but the value is the wiring: which trigger fires when, which data gets pulled, which human approves at which step, where the output lands.
What’s in the engine
Teedian ships as five connected components. Each runs as a set of Make.com scenarios or n8n workflows you can inspect and edit.
Briefing Engine. Reads your editorial calendar (Notion database by default) and campaign goals. Pulls the relevant brand guide sections, audience notes, and past posts on the topic. Produces a briefing document Claude can draft from. Editors can edit the briefing before it flows downstream.
Draft Engine. Claude writes the first draft following your voice guide, tone rules, and audience profile. Output includes structured metadata: headline, excerpt, tags, target audience, estimated reading time. The draft lands in Notion with a review task attached.
Review Flow. Human approvals run through Slack, Notion comments, or email, whichever your team already uses. Every revision is versioned. The editor sees a diff, not a mystery rewrite.
Cross-post Engine. One approved article syndicates to LinkedIn, Dev.to, Hashnode, Medium, and X with canonical links pointed at the source. Platform-specific formatting (code blocks for Dev.to, carousel hints for LinkedIn) applied per destination.
Performance Loop. Tracks reach and engagement per post per platform. Feeds insights back into the Briefing Engine so next week’s briefings know what worked.
Why Make.com and n8n, not a monolithic SaaS
Teedian runs on top of Make.com and n8n because those are the platforms editorial teams already use for the rest of their automation. Three reasons this matters.
You already run them. Pulling content ops into the same scenario canvas as your HubSpot syncs and webform handlers means one place to debug, one place to grant access, one set of credentials to rotate. A new dashboard is a new cognitive tax.
No vendor lock-in on a proprietary tool. Make.com scenarios and n8n workflows are portable. If you outgrow a pattern, you fork it. If you want to self-host the orchestration later, n8n supports that natively (see /blog/n8n-self-hosting-guide/ for the production setup).
Visual editing puts non-engineers in control. Your editor or marketer can tweak a trigger schedule, change a platform destination, or adjust a prompt without filing a ticket. That is the difference between content ops that ship and content ops that rot.
For the full comparison between the two platforms at production scale, see /guides/makecom-vs-n8n-production-workloads/ and the German version /guides/make-vs-n8n-vergleich/.
Why Claude under the hood
The text model choice is not neutral. Teedian runs Claude, and specifically Claude Sonnet 4.6 for drafting with Haiku for fast classification work. Four reasons.
German and multilingual output is better than the alternatives. DACH editorial teams need drafts that read as native German, not translated English. Claude’s German handling is the practical winner for this audience, covered in depth in /blog/claude-api-deutsch/.
Tool use produces structured draft metadata reliably. Instead of asking the model to emit JSON and hoping, Teedian uses tool schemas to force the output shape: headline, excerpt, tags, audience, reading time. The draft and its metadata arrive together.
Long context fits the brand guide, past posts, and the briefing in a single call. No retrieval gymnastics. The model sees the full context every time, which means drafts sound like your publication rather than a generic LLM average.
Prompt caching cuts the cost of repeating the brand and voice context on every draft. The system prompt with the voice guide and audience definition is cached. Per-article calls pay only for the unique briefing plus output tokens.
The stack
- Make.com scenarios for light sync work: webhooks, quick triggers, platform-specific posting.
- n8n workflows for heavier orchestration: the Draft Engine, the Performance Loop, anything that needs self-hosting for data-sensitive clients.
- Notion as the editorial database: calendar, briefings, drafts, brand guide, metrics dashboard.
- Claude API as the text engine. Sonnet 4.6 default, Haiku 4.5 for classification and triage.
- Slack for approval notifications and review threads.
- Platform connectors for LinkedIn, Dev.to, Hashnode, Medium, X, your CMS.
The dashboards live in Notion by default. Teams that want a lightweight web UI get one as an optional add-on.
Who it’s for
Teedian fits four patterns.
Small-to-mid editorial teams of two to twenty people running a regular publishing cadence. The ops overhead is high enough to matter, and the team is small enough that a dedicated ops hire is not on the cards.
Content agencies serving multiple brands with distinct voice guides. Each brand gets its own configuration. The engine handles brand switching per pipeline run.
Solo founders with a content pipeline they cannot let drop. Founders who write as their distribution channel and cannot afford the calendar to slip when the week gets busy.
Marketing teams in DACH Mittelstand who need German output, European data handling, and a stack they can audit.
What it doesn’t do
Three things Teedian does not pretend to cover.
It does not generate content autonomously with no human in the loop. Every draft passes through a human approval gate before publishing. The engine removes ops, not judgment.
It does not replace the writer or the editor. The voice, the angle, the call on what matters this week, those stay human. Claude drafts. The editor edits. The engine moves the work between the two faster.
It does not lock you into a proprietary platform. The Make.com blueprints and n8n workflows are yours to inspect, fork, and modify. If you fire Teedian tomorrow, the automations keep running until you decide otherwise.
Plugging into your existing workflow
The install pattern is deliberately boring.
Install the Make.com blueprints and n8n workflows into your accounts. Connect Notion, the Claude API, your syndication platforms, and Slack. Configure your brand guide as a Notion page the engine reads on every draft call. Run a first pipeline on a test article. First run lands within a day of kickoff.
The engine picks up your existing editorial database rather than asking you to migrate. Calendar stays in Notion. Brand guide stays in Notion. Metrics flow back into Notion. No tool switching for the team.
For teams already running AI agents in n8n, Teedian composes with existing workflows. The agent patterns in /blog/n8n-ai-agent-workflows/ plug directly into the Draft Engine as custom pre-processing steps.
Typical rollout pattern
Week one: install, connect platforms, configure the voice guide, dry-run on two test articles.
Weeks two and three: run the full pipeline on two or three article types (long-form blog, LinkedIn post, newsletter section). Feedback loop on voice match. Editors flag what sounds off, the voice guide gets tightened.
Week four onwards: expand to the full content calendar. At this point the team sees the ops time drop. Hours that were going to status updates and cross-posting shift back to voice, editing, and strategy.
Most teams reach steady state by the end of week four. Agencies with multiple brands run a staggered rollout, one brand per week.
Pricing and engagement
Teedian as a product: pricing is on teedian.com. Self-serve install with the published blueprints and workflows.
Custom implementations for agencies and larger editorial teams: freelance engagement, typically four to eight weeks, covering install, voice configuration, custom platform connectors, and team handover.
Open source components are available for the technical pieces where it makes sense: the prompt caching patterns, the structured metadata tool schemas, the cross-posting formatter logic.
Data handling
For DACH and EU clients who have to answer data questions before they can buy.
Your content stays in your tools. Notion remains your database. Google Drive remains your asset store. Teedian moves data between these tools. It does not introduce a new storage layer you have to audit.
Claude API calls run under Anthropic’s AVV and support EU-region processing where available. No training on client content is part of the standard API terms.
Self-hosting the orchestration layer on n8n is available for teams that need it. The Claude API calls still go to Anthropic, but every other piece of the pipeline can run on infrastructure you control.
How it was built
Teedian started as Rene’s own content pipeline. Make.com scenarios and n8n workflows running against a Notion editorial database, with Claude handling drafts and cross-posting. The patterns were tested at real publication rhythms (daily LinkedIn, weekly blog, multi-platform syndication) before they were packaged into the product.
The automation patterns in /blog/automate-content-publishing-make/ cover the Make.com side of the Cross-post Engine. The agent composition patterns in /blog/n8n-ai-agent-workflows/ cover how the Draft Engine chains model calls inside n8n. Those blog posts are the technical source material behind the product.
Content ops are the silent killer of editorial teams. Teedian gives you back the hours so the team focuses on voice, not ops.