n8n-nodes-invisible-api

One node between your n8n workflows and the social platforms behind them — publish and schedule Instagram and X content, track delivery, and pull Instagram account insights.

InvisibleAPI is a single layer over the social platforms. Today it covers Instagram and X publishing plus Instagram account insights; Google and Facebook publishing, broader insights and further platforms are on the way — this node grows with the API.

Maintained by the InvisibleAPI team. Questions and support: support@invisibleapi.ai.

Install

On self-hosted n8n: Settings → Community nodes → Install, then enter:

n8n-nodes-invisible-api

Full instructions: n8n community nodes installation guide.

What you can build

Publish a content calendar, and know whether it landed

⏱  Schedule Trigger (daily, 9am)
  ↓
📄 Google Sheets: read today's row (caption + image URL)
  ↓
📤 InvisibleAPI: Publish Job → Create (Instagram + X targets)
  ↓
⏳ Wait (2 min)
  ↓
🔎 InvisibleAPI: Publish Job → Get (the returned id)
  ↓
🔀 IF status = failed  →  💬 Slack: alert the team

Cross-post every new blog article

📰 RSS Feed Trigger (your blog)
  ↓
🤖 AI node: write a 280-character version of the title + summary
  ↓
📤 InvisibleAPI: Publish Job → Create (X target, text-only)

Weekly Instagram performance report

⏱  Schedule Trigger (Mondays)
  ↓
👥 InvisibleAPI: Social Account → Get Many (provider = Instagram)
  ↓
📈 InvisibleAPI: Insight → Get Instagram Account Insights
     (metrics: reach, views · period: week)
  ↓
📄 Google Sheets: append row   →   💬 Slack: post the summary

Operations

Credentials

Create an organization API key in the InvisibleAPI dashboard (Organization → API Keys) and paste it into the Invisible API credential.

Things to know

Behaviour that will bite you otherwise:

• The job status you get back is not final. Create returns as soon as the workflow start is recorded. To wait for delivery, follow up with Publish Job → Get on the returned id (a Wait node in between works well) and read status plus deliveries.
• What a post may contain depends on the target. Instagram requires at least one media item — image, video, or several for a carousel. X also accepts text-only posts, caps text at 280 characters, and allows either up to 4 images (no videos) or a single video. Content a provider can't publish is rejected with a validation error before any delivery starts.
• Client Request ID is an idempotency key. Reuse the same value when retrying a failed run; send a new value when you deliberately want to publish identical content again.
• Retry is deliberately conservative. It only requeues deliveries it can prove never reached the provider, and answers with a conflict error when nothing about the job is safely retryable.
• Some Meta metrics need total_value. accounts_engaged, total_interactions, likes and friends are silently omitted from time-series responses. Metric Type sits under Additional Fields and is only sent once you add it there, so add it and leave it on total_value to get them.
• Demographics metrics need Timeframe. follower_demographics and engaged_audience_demographics require it, and Meta gives it precedence over Since and Until.

Metrics is a multi-select of the metrics the backend has verified. Additional Metrics takes a comma-separated list for anything outside it, forwarded to Meta unvalidated. Period is a Meta period: day, week, days_28 or lifetime.

Compatibility

Only the latest published version of this node receives fixes. Upgrade under Settings → Community nodes in n8n.

Development

npm install
npm run lint             # eslint over the whole package, package.json included
npm run format           # prettier --write; CI runs `npx prettier --check .`
npm run typecheck
npm test
npm run build
npm audit --omit=dev     # the one CI check with no npm script
npm run dev              # runs the node against a local n8n

The node is organised so new providers and features slot in without touching what exists:

nodes/InvisibleApi/
  InvisibleApi.node.ts       # description assembly + one entry per resource in RESOURCE_HANDLERS
  descriptions/              # UI parameters, one module per resource
  actions/                   # request building, one module per resource
  methods/loadOptions.ts     # dynamic dropdowns
  transport/                 # auth, base URL and pagination

Adding a resource means: a description module, an action module, and one line in RESOURCE_HANDLERS.

Releasing

Releases are published to npm by the Publish workflow, never from a local machine. The workflow runs n8n-node release, which lints, builds and publishes with an npm provenance statement — a requirement for verified community nodes since May 2026. A plain npm publish is blocked by the prepublishOnly guard.

To cut a release:

1. Bump the version in both package.json and package-lock.json:

   npm version 1.1.0 --no-git-tag-version
   

2. In CHANGELOG.md, rename the ## Unreleased heading to ## 1.1.0 (or add the heading if the release has no Unreleased section yet).

3. Merge those changes to main.

4. Tag the merge commit with the bare version and push the tag:

   git tag 1.1.0
   git push origin 1.1.0
   

The workflow refuses to publish, before anything is built, if the tagged commit is not on main, the tag is not a stable X.Y.Z version, the tag does not match the package.json version, or CHANGELOG.md has no heading for that version. It also verifies afterwards that the version is on npm with a provenance attestation. The one-time npm setup (a Trusted Publisher for GitHub Actions, or an NPM_TOKEN secret for the first release) is described in the comments at the top of the workflow file.

n8n-node release can also drive steps 1–4 locally, but it regenerates CHANGELOG.md from commit messages with auto-changelog, which would overwrite the hand-written changelog. Bump and tag by hand instead.

Contributing

Bug reports, fixes and new operations are welcome. CONTRIBUTING.md covers how to get set up, how the node is organised, the coding standards and what a pull request needs. Open an issue first for anything beyond a small fix, since the node's shape follows the InvisibleAPI backend. Everyone taking part is expected to follow the Code of Conduct.

Security

Do not open a public issue for a vulnerability. Email support@invisibleapi.ai with SECURITY in the subject; SECURITY.md describes what to include, what this repository is responsible for and how the API key is handled.

Resources

License

MIT