Skip to content

n8n social media automation

n8n social media automation can be built with a single HTTP Request node that publishes or schedules posts across Twitter, Instagram, LinkedIn, TikTok, YouTube, Pinterest, and more.

n8n HTTP Request node POST example
Method:  POST
URL:     {{API_BASE_URL}}/v1/posts

Headers:
  x-access-key: YOUR_API_KEY
  Content-Type: application/json

Body (JSON):
{
  "content": "A short example update.",
  "platforms": [
    { "platform": "twitter", "accountId": "YOUR_ACCOUNT_ID" }
  ],
  "publishNow": true
}
Illustrative request
Example line 1

Method: POST

Illustrative request
Example line 2

URL: {{API_BASE_URL}}/v1/posts

Illustrative request
Example line 3

Headers:

This guide shows the exact request to configure, how to choose between immediate publishing and scheduling, and how to check each step before you run the workflow.

What you can build with n8n social media automation

Several practical patterns fit this setup. An AI node can draft copy, a review step can approve it, and the HTTP Request node can then publish it. A channel upload event can trigger a Cross-post flow to other destinations, with the workflow mapping the new video details into the post content as an illustrative example. Rows from a database or spreadsheet, such as Notion, Airtable, or Google Sheets, can drive scheduled publishing when they become due. Private flows can also keep drafting, review, and publishing steps under your own control. Each pattern starts the same way: an event produces a payload, the HTTP Request node sends it, and the response is checked before the workflow continues.

Why use this approach with n8n

Self-hosted automation means you run n8n on your own infrastructure and keep control over your data and workflows. HTTP node integration means you do not need a custom node: the HTTP Request node can send the documented POST request directly. AI-friendly workflows means you can combine AI nodes for drafting and review with the HTTP Request node for publishing, keeping the publish step explicit and inspectable. Check the deployment choice first: if you run n8n yourself, confirm the workflow can reach the API base URL and that the API key is stored as a credential rather than typed into the body. If you use cloud n8n, confirm the same reachability and credential handling. In both cases the request contract is identical.

How to set it up

Step one is to obtain an API key and keep it ready for the header configuration. Step two is to add an HTTP Request node to your workflow, set the method to POST, and set the URL to the exact path shown in the worked example below. Step three is to configure the headers and body: add x-access-key with your API key, set Content-Type to application/json, and set the JSON body to your post payload. Before running, check three failure points: the method is POST and not GET, the path ends with /v1/posts exactly, and the body is valid JSON with content and platforms present. If any of those checks fail, fix the node configuration rather than changing the contract. The field map and worked example below give the exact values to compare against.

Worked example: POST request for immediate publishing

The worked example below shows the complete HTTP Request node configuration for immediate publishing. Replace the placeholder API key and accountId with your own values, keep the header names exactly as shown, and keep publishNow set to true for immediate delivery. After sending, inspect the response in the node output before adding downstream steps, because the source contract for this page does not define a response body or status codes. If the request fails, check the header spelling first, then the JSON syntax, then whether accountId matches a connected account for the platform you selected.

Scheduling with scheduledFor versus publishNow

Use publishNow when the workflow should publish immediately, as in the worked example. Use scheduledFor when the workflow should schedule delivery for a later time, for example when a row in Notion, Airtable, or Google Sheets becomes due. The source does not define how publishNow and scheduledFor interact if both are present, so verify the intended behaviour in the current API documentation and check the payload preview before execution rather than assuming precedence. A common failure is scheduling from a spreadsheet while leaving the payload unchanged from an immediate-publish example. Another failure is supplying scheduledFor in a format the API does not accept; if the request is rejected, check the current API documentation for the accepted format before changing the workflow logic.

Is there a native n8n node?

There is no native n8n node documented for this integration. Use the HTTP Request node instead, which gives you full access to the REST API through the exact POST request on this page. If you later find a community node, treat it as a separate integration and compare its request fields against the contract here before adopting it.

Can I run this self-hosted?

Yes. n8n is open source and self-hostable, and the same API request works from cloud n8n or your own server. For self-hosted automation, also confirm that your server can make outbound HTTPS requests and that secrets are stored securely.

Can I schedule posts from n8n?

Yes. Pass scheduledFor in your request body and the API handles delivery at the time supplied. Verify the accepted time format in the current API documentation and test with a non-critical post before using scheduling for time-sensitive campaigns.

Request field map for POST /v1/posts
Field or headerLocationExample valuePurpose
x-access-keyHeaderYOUR_API_KEYAPI key sent with the request
Content-TypeHeaderapplication/jsonDeclares the JSON request body
contentBody"Hello from n8n!"Post text
platformsBodyArray of platform targetsDestinations for the post
platforms[].platformBody"twitter"Platform identifier for one target
platforms[].accountIdBody"YOUR_ACCOUNT_ID"Connected account identifier for one target
publishNowBodytruePublish immediately
scheduledForBodyTime value supplied in the requestSchedule delivery instead of immediate publishing

Example values are placeholders from the source example; requiredness and types beyond the example were not supplied in the source contract for this page.

Failure and decision matrix
DecisionConfigurationCheck before running
No native node availableUse HTTP Request node with POST {{API_BASE_URL}}/v1/postsMethod is POST and path ends with /v1/posts
Cloud n8nSame request contract as self-hostedWorkflow can reach the API base URL and the key is stored as a credential
Self-hosted n8nSame request contract as cloud n8nServer can make outbound HTTPS requests and secrets are stored securely
Immediate publishingSet publishNow to truePayload preview shows publishNow as intended
Scheduled publishingPass scheduledFor in the bodyPayload preview shows scheduledFor; verify publishNow interaction in current documentation
Missing or wrong keyFix the x-access-key headerHeader name is exactly x-access-key and the placeholder has been replaced
Invalid JSON bodyFix content and platforms fieldsBody parses as JSON and accountId matches a connected account

Response body, status codes, and error contract were not supplied in the source for this page; inspect the node response and current API documentation when a request fails. Interaction of publishNow and scheduledFor is not defined in the source.

Frequently asked questions

Is there an n8n node for this integration?

Not yet. The documented approach uses the HTTP Request node, which gives you full access to the REST API through the exact request described on this page.

Can I run this self-hosted?

Yes. n8n is open source and self-hostable. The same API request works whether you call it from cloud n8n or your own server, so self-hosted automation does not require a different contract.

Can I schedule posts from n8n?

Yes. Pass scheduledFor in your request body instead of relying only on publishNow for immediate delivery. The source FAQ states that delivery is handled at the time supplied in scheduledFor; exact timing behaviour and the accepted time format should be checked against the current API documentation before relying on it for time-critical posts.