How Borker Works
A complete picture of Borker's content pipeline: from calendar slot to published post.
Borker runs a content pipeline that starts with a schedule and ends with a published post. Here's the full picture.
The pipeline at a glance
Calendar Slot (date + platform + content type)
↓
Topic Selection (Decision Engine picks from your pool)
↓
Content Generation (Claude writes using your brand voice)
↓
Approval Queue (you review, or auto-approve fires)
↓
Scheduling (Postiz receives the post + optimal time)
↓
Published ✓The pieces explained
Calendar slots
A calendar slot is a scheduled content opportunity: a specific date, platform, and content type. For example: "Wednesday, LinkedIn, thought_leadership post."
Slots are generated by the Weekly Workflow based on your scheduling preferences (how many times per week, which platforms, preferred times). Without calendar slots, the Daily Workflow has nothing to generate.
Topic selection
When a workflow runs, the Decision Engine picks a topic for each calendar slot from your Topic Pools. It scores candidates based on:
- How recently the topic was used (avoids repetition)
- How past content on that topic performed (engagement signal)
- Diversity across the current batch
Each topic can have an angle: a specific perspective the AI should take. This is how you get from "AI in healthcare" to "AI in healthcare: focus on implementation challenges, not hype."
Content generation
Borker calls Claude with:
- Your brand voice config (who you are, how you write, your terminology)
- Your voice attributes (formality, brevity, technical depth, tuned per platform)
- The selected topic and its angle
- A prompt template for the specific platform and content type
- Recent posts context (to avoid repeating yourself)
Claude generates the content. For X threads, it produces a numbered series (1/ tweet text\n\n2/ next tweet). For LinkedIn, a structured post with a hook. And so on.
The approval queue
Generated content lands in the Approval Queue as pending_review. You review it, optionally edit it, and approve or reject.
If you've turned on auto-approval in Settings → Automation, content that passes confidence thresholds skips the queue and goes straight to approved status.
Approval alone doesn't schedule: it marks the content as ready. Scheduling is a separate step.
Scheduling via Postiz
When you click Schedule on an approved item, Borker:
- Calculates the optimal posting time for that platform (based on your preferences and existing schedule)
- Sends the content to Postiz via API
- Postiz queues it and publishes at the selected time
Postiz handles the actual platform connections (OAuth tokens for X, LinkedIn, Farcaster). Borker never holds your platform credentials directly.
Paragraph (blog) publishing
Paragraph posts bypass Postiz and publish directly via the Paragraph API. This requires a Paragraph API key — available on all plans.
The three workflows
Borker has three workflow types that cover different parts of this pipeline:
| Workflow | When to run | What it does |
|---|---|---|
| Daily | Every day | Generates content for today's calendar slots; checks news for reactive content |
| Weekly | Start of week | Plans the week's calendar; identifies content for recycling |
| Process Approved | On-demand | Takes all approved-but-unscheduled content and sends it to Postiz |
Workflows can be run manually from the Workflows page, or scheduled via cron. See Running Workflows.
Your role in the loop
Once set up, your recurring job is:
- Review: Open the Approval Queue a few times a week and approve/edit/reject items
- Schedule: Click Schedule on approved items to push them to Postiz
- Improve: Adjust your brand voice, add new topics, and refine your prompt templates as you see what's working
The more you configure upfront, the less you touch it week-to-week.