Visual no-code workflows that ship to every platform SociaHive supports.

n8n's MCP support is partial — for full coverage, use the HTTP Request node against SociaHive's MCP JSON-RPC endpoint. Save the node as a template once and copy it into new workflows.

# Node type: HTTP Request

Method:        POST
URL:           https://sociahive.com/api/mcp
Authentication: Generic Credential Type → Header Auth
                Name: X-API-Key
                Value: sk_your_key_here

Headers:
  Content-Type: application/json
  Accept: application/json, text/event-stream

Body (JSON):
  {
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "{{ $json.toolName }}",
      "arguments": {{ $json.toolArgs }}
    }
  }

Every Monday 9am, n8n pulls last week's planned content from a Google Sheet, posts each row to the right platform via SociaHive, and sends the team a Slack confirmation with scheduled IDs and the dashboard link to review.

1. 1Trigger: Schedule node fires every Monday at 09:00 in your timezone.
2. 2Google Sheets node reads the 'Week of YYYY-MM-DD' tab — columns: Day, Time, Platform, Caption, Media URL, Account ID.
3. 3Loop over rows: for each, an HTTP Request node calls SociaHive create_scheduled_post with the platform-appropriate payload (LinkedIn longform, Twitter short, Instagram with first-comment hashtags).
4. 4Aggregate scheduled post IDs into a single Slack message: 'Week scheduled — 12 posts across LinkedIn, Instagram, Threads. Review: https://sociahive.com/dashboard/content-scheduler'.
5. 5If any create_scheduled_post fails, route to an error branch that opens a SociaHive support ticket via the same HTTP Request pattern and pings the on-call channel.

{
  "name": "Monday content drop — multi-platform",
  "nodes": [
    {
      "name": "Schedule",
      "type": "n8n-nodes-base.scheduleTrigger",
      "parameters": { "rule": { "cronExpression": "0 9 * * 1" } }
    },
    {
      "name": "Read week sheet",
      "type": "n8n-nodes-base.googleSheets",
      "parameters": {
        "operation": "read",
        "sheetId": "{{ $env.WEEKLY_SHEET_ID }}"
      }
    },
    {
      "name": "Schedule on SociaHive",
      "type": "n8n-nodes-base.httpRequest",
      "parameters": {
        "method": "POST",
        "url": "https://sociahive.com/api/mcp",
        "authentication": "headerAuth",
        "jsonBody": {
          "jsonrpc": "2.0",
          "id": "={{ $itemIndex }}",
          "method": "tools/call",
          "params": {
            "name": "create_scheduled_post",
            "arguments": {
              "platform": "={{ $json.Platform }}",
              "accountId": "={{ $json.AccountID }}",
              "caption": "={{ $json.Caption }}",
              "mediaUrl": "={{ $json.MediaURL }}",
              "scheduledAt": "={{ $json.Day }}T{{ $json.Time }}:00Z"
            }
          }
        }
      }
    },
    {
      "name": "Notify Slack",
      "type": "n8n-nodes-base.slack",
      "parameters": { "channel": "#social", "text": "Week scheduled..." }
    }
  ]
}

n8n decides what to post and when: content from a sheet, a feed or a database, your own rules, your own schedule. SociaHive does the posting. It keeps every post in one calendar, publishes to Instagram, Facebook, LinkedIn, Threads, TikTok, YouTube, Bluesky, Pinterest, a Telegram channel and more, and reports back with webhook events.

Today you connect the two with n8n's HTTP Request node and a SociaHive API key: create a post (POST /api/v1/posts), read its status (GET /api/v1/posts/{id}), find the next free posting slot (GET /api/v1/find-slot) and copy media from a public URL (POST /api/v1/uploads/from-url). For the other direction, add a Webhook node in n8n and point post.published or post.failed at it from Integrations, then Webhooks, in SociaHive.

The SociaHive community node, n8n-nodes-sociahive, is on npm: install it in n8n under Settings, Community nodes. It wraps the same actions (create and get a post, find the next slot, upload media) and adds a trigger for post events. n8n has not verified it yet, so n8n Cloud may not list it; the HTTP Request node works everywhere. It has no DM nodes: DM and comment automations are built in SociaHive's flow builder, not in n8n.

Each new article on your blog becomes a post in the next free posting slot of your accounts, so posts never pile up on the same morning. Set up your weekly posting slots in SociaHive first (POST /api/v1/posting-slots, or see Posting slots in the docs). It runs the same on n8n Cloud or your own server.

If all you need is a draft for each new article, SociaHive's own RSS feeds do that without n8n. Use n8n when you want your own rules: skip a category, rewrite the text with an AI node, or post only on weekdays.

1. 1RSS Feed Trigger node: your blog's feed URL, checked every hour.
2. 2IF node: drop the items you do not want to post, for example one category.
3. 3HTTP Request node: GET https://www.sociahive.com/api/v1/find-slot?account_ids= followed by your LinkedIn, Threads and Telegram account ids. It returns the next free time (at) and holds it for 10 minutes.
4. 4HTTP Request node: POST https://www.sociahive.com/api/v1/posts with the item title and link as text, the three accounts under platforms, schedule_type set to scheduled and scheduled_at set to the at value from the step before.
5. 5Optional: a Webhook node that receives post.failed and messages you in Slack when a post could not go out.

Read next: How to schedule Telegram channel posts · Telegram integration · SociaHive API and SDKs

n8n has its own Telegram nodes, and a Telegram bot built in n8n is a good fit when Telegram is the only place you post or when the bot needs to answer messages with your own logic.

When the same content also goes to Instagram, LinkedIn or Threads, send it through SociaHive instead. You connect the channel once with your own bot, every post sits in one calendar, and a post that fails shows up in one place. SociaHive posts to Telegram channels only, not to groups or private chats.