
Security News
Critical Security Vulnerability in React Server Components
React disclosed a CVSS 10.0 RCE in React Server Components and is advising users to upgrade affected packages and frameworks to patched versions now.
n8n-nodes-meta-publisher
Advanced tools
Publish to Instagram, Facebook Pages, and Threads (images, videos, reels, stories, carousels) via Meta Graph APIs.

Publish to Instagram, Facebook Pages, and Threads from n8n — including Images, Videos, Reels, Stories, and Carousels — with a single, DRY node.
Built from the official n8n community node starter structure so you can develop, lint, and ship confidently.
One node to publish across Instagram / Facebook Pages / Threads
Create → poll → publish workflow handled for you
Reels, Stories, Carousels (IG) + Photos/Videos (FB) + Text/Image/Video/Carousel (Threads)
Two input styles:
Consistent JSON output (status, IDs, permalinks-ready payloads)
Friendly polling with jitter; configurable timeouts
Facebook Pages
Threads
You’ll need on your development machine:
npm install n8n -g
For a smooth developer experience, see n8n’s guide on setting up the node development environment.
# in your repo
npm i
npm run build
# restart n8n pointing to your custom nodes folder if needed
The project follows the n8n node starter layout and build flow.
Add a credential in n8n called Meta Graph API with an Access Token (prefer long-lived). The node will also attempt OAuth2 if configured in your instance, then fall back to the access token.
Keep tokens in Credentials, not in node fields. This keeps secrets secure and reusable across workflows.
Drag Meta Publisher into your workflow.
Choose Platform:
Choose Operation (e.g., Publish Reel).
Fill required fields (e.g., IG User ID, Media URL, Caption).
Optionally adjust Polling Interval and Max Wait.
Run the workflow.
Example (IG → Publish Image)
1789…https://…/photo.jpgHello from n8n 🚀For advanced batching/programmatic posts, switch Input Source to From JSON Property and point to a JSON object/array in the incoming item (e.g. $json or data). Each object must include at least platform and operation. Any missing field falls back to node UI defaults.
Single job (from $json)
{
"platform": "instagram",
"operation": "publishImage",
"igUserId": "1789...",
"mediaUrl": "https://example.com/image.jpg",
"caption": "Hello world",
"autoPublish": true
}
Multiple jobs (from $json.data)
{
"data": [
{
"platform": "threads",
"operation": "threadsPublishText",
"userId": "12345",
"text": "Posting from n8n đź’š"
},
{
"platform": "facebook",
"operation": "publishFbPhoto",
"pageId": "999999",
"imageUrl": "https://example.com/photo.jpg",
"caption": "FB photo!"
}
]
}
Set JSON Property Path to data for the second example.
Every successful publish returns a consistent JSON shape (fields may vary slightly by platform/operation):
{
"platform": "instagram|facebook|threads",
"type": "image|video|reel|story|carousel|text",
"creationId": "1789...", // IG/Threads container or parent (when applicable)
"children": ["childId1"], // for carousels
"status": "FINISHED|PUBLISHED|READY|ERROR|...",
"published": true,
"publishResult": { "id": "1790..." }, // media/thread object
"videoId": "1234567890" // FB video id when relevant
}
Use this to chain downstream steps (e.g., fetch permalink, store IDs).
This repo uses the same conventions as the n8n node starter:
dist/build, lint, lintfixTypical loop:
npm i
npm run dev # tsc --watch
# In another terminal, run n8n and test
Refer to n8n’s “Using this starter” steps (generate repo, install deps, lint, test locally, publish) for overall workflow.
n8n documents how to run your node locally; follow those instructions to link your development build and iterate quickly.
Issues and PRs are welcome! Please:
npm run lint / npm run lintfix)MIT — same as the official starter.
graph.threads.net) under the Meta umbrella; this node handles it internally — you just choose Threads in the UI.FAQs
Publish to Instagram, Facebook Pages, and Threads (images, videos, reels, stories, carousels) via Meta Graph APIs.
The npm package n8n-nodes-meta-publisher receives a total of 42 weekly downloads. As such, n8n-nodes-meta-publisher popularity was classified as not popular.
We found that n8n-nodes-meta-publisher demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
React disclosed a CVSS 10.0 RCE in React Server Components and is advising users to upgrade affected packages and frameworks to patched versions now.

Research
/Security News
We spotted a wave of auto-generated “elf-*” npm packages published every two minutes from new accounts, with simple malware variants and early takedowns underway.

Security News
TypeScript 6.0 will be the last JavaScript-based major release, as the project shifts to the TypeScript 7 native toolchain with major build speedups.