wyro

Blog · 2026-11-16 · Markdown

Claude for social media managers: a week of work across multiple clients

If you manage social media for several clients, writing isn't what eats up your time. What wears you down is the context switching: remembering how each brand talks, chasing approvals over chat and loading every post into the right account.

Claude helps with all three if you set things up well. Here's a weekly workflow built for a social media manager with several clients: what you prepare once and what you do each day. At the end there's a list of what it doesn't cover.

What you set up once per client

A Claude project with the brief

In Claude you can create a project per client, with instructions and files that carry over to every conversation in that project. That's where the brief goes, so you don't have to repeat it every Monday:

Client: [name]. Sells [what] to [whom].
Tone: [3 adjectives]. Here's how the brand writes: [paste 3 approved posts].
We never use: [words, topics, emojis].
Networks and frequency: [Instagram 3 times a week, LinkedIn once a week].
Approver: [name]. Time zone: [city].
Before scheduling any post, show me the list with date, time and network, and wait for my "yes".

Add the brand guidelines and the price list, if you have them.

One wyro API key per client

Out of the box, Claude doesn't post to social media; it needs a connector. With wyro API, each client gets their own key, and the accounts connected with that key can only be used with that key. That prevents the costliest mistake in the job: posting to the wrong account.

  1. Copy a connector link at https://wyroapi.com/en/guide. Each link includes its own key.
  2. In Claude: Customize → Connectors → Add custom connector. Give it a name that identifies the client and paste the link.
  3. Repeat with a different link for each client, and in each conversation work only with that client's connector.

The key starts in test mode: it lasts 72 hours, simulates all 8 networks and doesn't publish anything. To go live, ask Claude: "Give me the link to connect this client's Instagram". You send that link to the client, who authorizes their account through the network's official login. They never give you their password. The key stays the same; there's no need to reconfigure the connector.

Monday: drafts

Open the client's project and ask for the week:

Let's put together this week's posts. Don't schedule anything yet.
This week's goal: [launch, promotion, event].
Available assets: [public links to the images and videos].
Write [number] posts with different angles. For each one, give me the network, the format,
the first line and the full text. Don't make up data, numbers or testimonials.

Edit in the same chat, post by post. Before sending anything to the client, run each draft through a review: 8 Claude prompts for Instagram includes the one that asks Claude to read the post like someone in a hurry and tell you where they'd stop reading.

Repeat with the next client, in their project.

Tuesday: approval with preview links

Approving by screenshot is slow, and there's always one missing. With a key in test mode, every post Claude publishes is simulated and returns a preview link: a public page showing what the post would look like on each network, with its image and text.

Ask it: "Publish these posts as a test and give me the preview for each one". Then forward the links to the client wherever you already talk. They don't need an account or to install anything: they open the link and reply.

Since the test key lasts 72 hours, this step works best with a separate test key for drafts, and the client's real key for scheduling.

If they ask for changes, you make them in the chat and generate a new preview. Keep the written approval wherever you usually store it; wyro API doesn't record who approved what.

Wednesday: scheduling per client

With the client's "yes," go back to their project and schedule with their real key:

Posts 1, 2 and 4 are approved. Schedule them like this, in [client's city] time:
- Thursday at 10 a.m.: post 1 on Instagram.
- Friday at 6 p.m.: post 2 on Instagram and LinkedIn.
- Monday at 9 a.m.: post 4 on LinkedIn.
Show me the full list before scheduling and wait for my confirmation.

Three details that save you trouble:

The posts go out on their own at the scheduled time, even with Claude closed.

Friday: status check

Before wrapping up the week, ask in each client's project: "How are the posts we scheduled doing?". Claude checks the status of each one: scheduled, published or failed, and if so, the reason, network by network. If one failed because an image link stopped working, you fix that and ask it to publish again.

You can also see it without Claude: the keys you connect with your email show up in your dashboard, with their accounts, recent posts and the status of each one. With your own tools, the same data is available through the API with GET /v1/posts/{id} (documentation).

What this workflow doesn't do

Worth knowing before you promise it to a client:

What it costs

Trying it is free, with no sign-up and no credit card. Publishing for real costs $5 per connected account per month, with unlimited posts per account and no per-user plans: an agency with 10 client accounts pays $50 a month. Founder access covers up to 5 accounts for $15 a month and has limited spots. If you manage more accounts, check out the agencies page or Pricing.

FAQ

Does my client have to use Claude? No. They only open two kinds of links: the connection link, once, to authorize their account, and the preview links, to approve.

Can I handle all my clients with a single key? One key per client is safer: accounts connected with one key can't be used from another, so a post never ends up on the wrong account.

Does this work if I don't use Claude? Yes. The same workflow works with Claude Code, Codex, Cursor or n8n. We cover it in How to automate your clients' social media with AI.

Copy my connector link →

Try it, no sign-up
curl -X POST https://wyroapi.com/v1/sandbox