n8n Social Media Automation: Post to TikTok, Instagram and Facebook

n8n social media automation usually means wiring together separate nodes and credentials for every platform a workflow needs to reach. With IMMA AI, one HTTP Request node calling a single social media API can post to TikTok, Instagram, Facebook Pages and Threads, while IMMA AI checks each platform's limits and handles TikTok's required approval step.

Can you automate social media posting with n8n?

Yes. n8n already ships community and native nodes for individual platforms, but most teams end up combining several of them plus custom code for anything TikTok related, since TikTok's Content Posting API requires a real consent screen rather than a background API call. An n8n workflow built against IMMA AI's social media API instead uses one credential and one request shape for all four platforms: a trigger node (schedule, webhook, or an AI agent node) builds the caption and media, an HTTP Request node posts it to IMMA AI, and IMMA AI queues Meta platforms directly while generating a hosted approval link for any TikTok target. The workflow can then wait for a post.approved webhook or poll GET /v1/posts/{id} before marking the automation step complete, without the workflow itself ever needing to render a TikTok consent screen.

How do you connect n8n to a social media API?

IMMA AI's REST API and MCP server are currently in preview. A typical n8n workflow adds an HTTP Request node configured with the IMMA AI API base URL and a workspace API key stored as n8n credentials, then sends a JSON body with the caption, media URLs, and target platforms to POST /v1/posts. For content built by an AI agent inside the workflow (for example an n8n AI Agent node using Claude or GPT), the same request can be sent through IMMA AI's MCP server instead of the REST endpoint, using the create_posts_batch tool to queue up to 31 drafts in one call. Because IMMA AI validates media format and platform quotas before queuing, a failed request returns a specific reason such as a quota limit or an unsupported media type, which n8n's error-handling nodes can branch on directly instead of guessing from a generic HTTP error.

What can an n8n workflow post to TikTok safely?

An n8n workflow can queue a TikTok post through IMMA AI, but it cannot make that post go live on its own, by design. TikTok requires the account owner to preview the exact video and caption and choose a privacy setting before anything publishes through the Content Posting API, so IMMA AI always creates a hosted approval link for TikTok targets rather than accepting a privacy choice from the workflow, even if the request that built the draft came from a fully autonomous AI agent node. The n8n workflow's job is to prepare the draft, the media, and the caption, then either wait for the post.approved webhook or simply let the account owner approve later from Telegram on their own schedule, with no further action needed from the workflow itself. This keeps a fully automated content pipeline compliant with TikTok's review rules without the n8n workflow needing any TikTok-specific consent logic of its own, and without exposing the account owner's TikTok login to the automation.

n8n automation steps with IMMA AI

Step	n8n node	What happens
1	Trigger (Schedule, Webhook, or AI Agent)	Builds caption, picks media, chooses target platforms
2	HTTP Request	Calls POST /v1/posts with the draft and targets
3	IMMA AI (server side)	Validates media and quota, publishes to Meta, creates a TikTok approval link if needed
4	Wait / Webhook	Workflow waits for post.approved or polls GET /v1/posts/{id}
5	IF / branch	Handles published, pending_approval, or failed differently

How it works

IMMA AI's REST API and MCP server share the same posting logic used by the dashboard composer, so an n8n workflow gets the same platform validation and TikTok approval flow a human using the dashboard would. See the social media API page for the full request and response shape, or the approval workflow page for how the hosted TikTok link works end to end.