PostPulse

v0.2.5

Last updated Apr 17, 2026

n8n community node for PostPulse social media management

55 Weekly Downloads

161 Monthly Downloads

View on NPM GitHub Repository

Included Nodes

PostPulse

Description

PostPulse n8n Node

> Official n8n integration for PostPulse — schedule and publish content to multiple social networks from your n8n workflows.

Auth: OAuth2 (auto refresh)
Core actions: Accounts → Media Upload → Schedule Post(s) (+ Telegram Channels / Facebook Pages lookup)
Targets today: Facebook, Instagram, TikTok, YouTube, Threads, LinkedIn, Telegram, X, Bluesky
Use cases: One-click multi-destination posting, media pipeline, automated campaigns

—

Prerequisites
Install
Authenticate
Quick start
Operations
Data model
Platform settings
Media & text validations
Rate limits & API keys
Webhooks
Examples
FAQ
Support
Versioning & License

—

Prerequisites

1. Sign up at https://post-pulse.com/login
2. Connect your social accounts in the web app: https://post-pulse.com/app/accounts
3. Create OAuth client: Visit https://developers.post-pulse.com and sign in using the email associated with your PostPulse account. Create a new OAuth client to obtain clientid and clientsecret.
4. (Telegram only) Add the official PostPulse bot to your channels you plan to post to.

> Use the same email in n8n OAuth as your PostPulse account email.

—

Install

From npm (recommended):

  npm install @postpulse/n8n-nodes-postpulse

—

Authenticate

Create Credentials → PostPulse OAuth2 API in n8n:

OAuth Redirect URL: Use this URL when creating your OAuth client at https://developers.post-pulse.com
Client ID / Secret: Obtained from the developer portal at https://developers.post-pulse.com

This node extends n8n’s oAuth2Api so tokens are refreshed automatically.

—

Quick start

Using Schedule (Light) – Recommended for simple workflows

1. Media → Upload (if posting media)
– From File: Upload binary file data (automatically confirmed for integrity)
– Returns: { path } — use this directly in attachment paths
– From Public URL: Import media from a URL
– With Wait for Completion enabled (recommended): polls until ready and returns { path } — same shape as file upload
– With Wait for Completion disabled: returns { id, state } — use Media → Get Upload Status to poll manually
2. Posts → Schedule (Light)
– Choose Schedule Mode: “Post Now” (immediate) or “Schedule for Later” (pick a time)
– Select your connected account from the dropdown (accounts loaded automatically)
– UI automatically shows platform-specific fields (e.g., Instagram: Publication Type)
– Facebook and Telegram accounts: select Page/Channel from dropdowns (loaded automatically)
– Enter content and comma-separated attachment paths

Using Schedule – Advanced workflows

For multi-account posting or complex scenarios:

1. Accounts → Get Many
Retrieve your connected accounts. Save the id of targets you’ll post to.
2. Accounts → Get Connected Chats (only if posting to Telegram/Facebook manually)
Input: Account ID and platform. Output contains chat/page IDs.
3. Media → Upload (same as above)
4. Posts → Schedule
Build one PostSchedule with one or more Publications.
– Choose “Post Now” or “Schedule for Later” (with a specific time)
– Manually construct platformSettings JSON
– For now, prefer isDraft: false (update APIs will come later)

—

Operations

Accounts: Get Many

Output: Array of accounts: { id, platform, handle, ... }
Use: Pick id for each destination.

Telegram: Get Connected Chats

Input: { id } (must be a Telegram account)
Output: Array: { id, title } — pass chatId into Telegram posts.

Media: Upload

Input: File or Public URL
Output:

– File upload: { path } — use in attachmentPaths of posts (upload is automatically confirmed for integrity)
– URL import (Wait for Completion ON): { path } — same shape as file upload, ready to use
– URL import (Wait for Completion OFF): { id, state } — use id with “Get Upload Status” to monitor progress manually

Upload Sources:

– From File: Upload binary file data
– From Public URL: Import media from a public URL. Enable Wait for Completion to automatically poll until the import is ready (configurable polling interval and max wait time).

Media: Get Upload Status

Input: { importId } (from URL import response)
Output: Complete import status including id, state, sourceUrl, bytesDownloaded, totalBytes, detectedMime, s3Key, errorCode, errorMessage
Use: Monitor the progress of URL-based media imports

Posts: Schedule

Input: PostSchedule (see Data model)
Schedule Mode: “Post Now” (publishes immediately, no scheduledTime needed) or “Schedule for Later” (pick a time)
Behavior: Schedules one or multiple publications for the same time.
Recommended: isDraft: false (until update endpoints are exposed in node).

