Skip to main content
n8n can drive Postsiva in three ways:
  1. Community nodes — n8n-nodes-postsiva package with 43 dedicated nodes (recommended for most workflows)
  2. MCP AI Agent — natural-language tool selection (best for flexible AI workflows)
  3. REST HTTP Request — deterministic calls to specific endpoints (best for custom or uncovered endpoints)
All use the same workspace API key and Pro plan requirements.

​
Prerequisites

  • n8n instance (cloud or self-hosted) with MCP or HTTP Request nodes
  • Pro plan with mcp_enabled (MCP) or api_keys_enabled (REST)
  • Workspace API key: psk_live_YOUR_KEY
  • Social accounts connected in the target workspace
Install n8n-nodes-postsiva from Settings → Community nodes for 43 ready-made nodes: posting, scheduling, drafts, inbox, AI generation, AI Watcher, and brand persona. See the full guide: n8n integration.

​
Option B — MCP AI Agent

Use when the workflow should decide which Postsiva action to take based on incoming data or chat input.

​
MCP server config

FieldValue
URLhttps://mcp.postsiva.com/mcp
TransportStreamable HTTP
Auth headerX-API-Key: psk_live_YOUR_KEY
In n8n’s AI Agent node (or MCP Client tool):
  1. Add MCP server Postsiva with the URL and header above
  2. Connect the agent to your trigger (Webhook, Schedule, Slack, etc.)
  3. System prompt example:
You manage social media via Postsiva MCP tools.
Always confirm before publishing live posts.
Use get_accounts first if platform connection is unclear.
Timestamps for scheduling must be ISO 8601 UTC.

​
Example workflow — Webhook → Agent → Slack

Webhook body: 
{
  "instruction": "Draft a LinkedIn post about our n8n integration and save as draft"
}
Agent tools used: idea_to_content → publish with draft: true

​
Example workflow — Scheduled content

  1. Schedule Trigger — every Monday 08:00
  2. AI Agent — “Generate 3 LinkedIn post ideas from our blog RSS themes and save top one as draft”
  3. HTTP Request (optional) — notify team in Slack with draft link

​
Option C — REST HTTP Request

Use for fixed pipelines where you know the exact endpoint.

​
Shared credentials

Create n8n Header Auth credential:
Header nameValue
X-API-Keypsk_live_YOUR_KEY
Base URL: https://backend.postsiva.com

​
Pattern 1 — Generate and publish

Node 1: HTTP Request — generate copy 
POST /unified/content/generate?workspace_id={{ $env.WORKSPACE_ID }}
Body (JSON):
{
  "idea": "{{ $json.topic }}",
  "platforms": ["linkedin"]
}
Node 2: HTTP Request — publish 
POST /unified/post/text
Body (JSON):
{
  "platforms": ["linkedin"],
  "default_text": "{{ $json.data.linkedin.content }}"
}

​
Pattern 2 — Sync analytics daily

GET /unified/analytics
Headers: X-API-Key
Store $json in Google Sheets, Airtable, or your data warehouse.

​
Pattern 3 — Comment auto-reply (deterministic)

  1. GET /unified/comments?platforms=instagram&limit=5
  2. IF node — filter unanswered
  3. POST /unified/comments/reply?platform=instagram&comment_id={{ $json.id }}&text=Thanks for your comment!
For AI-generated replies, use the MCP AI Agent with get_comments + reply_to_comment instead of hard-coded text.

​
Community nodes vs MCP vs REST

Community nodesMCP AI AgentHTTP Request
SetupInstall n8n-nodes-postsiva + credentialMCP server + agent promptPer-endpoint nodes
Coverage43 Postsiva actionsFull MCP tool catalogAny REST path
FlexibilityMedium — pick node + fieldsHigh — agent picks toolsLow — fixed paths
Best forScheduled posts, inbox, watcherChatbots, variable instructionsCustom / debug endpoints
See n8n integration for community node workflows.

​
Environment variables

Store secrets in n8n credentials or env vars: 
POSTSIVA_API_KEY=psk_live_...
POSTSIVA_WORKSPACE_ID=aaa01a56-e769-44a6-87bf-cf6dfb9e7a27
POSTSIVA_BASE_URL=https://backend.postsiva.com
Reference in expressions: {{ $env.POSTSIVA_API_KEY }}

​
Error handling

ErrorAction
401Rotate or fix API key credential
Plan / 402 messageUpgrade workspace to Pro
Tool success: falseBranch on $json.success; log $json.error
Rate limitsAdd Wait node; reduce schedule frequency
Enable Continue On Fail on HTTP nodes only when downstream logic handles partial success (e.g. multi-platform publish).

​
Example: RSS → AI → schedule

1

RSS Read

Trigger on new blog post URL
2

AI Generate Post from Idea

Postsiva node with idea = post title + summary, platforms = linkedin, threads
3

Create Scheduled Post

Postsiva node with caption from AI output and scheduled_time = next business day 09:00 UTC
4

Notify

Send confirmation email or Slack message with scheduled time
Same flow works with HTTP Request nodes — see REST AI content and n8n HTTP fallback.

​
Security

  • Store psk_live_ keys in n8n Credentials, not in workflow JSON exports
  • Use scoped keys (linkedin_posts read-only for analytics-only workflows)
  • Restrict webhook URLs with authentication

​
Next

Community nodes

Install n8n-nodes-postsiva

Cursor guide

MCP in Cursor

REST AI content

Generate endpoints

Authentication

Scopes and headers