Most "social media automation" stops at scheduling. You still write every post by hand, then paste it into a queue. The writing is the bottleneck, and a scheduler does nothing to fix it.

The real unlock is connecting an AI content API to an automation tool like n8n. Then a single trigger can generate on-brand posts, format them per platform, and drop them into a publishing queue, all without you opening a blank editor. This guide walks through building that workflow end to end.

Why n8n instead of a built-in scheduler

n8n is an open-source workflow automation tool. Think of it as visual glue between APIs: a trigger fires, data flows through nodes, and each node does one job. It's a strong fit for content automation for three reasons:

  • It's API-native. An HTTP Request node can call any REST endpoint, so a content API plugs straight in.
  • It branches. One topic can fan out into LinkedIn, X, and a newsletter in parallel, each with its own formatting.
  • You own the logic. Approval steps, delays, and conditionals are yours to define, not locked inside someone else's product.

What you'll build

A workflow that runs on a schedule, generates a platform-native post from a topic, and routes it to a review queue before anything goes live:

  1. Schedule trigger fires every weekday morning.
  2. Pick a topic from a list (a spreadsheet, Airtable, or a static set in n8n).
  3. Call the content API to generate a post tuned to your brand voice.
  4. Format the result and send it to a review channel.
  5. Publish on approval through your platform of choice.

Step 1: Set your brand context once

Before any automation, configure your workspace so generated content sounds like you, not generic AI. With supapost you point the brand detector at your URL and it extracts voice, tone, industry, and audience automatically. That context is then applied to every API call, so your n8n workflow never has to pass brand instructions manually.

Step 2: Add the Schedule trigger

In a new n8n workflow, add a Schedule Trigger node. Set it to fire on the cadence you want, for example weekdays at 8am. This replaces the "remember to post" reminder that never works.

Step 3: Generate the post with an HTTP Request node

Add an HTTP Request node and point it at the content generation endpoint. The body carries the content type, platform, and topic. Brand voice is already attached to your workspace, so the request stays small:

POST https://api.supapost.ai/api/v1/content/generate
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

{
  "type": "social",
  "platform": "linkedin",
  "topic": "{{ $json.topic }}",
  "tone": "professional"
}

The {{ $json.topic }} expression pulls the topic from the previous node, so the same workflow works for any subject you feed it. The response comes back ready to use:

{
  "type": "social",
  "platform": "linkedin",
  "content": "Most teams treat content like arts and crafts...",
  "variations": ["...", "..."],
  "hashtags": ["ContentStrategy", "Automation"]
}

Step 4: Fan out to multiple platforms

Here's where n8n beats a single-tool scheduler. Duplicate the HTTP Request node and change one field. The same topic becomes a native post for each channel:

{ "type": "social", "platform": "x", "topic": "{{ $json.topic }}" }

X gets a punchy, character-limited version. LinkedIn gets a longer, structured one. Run them in parallel branches and you produce a full cross-platform set from one topic in a single execution.

Step 5: Route to a review queue

Automation should not mean posting unread. Add a node that sends each draft somewhere you'll actually see it, a Slack channel, an email, or a row in a tracking sheet. Include the generated content and its variations so you can pick the best one:

New post draft for review:

{{ $json.content }}

Variation 2: {{ $json.variations[0] }}
Hashtags: {{ $json.hashtags.join(" ") }}

This keeps a human in the loop. The AI handles production, you handle judgment. The bottleneck shifts from "I have nothing to post" to "which of these good drafts do I want."

Step 6: Publish on approval

For the final step, connect the platform you publish through. That might be a native social integration, a scheduling tool's API, or a buffer in your own database. Trigger it from an approval action, a thumbs-up reaction in Slack, a checkbox in your sheet, so nothing goes live until you say so.

Take it further

Once the core loop works, the same pattern extends naturally:

  • Repurpose long-form. Add a branch that calls the repurpose endpoint to turn a published blog post into a week of social content.
  • Generate replies. Watch for new comments and call the API with a reply type to draft contextual responses for approval.
  • Per-client workflows. Agencies can clone the workflow per workspace, each with its own brand voice and API key, so every client stays on-brand.

The bigger picture

A scheduler moves work around. An AI content API connected to n8n removes work entirely. You stop being the person who writes every post and become the person who designs the system that does. That shift, from manual production to supervised automation, is what lets a one-person team operate like a content department.

Start with one platform and one daily topic. Get the generate-review-publish loop running, then add branches as you trust it. Within a week your social presence runs on autopilot, and you only show up for the part that needs a human: the final call.