Editorial Calendar

The Editorial Calendar is your project's timeline. Instead of keeping article topics, research, and publishing dates in spreadsheets, you place events directly on a project-bound calendar — with date, type, optional links to articles, keywords, or tracking runs. Every project has its own calendar, every event is team-scoped, and everything is readable and writable via the API. That makes the calendar the sync point between editorial, SEO, and automation.

What it can do

• Per-project calendar — GET /v1/projects/{project}/calendar lists every event of a project. Each project has its own editorial pipeline.
• Event types — article slots, keyword research, publish dates, tracking runs, outreach actions, free notes. The type is freely taggable.
• Arbitrary links — an event can point to an article, a keyword, a tracking run, or an external URL. The reference stays valid through status changes.
• CRUD via API — create, change, delete events through PUT/DELETE /v1/calendar/{id}.
• Team scoping — cross-team lookups return 404, no existence leak.
• Combinable with Automation — Autopilot pipelines can create events (e.g. "every Tuesday, 1 article for cluster X").

When to use

• You're planning content pipelines with clear publish dates.
• You want tracking runs (Rank Tracker, AI Visibility) to run on a deliberate rhythm rather than ad-hoc.
• You work with editors who don't click through the tool — they only see the calendar; you orchestrate behind it.
• You need an audit trail: "when was what published / tracked / researched?".

Workflow

1. Pick a project — the calendar is always project-bound, no team-global view.
2. Create event — POST /v1/projects/{project}/calendar with date, type, title, and an optional reference (e.g. article_id).
3. Fetch the list — GET /v1/projects/{project}/calendar for UI rendering or external tools (e.g. Notion sync).
4. Move/edit — PUT /v1/calendar/{id} changes date, title, status.
5. Resolve or delete — DELETE /v1/calendar/{id} removes the event for good.

Tip: combine with Automation — a pipeline can automatically trigger an AI Content Editor task when a calendar event is created.

API

Example body for POST:

{
  "date": "2026-05-12",
  "type": "article_publish",
  "title": "Stoßdämpfer wechseln — Guide",
  "article_id": 8421
}

Credits & Limits

• Free — all calendar endpoints are credit-free. Only the connected actions (article generation, tracking runs) consume credits in their respective modules.
• Team scoped — all reads/writes go through the currentTeam() filter; cross-team → 404.
• No hard event cap — the calendar scales via pagination in the frontend.
• Reference integrity — if a linked article or tracking run is deleted, the calendar event remains (with an invalid reference, marked as "orphan entry" in the UI). You decide whether to remove it or keep it as an audit trail.
• Bulk creation — for large editorial plans we recommend creating events programmatically via the API rather than one-by-one in the UI; the POST endpoint has no hard frequency throttle beyond the standard Sanctum throttle.

Related modules

• AI Content Editor — calendar events can point to article drafts and schedule their publishing.
• Automation — Autopilot and pipelines can create, change, or trigger on calendar events.
• Rank Tracker — make planned tracking runs visible as calendar events.
• Storylines — storyline stages map 1:1 to calendar slots.