Skip to content
Back to Resources
ClaudeSocial MediaIntermediateGuide

Claude Cowork for Social Media Automation: Auto-Posting, Connectors, and Multi-Platform Workflows

Practical playbook for using Claude Cowork to auto-post to Instagram, LinkedIn, X, and TikTok — connector setup, voice-safe drafting, and approval routing for multi-client workflows.

Claude Cowork for Social Media Automation: Auto-Posting, Connectors, and Multi-Platform Workflows

What this guide covers

If you've already read How to Use Claude as Your Social Media Manager Co-Worker, you know the prompting layer. This guide is the next layer: automation. How to wire Claude Cowork to Instagram, LinkedIn, X, and TikTok so the calendar-to-published flow runs without you copy-pasting captions into Buffer one at a time.

Specifically:

  1. The architecture for an auto-publish workflow that doesn't ship voice-bleed garbage
  2. How to set up Cowork connectors for each major platform (least-privilege permissions, security review)
  3. The approval queue pattern that keeps clients in the loop without making you the bottleneck
  4. The Live Artifact monthly client dashboard — Cowork-native deliverable that ChatGPT-based competitors can't replicate
  5. What to log, what to alert on, and how to recover when a platform API misbehaves

Who this is for. Freelance and boutique agency social media managers who are technical-but-not-developers. If you've ever set up a Make/Zapier flow, you can build everything below. If you've never touched an automation tool, start with the SMM cowork basics guide and come back to this one once you've got Claude in your daily workflow.

The architecture in one diagram

[Your content calendar — Notion / Airtable / Google Sheet]
         │
         ▼
┌─────────────────────────────────┐
│ Claude Cowork reads the calendar │  (cron or watcher)
└─────────────────────────────────┘
         │
         ▼
┌─────────────────────────────────┐
│ Apply Brand Voice Cartridge      │
│ (per client, per row)            │
└─────────────────────────────────┘
         │
         ▼
┌─────────────────────────────────┐
│ Draft caption + run brand-voice  │
│ guard skill                      │
└─────────────────────────────────┘
         │
    ┌────┴────┐
    ▼         ▼
[Auto-publish]  [Approval queue]
    │              │
    ▼              ▼
[Platform]     [Client review → publish]

Three things make this safe instead of chaotic:

  1. The cartridge is required at every step. No cartridge = no draft. This kills voice bleed at the source.
  2. The voice-guard runs before publishing. If the draft drifts from the cartridge, it's auto-routed to approval regardless of what the calendar says.
  3. Audit trail is mandatory. Every published post logs the cartridge version, the voice-guard pass/fail, and who approved (if anyone).

Step 1 — Pick your calendar source-of-truth

Before connecting any platform, decide where the calendar lives. Options ranked by SMM workflow fit:

Option Best for Cost Fit with Cowork
Notion Solo / boutique agencies, design-friendly Free tier works Strong — Cowork's Notion connector is mature
Airtable Agencies with structured workflows, multi-client views Free → $20/user Strong — view filtering helps client-specific automation
Google Sheets Maximum simplicity, fastest setup Free Adequate — basic but works
A custom database Agencies with engineering support Higher Overkill for most

