PostPulse icon

PostPulse

Interact with PostPulse API to manage social media posts

Actions3

Overview

This node integrates with the PostPulse API to manage social media posts, specifically allowing users to schedule posts for future publication. It is useful in scenarios where social media managers or marketers want to automate posting content across multiple platforms at specific times without manual intervention.

For example, a user can prepare a post with text, media attachments, and platform-specific settings, then schedule it to be published on various social media accounts at a chosen date and time. This helps maintain consistent engagement and timely content delivery.

Properties

Name Meaning
Scheduled Time The exact date and time when the post should be published.
Is Draft A boolean flag indicating whether the post should be saved as a draft instead of being published immediately.
Publications A collection of one or more publications specifying where and how the post will be published. Each publication includes:
- Social Media Account ID The numeric identifier of the social media account where the post will be published.
- Platform Settings A JSON object containing platform-specific configuration options for the post.
- Posts One or more posts within the publication, each including:
-- Attachment Paths Paths to media files to attach to the post (e.g., images, videos).
-- Chat ID For Telegram posts, the chat ID where the post should be sent.
-- Content The textual content of the post.
-- Thumbnail Path Path to a thumbnail image associated with the post.

Output

The node outputs an array of JSON objects representing the results of the scheduling operation for each input item. Each output item corresponds to the response from the PostPulse API after attempting to schedule the post(s).

  • The json field contains details such as confirmation of scheduled posts, any errors encountered, or metadata returned by the API.
  • If the operation fails for an item and "Continue On Fail" is enabled, the output will include an error message in the JSON field for that item.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to connect securely to the PostPulse API.
  • The node communicates with the PostPulse API endpoint at https://api.post-pulse.com.
  • No additional external dependencies are required beyond the API access.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrectly formatted platform settings JSON may result in API errors.
    • Scheduling posts in the past or with invalid date formats will likely be rejected.
    • Missing required fields like Social Media Account ID or Scheduled Time will cause validation errors.

  • Error Messages:

    • Errors returned from the API are passed through in the output JSON under an error property.
    • If the node is set to stop on failure, any error will halt execution; enabling "Continue On Fail" allows processing subsequent items.

  • Resolution Tips:

    • Verify API credentials and permissions.
    • Ensure all required properties are correctly filled.
    • Validate JSON syntax for platform settings before execution.
    • Confirm scheduled times are set to future dates.

Links and References

Discussion