Posts: Schedule (Light)

Purpose: Simplified interface for scheduling a single post to one account
Key Features:

– Platform-specific dynamic fields — The UI automatically shows relevant fields based on the selected account’s platform
– Automatic platform settings — No need to manually construct JSON; the node builds platformSettings automatically
– Smart chat selection — Facebook Pages and Telegram Channels appear as dropdowns (loaded from API)
– Simple attachment paths — Enter comma-separated media paths instead of managing collections

Input Fields:

– Schedule Mode — “Post Now” (publishes immediately) or “Schedule for Later” (pick a time)
– Scheduled Time — (only when “Schedule for Later”) When to schedule the post. Interpreted using the workflow timezone (see Workflow Settings).
– Social Media Account — Dropdown of your connected accounts
– Dynamic fields based on platform:
– Instagram: Publication Type (Feed/Reels/Story)
– Facebook: Publication Type (Feed/Reels/Story) + Page dropdown
– YouTube: Video Title
– TikTok: Title
– Threads: Topic Tag (optional)
– Telegram: Channel dropdown
– X/Twitter, BlueSky, LinkedIn: No additional fields
– Content — Post text/caption (multi-line)
– Attachment Paths — Comma-separated media paths from Media → Upload

Output: Same as Schedule operation
Use Case: Perfect for simple workflows and testing; for complex multi-account or multi-post scenarios, use Schedule operation

—

Data model

`PostSchedule`

{
  "scheduledTime": "2025-08-17T14:03:00",  // omit to post immediately
  "isDraft": false,
  "publications": [ / Publication[] / ]
}

`Publication`

Represents “one publication in user’s mind” that may map to one or many platform posts.

{
  "socialMediaAccountId": 442,
  "posts": [ / Post[] / ],
  "platformSettings": { / see below / }
}

One publication → multiple posts is useful when:

– Telegram account posts to several channels (one post per channel)
– Telegram account posts with large text or more than 10 media (one post per message that will be published)
– Instagram storyline (multiple stories in one conceptual set)

`Post`

{
  "attachmentPaths": [
    "6354d8d2-e0f1-702b-af6c-62e28e377ec7/c6c2b826-8aca-4eae-8549-515325012ab4.jpeg"
  ],
  "content": "Your caption or description",
  "chatId": "1234567890"   // Telegram only
  / "thumbnailPath": "..." — coming soon /
}

> Note: For YouTube/TikTok, content is used as description (titles are set in platformSettings).

—

Platform settings

Each Publication must include platformSettings with a required discriminator: type.

{ "type": "INSTAGRAM", "publicationType": "REELS" }

Supported shapes:

Instagram

{
  "type": "INSTAGRAM",
  "publicationType": "FEED" | "REELS" | "STORY"
}

{
  "type": "LINKEDIN",
  "visibility": "PUBLIC" | "CONNECTIONS" | "GROUP"
}

Threads

{
  "type": "THREADS",
  "topicTag": "your-topic-tag"
}

TikTok

{
  "type": "TIK_TOK",
  "title": "My video title",
  "privacyLevel": "PUBLICTOEVERYONE" | "FOLLOWEROFCREATOR" | "MUTUALFOLLOWFRIENDS" | "SELF_ONLY",
  "disableDuet": false,
  "disableComments": false,
  "disableStitch": false,
  "brandContent": false,
  "brandOrganic": true,
  "hasUsageConfirmation": true
}

YouTube

{
  "type": "YOUTUBE",
  "title": "My video title",
  "privacyStatus": "PUBLIC" | "UNLISTED" | "PRIVATE",
  "category": "FILMANIMATION" | "AUTOSVEHICLES" | "MUSIC" | "PETSANIMALS" | "SPORTS" | "TRAVELEVENTS" | "GAMING" | "PEOPLEBLOGS" | "COMEDY" | "ENTERTAINMENT" | "NEWSPOLITICS" | "HOWTOSTYLE" | "EDUCATION" | "SCIENCETECHNOLOGY"
}

—

Media & text validations

PostPulse Web enforces rich, platform-specific validations.
API clients must currently validate themselves. (Server-side validations for API clients are planned.)

> Follow updates at https://post-pulse.com/releases — we’ll announce when API-side validations roll out.

—

Rate limits & API keys

Authentication uses OAuth2; tokens are auto-refreshed by n8n.
PostPulse runs on AWS API Gateway usage plans. Typical plans:

– Standard: 20 RPS burst, 200 RPS steady, 50k req/month
– Agency: higher limits on request

—

Webhooks

PostPulse supports webhooks for real-time notifications instead of polling for status updates. This is especially useful for tracking:

Post publishing status — Get notified when scheduled posts are published or fail
Media import progress — Receive updates on URL-based media imports without polling the “Get Upload Status” endpoint

Setting up webhooks

1. Register webhook endpoints at the Developer Portal
2. Configure event types you want to receive notifications for
3. Review webhook models and event types in the developer documentation

Benefits over polling

Real-time updates — Instant notifications when events occur
Reduced API calls — No need to repeatedly poll status endpoints
Better reliability — Guaranteed delivery with retry mechanisms
Lower latency — Immediate response to status changes

> Learn more: Visit https://developers.post-pulse.com for complete webhook documentation, supported event types, and payload schemas.

—

Examples

Minimal single-destination post (Reel)

{
  "scheduledTime": "2025-08-17T14:03:00",
  "isDraft": false,
  "publications": [
    {
      "socialMediaAccountId": 442,
      "platformSettings": {
        "type": "INSTAGRAM",
        "publicationType": "REELS"
      },
      "posts": [
        {
          "attachmentPaths": [
            "6354d8d2-e0f1-702b-af6c-62e28e377ec7/c6c2b826-8aca-4eae-8549-515325012ab4.jpeg"
          ],
          "content": "New drop is live! #fashion"
        }
      ]
    }
  ]
}

Telegram to multiple channels in one publication

{
  "scheduledTime": "2025-08-17T14:03:00",
  "isDraft": false,
  "publications": [
    {
      "socialMediaAccountId": 501,   // Telegram account id
      "platformSettings": { "type": "TELEGRAM" },
      "posts": [
        { "chatId": "-100123", "content": "Hello Channel A", "attachmentPaths": ["u1/p1.jpg"] },
        { "chatId": "-100456", "content": "Hello Channel B", "attachmentPaths": ["u1/p1.jpg"] }
      ]
    }
  ]
}

TikTok with title & privacy

{
  "scheduledTime": "2025-08-17T14:03:00",
  "isDraft": false,
  "publications": [
    {
      "socialMediaAccountId": 777,
      "platformSettings": {
        "type": "TIK_TOK",
        "title": "Top 5 tips",
        "privacyLevel": "PUBLICTOEVERYONE",
        "hasUsageConfirmation": true
      },
      "posts": [
        { "attachmentPaths": ["u1/v1.mp4"], "content": "Full guide in bio" }
      ]
    }
  ]
}

Media import from URL

{
  "url": "https://example.com/my-video.mp4",
  "filenameHint": "promotional-video.mp4"
}

Response:

{
  "id": 12345,
  "state": "QUEUED"
}

Check media import status

Input: importId: 12345

Response:

{
  "id": 12345,
  "state": "READY",
  "sourceUrl": "https://example.com/my-video.mp4",
  "bytesDownloaded": 15728640,
  "totalBytes": 15728640,
  "detectedMime": "video/mp4",
  "s3Key": "6354d8d2-e0f1-702b-af6c-62e28e377ec7/promotional-video.mp4"
}

> Note: Use the s3Key value in attachmentPaths when the state is READY.

Schedule (Light) – Instagram Reel

Using the simplified interface with automatic platform settings:

Node configuration:

Schedule Mode: Schedule for Later
Scheduled Time: 2025-08-17T14:03:00
Social Media Account: INSTAGRAM - @fashionbrand
Publication Type: Reels (automatically appears for Instagram)
Content: New drop is live! #fashion
Attachment Paths: 6354d8d2-e0f1-702b-af6c-62e28e377ec7/video.mp4

The node automatically builds this API request:

{
  "scheduledTime": "2025-08-17T14:03:00",
  "isDraft": false,
  "publications": [{
    "socialMediaAccountId": 442,
    "platformSettings": {
      "type": "INSTAGRAM",
      "publicationType": "REELS"
    },
    "posts": [{
      "content": "New drop is live! #fashion",
      "attachmentPaths": ["6354d8d2-e0f1-702b-af6c-62e28e377ec7/video.mp4"]
    }]
  }]
}

Schedule (Light) – Telegram with Channel Selection

Node configuration:

Schedule Mode: Post Now
Social Media Account: TELEGRAM - @mybot
Channel: Tech Updates (loaded from API, shows connected channels)
Content: Check out our latest update!
Attachment Paths: user1/screenshot.png, user1/demo.mp4