For most freelance/boutique workflows, Notion or Airtable is the right choice. The columns you'll need:

  • client — which client this post is for (drives cartridge selection)
  • platform — IG, LinkedIn, X, TikTok, FB
  • scheduled_for — date + time
  • format — carousel, reel, single, thread, etc.
  • topic — 1-line topic
  • hook — the hook line (if you've drafted) OR blank (if Claude should generate)
  • visual_concept — 1-line description
  • pillar — content pillar
  • auto_publish — boolean (defaults to false for new clients)
  • status — draft | ready | drafted | flagged | approved | published | failed

This is the contract between your brain, Claude, and the platforms. Get it right once, reuse forever.

Step 2 — Set up connectors per platform

Claude Cowork ships with first-party connectors for major social platforms. The connection flow is similar across all of them:

  1. In Cowork, open Settings → Connectors
  2. Search for the platform (Instagram, LinkedIn, X, TikTok, Facebook)
  3. Click Connect
  4. Authorize via the platform's OAuth flow
  5. Grant only the permissions you need for the named goal

The least-privilege principle matters. Don't grant DM access if you only need posting. Don't grant analytics access if you only need DMs. If you add new workflows later, expand permissions then — not now.

Platform-specific gotchas

  • Instagram: requires a Business or Creator account linked to a Facebook Page. Personal accounts can't be automated. The Page → IG link must be set up before the connector works.
  • LinkedIn: posting via API requires Company Page admin access (or a Personal connection with elevated permissions). Personal-profile auto-posting is more limited than Company Page auto-posting.
  • X: API access has tier requirements — the free tier is limited; the Basic tier ($100/month from X) is usually needed for serious automation. Factor this into client pricing.
  • TikTok: the connector ecosystem is younger. Some features (auto-publish drafts to client review queue rather than direct publish) may not be available yet. Test before promising clients automation.
  • Facebook: generally easier than Instagram if you only need FB Page posting. If you need IG + FB, set up the FB connector first since IG depends on it.

Security review checklist

Before connecting any platform for a client:

  • Confirm what permissions you're granting
  • Confirm credentials live in Cowork's encrypted store (not in plain text anywhere)
  • Confirm only your Cowork account has access (not shared with team unless explicitly needed)
  • Document how to revoke access (Settings → Connectors → Disconnect, plus revoke on the platform side)
  • Send the client a disclosure note (template below)

Client disclosure note (copy-paste)

Before automating a client's account, send this:

Quick FYI on workflow:

To save time on scheduling and reporting, I've connected your [Platform] account to my Claude Cowork workspace via [Platform]'s official integration. This lets me draft, schedule, and pull analytics from one place instead of manually copying data between tools.

What this means for you:

  • I can publish posts directly from my workflow (you still approve everything that needs approval)
  • I can pull metrics for your monthly report automatically (cleaner numbers, faster reports)
  • Your account credentials stay with [Platform] — I never see your password
  • You can revoke access anytime from your [Platform] settings, and I'll get the same notification you do
  • All actions taken via the connector are logged in my workspace

Let me know if you have any questions.

This disclosure builds trust AND protects you legally. Send it before connecting, not after.

Step 3 — The voice-safe drafting flow

The trap with auto-publishing is voice drift — Claude generates plausible-sounding captions that don't match the client's voice, ships them while you're not looking, and the client notices. The Brand Voice Cartridge system is the antidote.

For every row in the calendar where Claude will draft:

  1. Cartridge is required. Look up cartridges/[client-slug].md and load it into the prompt context.
  2. The caption command runs with the cartridge in context. This is where /caption-instagram (or the platform-specific command) does its work.
  3. The voice-guard runs against the draft. If any flag fires (AI tells, cartridge violations, voice drift, cross-client bleed), the row is auto-routed to approval queue regardless of auto_publish setting.
  4. Only clean drafts auto-publish. Anything the guard flags becomes a manual decision.

This is the structural defense. You can't accidentally ship a flagged draft because the guard short-circuits the auto-publish branch.

Step 4 — The approval queue

When a draft needs approval, it routes to wherever your team works. Options:

  • Slack channel — fastest, scales well
  • Cowork inbox — keeps everything in one place
  • Notion view filtered by status = flagged — works if Notion is your calendar
  • Email — fine for solo, gets noisy at agency scale

Whatever you pick, the approval flow needs:

  • The draft
  • The voice-guard report (what flagged)
  • An approve / change / pass decision primitive
  • An SLA (typically 24-48 hours)
  • A timeout behavior (if no response → mark auto-skip and move on)

Don't auto-publish if approval times out. This is the most important rule. Defaulting to "publish if no one says no" is the path to a client incident. Default to "skip if no one says yes."

Step 5 — Audit trail

Every published post should log:

  • Calendar row ID (for traceability)
  • Platform
  • Final caption text (after any voice-guard fixes)
  • Cartridge version used
  • Voice-guard pass/fail status (and which flags fired, if any)
  • Approval status (auto-published OR who approved + when)
  • Platform response (post URL, post ID, any errors)

Log location can be: a Sheet tab, a Cowork artifact, or a file you back up. The point is that 6 weeks from now when something looks weird, you can answer "what happened on this post" in 30 seconds instead of 30 minutes.

Step 6 — The Live Artifact monthly dashboard (the differentiator)

Live Artifacts are Cowork's persistent, auto-refreshing dashboards. For monthly client reporting, this is the killer feature — your client gets a permalink to a dashboard that always shows the latest month's data without you having to send a new PDF every 30 days.

The dashboard structure:

  1. Top-line KPIs — 4-6 numbers the client wakes up to (with plain-English business framing for each)
  2. Trend charts — engagement rate, reach, follower growth, top-pillar performance
  3. Top + bottom posts this month — auto-pulled, with a manager commentary slot you fill in once per month
  4. The ask — decisions the client owes the manager this month, with approve/discuss/defer primitives
  5. Auto-refresh notes — what updates automatically vs. what's manual entry
  6. Branded — header with client logo + month + theme color

This deliverable is the single biggest perceived-value upgrade you can make to your retainer. Static PDFs feel like 2018; Live Artifacts feel like the platform of 2026. Clients renew faster when they can pull up a live dashboard whenever they want.

Failure modes and recovery

The flows above will fail occasionally. Plan for it.

Failure Detection Recovery
Calendar field incomplete Pre-flight validation Skip row, log error, ping manager
Cartridge file missing Pre-flight Skip row, ping manager
Voice-guard flagged Post-draft Route to approval queue
Platform API failure Post-publish Retry 3x with exponential backoff, then alert
Connector revoked Pre-publish Pause workflow, alert manager, link to reconnection steps
Rate limit hit Post-publish Defer to next available window, log delay
Wrong cartridge loaded (cross-client) Voice-guard catches it Flag as bleed-suspected, route to manual review

Test failure modes before going live. Deliberately misname a cartridge, deliberately leave a calendar field blank, see what your workflow does. If it auto-publishes garbage, fix the validation before connecting a real client.

Build sequence (3 weeks to production)

Week 1 — single client, single platform.

  • Pick the simplest case — one client, one platform, low-stakes content
  • Build the calendar source
  • Wire the connector
  • Run with auto_publish = false for the entire week — every post goes to approval
  • Tune based on what the voice-guard catches and what the client redirects

Week 2 — add a second platform for the same client.

  • Confirm the cartridge applies cleanly across platforms
  • Start auto-publishing the lowest-stakes content (story posts, reactive content)
  • Keep high-stakes content (carousels, video) on approval

Week 3 — second client.

  • This is the real test — does cartridge isolation hold?
  • Confirm no voice bleed between clients
  • Document any per-client overrides
  • After week 3, scaling to all clients × all platforms is mechanical

Cost and rate-limit notes

Platform Realistic posts/day cap Cost layer
Instagram ~25 posts/day before rate limits Free with Business account
LinkedIn ~20 posts/day for Company Pages Free for organic
X ~50 posts/day on Basic tier $100/mo for Basic API access
TikTok Connector limitations apply Free where supported
Facebook ~30 posts/day Free

For an SMM managing 5 clients × 5 posts/week each, you're well within rate limits on every platform except X (where the Basic tier is usually needed). Factor X's API cost into client pricing.

What this doesn't replace

Automation handles the publishing layer. It doesn't replace:

  • Strategy — quarterly KPI plans, content pillars, audience analysis still need a human
  • Crisis comms — anything sensitive escalates to manual
  • Final approval on high-stakes content — campaigns, launches, anything tied to a specific business outcome stays manual
  • Client relationship work — the dashboards and reports support trust; the actual relationship is still your job

The vault gives you the playbook for everything above, but the automation layer is for the execution surface — captions on a calendar, monthly metric pulls, recurring approval batches. The strategic and relational work is where SMMs differentiate, and AI doesn't touch it.

Ready for the full automation playbook?

This page covers the high-level approach. The Social Media Manager Claude Vault ships with the actual connector setup playbook, the multi-platform auto-publish workflow spec, and the Live Artifact monthly client dashboard template — plus 22 other prompts for captions, reports, strategy work, and client comms.

The vault includes the brand-voice-guard skill that catches voice drift and cross-client bleed before publishing, plus the Brand Voice Cartridge system that captures each client's voice in a reusable artifact. The automation layer is only safe with both running.

$39 one-time. Get the vault →

Get weekly AI prompts for Social Media professionals

Join professionals already saving hours every week. Free. No spam.