PostPulse

v0.2.13

Last updated Nov 10, 2026

n8n community node for PostPulse social media management

241 Weekly Downloads

635 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 / Pinterest Boards / WhatsApp numbers, contact lists and templates lookup)
Targets today: Facebook, Instagram, TikTok, YouTube, Threads, LinkedIn, Pinterest, Telegram, X, Bluesky, WhatsApp (template broadcasts)
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: Open the Developer Portal in the PostPulse app (sign in 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.
5. (WhatsApp only) Connect the WhatsApp Business Account and create contact lists on the website. Message templates are created and approved in WhatsApp Manager. WhatsApp can’t be connected from n8n.

> 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://post-pulse.com/app/portal/apps
Client ID / Secret: Obtained from the Developer Portal at https://post-pulse.com/app/portal/apps

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

—

Quick start

> Renamed in 0.2.13: the operation formerly called Schedule (Light) is now Schedule (action “Schedule a post”), and the former Schedule is now Schedule (Advanced) (action “Schedule an advanced post”). Only the names changed: existing workflows keep working as they are.

Using Schedule – Recommended

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
– 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, Telegram and Pinterest accounts: select Page/Channel/Board from dropdowns (loaded automatically). A Facebook Page account is the Page itself, so it has no Page dropdown
– WhatsApp accounts: select the number to send from, the contact list and the template from dropdowns, then fill the template’s variables (see WhatsApp)
– Enter content and comma-separated attachment paths
– TikTok accounts: pick a Privacy Level (required, loaded from the account’s TikTok creator info) and set the interaction, music and commercial-content options (see below)
– Instagram and TikTok accounts: optionally turn on the AI Content toggle (off by default) to label the post as AI-generated

Using Schedule (Advanced) – Advanced workflows

For posting to several accounts in one post, several posts in one publication (e.g. several Telegram channels), drafts, or platform settings that Schedule has no fields for (e.g. LinkedIn visibility, YouTube privacy and category):

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/Pinterest/WhatsApp manually)
Input: Account ID. Output contains chat/page IDs.
3. Accounts → Get Contact Lists and Accounts → Get Templates (WhatsApp only)
Input: WhatsApp account. Output: the contact lists (id → contactListId) and the templates (name, language → templateName, templateLanguage, plus the keys of the template’s variables). See WhatsApp.
4. Media → Upload (same as above)
5. Posts → Schedule (Advanced)
Build one PostSchedule with one or more Publications.
– Choose “Post Now” or “Schedule for Later” (with a specific time, interpreted in the workflow timezone)
– 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.

Accounts: Get Connected Chats

Input: Account ID (a Telegram, Facebook, Pinterest or WhatsApp account)
Output: Array: { id, title } — Telegram channels, Facebook Pages, Pinterest boards or WhatsApp phone numbers. Pass id as chatId into posts.

Accounts: Get Contact Lists

Input: WhatsApp Account — Dropdown of your connected WhatsApp accounts (or the account id via an expression)
Output: One item per contact list: { id, name, contactCount, createdTime }. Pass id as contactListId in the WhatsApp platformSettings.
Note: Contact lists are created and filled on the PostPulse website.

Accounts: Get Templates

Input: WhatsApp Account — Dropdown of your connected WhatsApp accounts (or the account id via an expression)
Output: One item per message template: { name, language, category, parameterFormat, headerFormat, headerText, headerParameterKey, bodyText, bodyParameterKeys, footerText, buttons, supported, unsupportedReason }
Use: Pass name and language as templateName and templateLanguage in the WhatsApp platformSettings, then fill the variables:

– bodyParameters — a value for every key in bodyParameterKeys ("1", "2", … when parameterFormat is POSITIONAL, the variable names when it is NAMED)
– headerParameter — only when headerParameterKey is set
– buttonParameters — the URL ending of each button with dynamicUrl: true, under the button’s index in buttons
– A headerFormat of IMAGE or VIDEO needs exactly one attachment of that type

Note: Templates with supported: false can’t be sent; unsupportedReason says why. Templates are created and approved in WhatsApp Manager.

Media: Upload

Input: File or Public URL
Output:

