Social creation and publishing
Draft channel-specific posts from current business context and publish them through Zernio MCP.
Zernio already holds the social accounts you have connected — X, LinkedIn, Instagram, TikTok, and others. Rather than re-authorizing each network inside Work on Repeat, you paste one Zernio API key and the routine publishes through it.
What you get: channel-ready posts with a trace of drafts, approvals, and any completed publishing actions.
Prerequisites
- A Zernio API key, pasted under Connections → Zernio. The key is verified
immediately against
GET /v1/accounts; a key Zernio rejects is never stored. - At least one active account in Zernio. The dashboard lists each connected account with its platform, handle, and status, read live from Zernio.
Configure it
Start from the template
Routines → New routine → Social creation and publishing. Suggested
schedule: 0 11 * * 1,3,5 — 11:00 on Monday, Wednesday, and Friday.
Set campaign, for example August product education, and reference it as
{{campaign}}.
Say what "channel-appropriate" means
A single post rewritten three ways is not the same as three posts. Spell out the shape of each channel you publish to: length, tone, whether links belong in the body, and what a good opening line does. Name the accounts by handle so the routine cannot invent one.
Also state what must never be posted: unreleased features, customer names, unapproved metrics, and any claim you are not prepared to defend publicly.
Decide draft-only or publish
This is the decision that matters.
- Draft-only — enable Zernio's read tools, leave publish tools disabled. The result contains posts you copy out. Safe, and the right first step.
- Publish — enable the publish tool and grant automatic execution
explicitly. Every publish attempt is recorded as a
tool_callandtool_resultin the run trace.
Run draft-only for a few cycles before granting publish. The routine's voice usually needs two or three rounds of instruction edits.
Prove it, then activate
The manual run is where you find out whether the posts sound like you. Read them as posts, not as output.
Tuning
- Same post every cycle. Give the routine a source of change — a variable carrying this week's theme, or a tool that reads recent product or blog activity. Without new input, a recurring writer repeats itself.
- Publishing at the wrong hour. The schedule fires in the routine's IANA timezone. Set it to your audience's timezone, not your own.
- Partial failure. If one channel fails, the run can still succeed with the others published. Ask for an explicit per-channel status list in the result so the trace and the outcome agree.