The node automatically builds this API request (no scheduledTime — posts immediately):

{
  "isDraft": false,
  "publications": [{
    "socialMediaAccountId": 501,
    "platformSettings": {
      "type": "TELEGRAM"
    },
    "posts": [{
      "chatId": "-1001234567890",
      "content": "Check out our latest update!",
      "attachmentPaths": ["user1/screenshot.png", "user1/demo.mp4"]
    }]
  }]
}

Schedule (Light) – YouTube Video

Node configuration:

Schedule Mode: Schedule for Later
Scheduled Time: 2025-08-17T14:03:00
Social Media Account: YOUTUBE - @MyChannel
Video Title: Top 5 JavaScript Tips (automatically appears for YouTube)
Content: Full tutorial with code examples. Links in description.
Attachment Paths: user1/tutorial-video.mp4

The node automatically builds this API request:

{
  "scheduledTime": "2025-08-17T14:03:00",
  "isDraft": false,
  "publications": [{
    "socialMediaAccountId": 777,
    "platformSettings": {
      "type": "YOUTUBE",
      "title": "Top 5 JavaScript Tips"
    },
    "posts": [{
      "content": "Full tutorial with code examples. Links in description.",
      "attachmentPaths": ["user1/tutorial-video.mp4"]
    }]
  }]
}

—

FAQ

Do I have to upload media to PostPulse even if I have a public URL?
Not anymore! You can now use the “From Public URL” option in Media → Upload to import media directly from URLs. The system will download and host the media on post-pulse.com for platform compatibility.

How do I import media from a URL?
Use Media → Upload with “From Public URL” option. Provide the URL and optionally a filename hint. Enable Wait for Completion to have the node automatically poll until the media is ready — it returns { path } just like file upload. Alternatively, disable Wait for Completion to get the import job ID and poll manually with Media → Get Upload Status.

What are the different import states?

QUEUED: Import job is waiting to start
DOWNLOADING: Media is being downloaded from the source URL
VALIDATING: Downloaded media is being validated
UPLOADING: Media is being uploaded to PostPulse storage
READY: Import complete, media ready to use (check s3Key field)
FAILED_TEMPORARY: Temporary failure, may retry automatically
FAILED_PERMANENT: Permanent failure, check errorCode and errorMessage

Can I draft then update later via the node?
In v1 of the node, we recommend isDraft: false. Update endpoints will be exposed in a later version.

How do I post to multiple accounts at once?
Create one PostSchedule with multiple Publication objects (one per account).

How do I set YouTube or TikTok titles?
Titles live in platformSettings (see schemas above). content becomes description.

Should I use webhooks or polling for status updates?
Webhooks are recommended for production workflows as they provide real-time notifications without the need to repeatedly call status endpoints. Set up webhooks at https://developers.post-pulse.com to receive instant notifications for post publishing status and media import progress. Use polling (Get Upload Status) only for testing or when webhooks aren’t feasible.

—

Support

Developer Portal: https://developers.post-pulse.com (for OAuth client setup and documentation)
Discord Community: PostPulse for Developers (feature requests, community support)
Email Support: support@post-pulse.com (technical issues and general inquiries)

—

Versioning & License

Semantic Versioning: MAJOR.MINOR.PATCH
License: MIT

—

Security notes

Store secrets in n8n Credentials only; don’t hardcode in workflows.

Included Nodes

Description

PostPulse n8n Node

Table of contents

Prerequisites

Install

Authenticate

Quick start

Using Schedule (Light) – Recommended for simple workflows

Using Schedule – Advanced workflows

Operations

Accounts: Get Many

Telegram: Get Connected Chats

Media: Upload

Media: Get Upload Status

Posts: Schedule

Posts: Schedule (Light)

Data model

PostSchedule

Publication

Post

Platform settings

Instagram

LinkedIn

Threads

TikTok

YouTube

Media & text validations

Rate limits & API keys

Webhooks

Setting up webhooks

Benefits over polling

Examples

Minimal single-destination post (Reel)

Telegram to multiple channels in one publication

TikTok with title & privacy

Media import from URL

Check media import status

Schedule (Light) – Instagram Reel

Schedule (Light) – Telegram with Channel Selection

Schedule (Light) – YouTube Video

FAQ

Support

Versioning & License

Security notes

More in Social Media

Instagram

Instagram

Line Messaging

Instagram

Chatwoot fazer.ai

Example Node

Mastodon

LINE

`PostSchedule`

`Publication`

`Post`