Your app produces content every day. Posting it by hand to four platforms is the thing that quietly stops happening after week two. This guide covers automating the whole thing from your existing Django backend — one rendered video, one AI caption, every platform, on a schedule you stop thinking about. Everything runs against the same Django API and media bucket from Guide 01. A single management command finds the day's content, renders a branded 1080x1920 video, resolves the caption, and publishes to Instagram, Facebook, YouTube Shorts and Threads from three cron jobs — twelve posts a day for under a dollar a month. What's inside — 33 pages Why a publication layer separate from per-platform post rows is what makes partial failure survivable — Instagram succeeds, Facebook rate-limits, and only Facebook retries Full Meta setup — business portfolios, Page and Instagram linking, and why /me/accounts silently omits the business-owned Page you're trying to post to Instagram's three-call container flow and Facebook's single call, including the polling budget that marks a perfectly good Reel as failed Server-side video rendering with Pillow and ffmpeg — one 1080x1920 H.264 file that every platform accepts unchanged, no screenshots of your app The Reels safe area nobody publishes — the exact insets where the player's own chrome sits on top of your caption AI captions that describe the actual image, with three guardrails and a deterministic fallback so a provider outage never costs you the day's post YouTube Shorts via resumable upload, and the consent screen setting that silently breaks your integration after exactly seven days Threads — tester invites, self-refreshing 60-day tokens, and the two callback endpoints Meta requires and genuinely calls A credential layer with encrypted tokens and per-platform refresh windows, built once and reused for every platform you add after Three layers of idempotency so a double-fired cron never double-posts, and retry that targets only the platform that failed TikTok's two publishing flows and two separate audits, and X's per-post pricing where one wrong decision is $18/month instead of $1.35 — both drawn from current platform documentation rather than a shipped integration, and the guide says which parts are which An appendix mapping 14 symptoms to their actual causes, each one a real debugging session Who this is for Developers running a Django backend who want content going out daily without opening a phone. The code is Django and Python; the API flows, the architecture and every trap apply to any stack. Guide 06 of the React Native + Django series. Instant PDF download.