– File upload: { path } — use in attachmentPaths of posts (upload is automatically confirmed for integrity)
> Always use the returned path, not the name of the file you uploaded. During confirmation PostPulse detects the real media format from the file bytes; if it doesn’t match the filename extension (e.g. a .mov file renamed to .mp4), the stored file is renamed to the correct extension and path reflects the corrected name.
– 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

Purpose: Simplified interface for scheduling a single post to one account (named Schedule (Light) before 0.2.13)
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, Telegram Channels, Pinterest Boards and WhatsApp numbers 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
– Facebook Page (an account that is one Page): Publication Type (Feed/Reels/Story); no Page dropdown, the account is the Page
– YouTube: Video Title
– TikTok: Title, Privacy Level, Allow Comments/Duet/Stitch, Auto Add Music, Disclose Content (Your Brand / Branded Content) — see TikTok settings in Schedule
– Threads: Topic Tag (optional)
– Pinterest: Board dropdown, Pin Title, Destination Link, Alt Text, Board Section ID (all optional)
– Telegram: Channel dropdown
– WhatsApp: Send From Number, Contact List and Template dropdowns, Header Variable, Body Variables (key/value), Button URL Suffixes (button index/value); no Content field — the text comes from the template
– X/Twitter, BlueSky, LinkedIn: No additional fields
– Content — Post text/caption (multi-line)
– Attachment Paths — Comma-separated media paths from Media → Upload. With Publication Type Story, each path becomes its own story, in the order given, within one post
– AI Content — (Instagram and TikTok only) Toggle, off by default. Turn on when the content is generated or significantly edited with AI; the node sends it as aiContent in platformSettings.

Output: Same as Schedule (Advanced)
Use Case: Most workflows; for posting to several accounts in one post, several posts in one publication, drafts or settings without a field here, use Schedule (Advanced)

#### TikTok settings in Schedule

The TikTok fields follow the same rules as the TikTok form in the PostPulse app, which in turn follows TikTok’s Content Sharing Guidelines:

The node shows TikTok’s declaration “By posting, you agree to TikTok’s Music Usage Confirmation” (plus the Branded Content Policy for branded content) and sends hasUsageConfirmation: true.

At execution the node reads the account’s creator info once per account per run to apply the account-level settings above.

Posts: Schedule (Advanced)

Purpose: The whole PostSchedule in one call: several accounts, several posts per publication, drafts, any platformSettings (named Schedule before 0.2.13)
Input: PostSchedule (see Data model); platformSettings is JSON (see Platform settings): JSON text, which may contain expressions, or an expression that returns an object, e.g. one built from the output of Accounts → Get Templates
Schedule Mode: “Post Now” (publishes immediately, no scheduledTime needed) or “Schedule for Later” (pick a time)
Scheduled Time: Interpreted using the workflow timezone (see Workflow Settings) and sent to the API as UTC. A value with an explicit offset or Z is used as-is.
Behavior: Schedules one or multiple publications for the same time.
Recommended: isDraft: false (until update endpoints are exposed in node).
IDs for the JSON: account IDs from Accounts → Get Many, chat IDs from Accounts → Get Connected Chats, WhatsApp contact lists and templates from Accounts → Get Contact Lists and Accounts → Get Templates.

Posts: Get Delivery Summary

Purpose: Results of a WhatsApp broadcast
Input:

– WhatsApp Account — Dropdown of your connected WhatsApp accounts (or the account id via an expression, e.g. socialMediaAccountId of the publication)
– Post — Dropdown of the account’s broadcasts of the last 30 days, newest first (the 20 newest schedules with WhatsApp). Via an expression: the id of the post inside the WhatsApp publication (publications[].posts[] in the Schedule response), not the schedule id. The number in the PostPulse dashboard URL (?post=…, /app/edit-post/…) is the schedule id: GET /v1/posts/{scheduleId} returns its post IDs

Output: { total, pending, sending, accepted, sent, delivered, read, failed, optedOut, cancelled, topErrors } — how many messages of the broadcast are in each status, and the most frequent WhatsApp errors. The counts keep changing while WhatsApp reports statuses.

—

Data model

`PostSchedule`

{
  "scheduledTime": "2025-08-17T14:03:00",  // omit to post immediately; naive values are read in the workflow timezone
  "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 or Facebook storyline (multiple stories in one conceptual set, one post per story). Schedule builds these posts from its comma-separated paths

`Post`

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

> Note: For YouTube/TikTok/Pinterest, 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",
  "aiContent": false            // optional, default false — mark the post as AI-generated
}

