The posts that would ship if someone had a spare afternoon every week.
AutoJet builds this as an n8n workflow behind your content calendar, not a separate app to log into. A trigger — a schedule, or a new row in the sheet or calendar you already plan content in — starts the run. A Claude skill drafts the caption and hashtags in your brand voice from a brief you give it (topic, key point, tone), or reformats a caption you've already written to fit each platform's own constraints: character limits, hashtag conventions, mention formatting. The draft lands in an approval queue — Slack, email, or a shared doc — before anything posts, unless you'd rather it post straight through on schedule.
Once approved, the workflow posts through each platform's own API — Instagram, LinkedIn, X, Facebook, whichever you actually run — and logs what went out, where, and when. Cross-posting isn't copy-paste: each platform gets a version fit to its own constraints, not the same caption trimmed until it fits.
What this doesn't do: generate video or design assets from scratch. It handles the words, the schedule, and the posting. If you're already producing the visual content elsewhere, this is the layer that gets it out the door on time, everywhere, logged — not another tool you have to remember to open.
Manual posting vs the workflow, in practice
Whoever has five minutes free writes, reformats, and posts to each platform by hand. Works until nobody has five minutes.
A Claude skill drafts from your calendar and brand voice, formats per platform, waits for approval if you want it, then posts and logs itself — on schedule, every time.
We don't replace your content calendar or your voice. We build the posting layer between the plan and the platforms.
How a social automation workflow ships
Map your calendar and voice → fixed scope → build the draft-and-post path → test on real content → hand off ownership.
- 01MapYour calendar, voice, and approval preference
- 02ScopeFixed price before build
- 03BuildSkill + platform API wiring
- 04TestAgainst real drafts, not a demo post
- 05HandoffWorkflow + skill files, yours
Connects to what you already use
No new content tool to learn. The workflow sits behind the calendar and platforms you already run.
Anatomy of a post
Every draft is checked before it goes anywhere — either by a person, or against your rules, never blind.
Goes out on schedule, formatted per platform, logged
Flagged back with the reason — never posted unreviewed
When this makes sense
This earns its keep when posting consistently is the actual bottleneck — not a shortage of things to say, but nobody has an afternoon free every week to format and post everywhere it needs to go.
Built for teams that already have a content rhythm — a calendar, a set of topics, a brand voice — and need the mechanical part handled: drafting to spec, formatting per platform, posting on schedule, without someone doing it by hand every time.
If the bottleneck is the writing itself rather than the posting, a Claude custom skill on its own might be the smaller, cheaper build — see Claude custom skills.
Illustrative pilot · not a named client
A small team wrote good content, but posting fell to whoever had five minutes free — inconsistent, and rarely on every platform at once. We built a workflow from their existing content calendar: a Claude skill drafts platform-specific versions from each topic, a Slack approval step catches anything off-brand, and approved posts go out on schedule, logged. The calendar stopped being aspirational.
This sounds like you if
- You have a content calendar or backlog that never gets fully posted
- The same caption gets manually reformatted for every platform, every time
- Posting happens whenever someone remembers, not on a schedule
- You want an approval step before anything goes out — not full autopilot
- Multiple platforms means multiple logins and multiple manual posts
- You've outgrown a basic scheduler tool but don't need a full social media team
What you get
- Discovery call to map your content calendar, brand voice, and approval preference
- Fixed-price workflow built and tested on real drafts before going live
- Connected to the platforms you actually post to
- Every post logged — what went out, where, when
- Full ownership: workflow export, skill files, logs
- Optional retainer to add platforms or refine the skill later
Pricing
$300 starting, fixed after a discovery call
Need more than one build? See the Custom plan for multi-system work.
Questions about social media automation
We work from a calendar or brief you provide — topics, key points, tone. The skill drafts and formats from that; it's not inventing what to say about your business from nothing.
Yes — that's the default. A Slack, email, or doc approval step sits before anything posts. Full autopilot is available if you'd rather skip that step.
Whichever you actually run — Instagram, LinkedIn, X, and Facebook are the common ones. If a platform has a posting API, we can usually wire it in.
No. This handles drafting captions, formatting per platform, scheduling, and posting — not producing the visual content itself.
Workflows fail loudly: a broken post trips the workflow's Error Trigger and flags it, instead of silently dropping.
Yes. Workflow export, skill files, and logs — same ownership model as our other builds.
Want this scoped for your stack?
Fixed-price proposal after a short discovery call — no open-ended retainers to start.