{
  "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,
  "autoAddMusic": false,        // photo posts only
  "hasUsageConfirmation": true,
  "aiContent": false            // optional, default false — mark the post as AI-generated
}

> AI Content: aiContent is supported by Instagram and TikTok only. In Schedule it appears as the AI Content toggle for those platforms (off by default); in Schedule (Advanced) set it directly in platformSettings.

{
  "type": "PINTEREST",
  "title": "My Pin title",                 // optional, up to 100 characters
  "link": "https://example.com/product",   // optional, opened when the Pin is clicked
  "altText": "Describe the image",         // optional
  "boardSectionId": "1234567890"           // optional, section within the board
}

> The board is required and is set as the post’s chatId (get board IDs from Accounts → Get Connected Chats with the Pinterest account’s ID). A Pin needs media: 1 image, 1 video, or a carousel of 2–5 images.

{
  "type": "WHATSAPP",
  "contactListId": 42,                           // required
  "templateName": "autumn_sale",                 // required, an approved template
  "templateLanguage": "en",                      // required
  "headerParameter": "Autumn sale",              // only for a text header with a variable
  "bodyParameters": { "1": "20%", "2": "Sunday" }, // a value for every body variable
  "buttonParameters": { "0": "autumn-2026" }     // URL ending of each button with a dynamic URL, by button index
}

> A WhatsApp publication sends an approved template to a contact list from one phone number: it has exactly one post, whose chatId is the number (from Accounts → Get Connected Chats). contactListId comes from Accounts → Get Contact Lists; templateName, templateLanguage and the variable keys come from Accounts → Get Templates. content is not needed: PostPulse takes the text from the template. A template with an image or video header needs exactly one attachment of that type. In Schedule, a template entered with an expression is name|language, for example autumn_sale|en. The full rules are in the API docs.

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://post-pulse.com/webhooks for complete webhook documentation, supported event types, and payload schemas.

—

Examples

The JSON examples are PostSchedule bodies for Schedule (Advanced); the Schedule examples list the node’s fields.

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 – 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 – 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 – 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?
Use Schedule (Advanced): create one PostSchedule with multiple Publication objects (one per account). With Schedule, each input item schedules a separate post to one account.

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

How do I label a post as AI-generated?
For Instagram and TikTok, turn on the AI Content toggle in Schedule (it is off by default), or set "aiContent": true in platformSettings when using Schedule (Advanced). Other platforms ignore this setting.

Which timezone is Scheduled Time in?
The workflow timezone (n8n → Workflow Settings → Timezone). A naive value like 2025-08-17T14:03:00 is converted from that timezone to UTC before it is sent to the API. If the value already carries an offset or Z, it is used as-is.

Why does the upload path differ from my filename?
PostPulse validates the real media format after upload. If the bytes don’t match the extension (e.g. a .mov renamed to .mp4), the stored file is renamed to the correct extension. Always pass the path returned by Media → Upload into attachmentPaths.

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://post-pulse.com/app/portal/webhooks 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://post-pulse.com/app/portal/apps (for OAuth client setup)
Documentation: https://post-pulse.com/n8n-integration
Discord Community: PostPulse for Developers (feature requests, community support)
Email Support: [email protected] (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 – Recommended

Using Schedule (Advanced) – Advanced workflows

Operations

Accounts: Get Many

Accounts: Get Connected Chats

Accounts: Get Contact Lists

Accounts: Get Templates

Media: Upload

Media: Get Upload Status

Posts: Schedule

Posts: Schedule (Advanced)

Posts: Get Delivery Summary

Data model

PostSchedule

Publication

Post

Platform settings

Instagram

LinkedIn

Threads

TikTok

Pinterest

WhatsApp

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 – Instagram Reel

Schedule – Telegram with Channel Selection

Schedule – YouTube Video

FAQ

Support

Versioning & License

Security notes

More in Social Media

Browserflow for LinkedIn

Instagram

Instagram

Scavio

Chatwoot fazer.ai

Linked API

Repliz Account

AdaptlyPost

`PostSchedule`

`Publication`

`Post`