PostPulse icon

PostPulse

Interact with PostPulse API to manage social media posts
Join our community

Actions4

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 you want to automate posting content across multiple social media accounts at specific times without manual intervention.

For example, a marketing team can prepare posts in advance and use this node to schedule them to be published on various platforms at optimal engagement times. It supports draft posts as well, enabling review workflows before going live.

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 is a draft (not yet published).
Publications A collection of one or more publications specifying:
- Social Media Account ID: The target social media account's identifier.
- Platform Settings: Platform-specific configuration as a JSON object.
- Posts: One or more posts containing:
  • Attachment Paths: Paths to media files to attach.
  • Chat ID: For Telegram posts, the chat identifier.
  • Content: The text content of the post.
  • Thumbnail Path: Path to a thumbnail image for the post.

Output

The node outputs an array of JSON objects representing the result of scheduling each post. Each output item corresponds to an input item processed and contains details returned by the PostPulse API about the scheduled post(s).

If errors occur during processing, the output will include error messages associated with the respective input items.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the PostPulse API.
  • The node communicates with the PostPulse API endpoint at https://api.post-pulse.com.
  • Proper configuration of OAuth2 credentials or equivalent API authentication is necessary within n8n.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrectly formatted platform settings JSON may lead to API errors.
    • Providing invalid social media account IDs or chat IDs can cause the scheduling request to fail.
    • Scheduling posts in the past might be rejected by the API.

  • Error Messages:

    • Errors returned from the API are passed through in the output under an error field.
    • If the node is set to continue on failure, it will output error details per failed item instead of stopping execution.

  • Resolution Tips:

    • Verify that the API credentials are correctly configured and have sufficient permissions.
    • Validate JSON syntax for platform-specific settings before submitting.
    • Ensure all required fields like scheduled time and social media account IDs are correctly provided.
    • Check that the scheduled time is set to a future date/time.

Links and References

Discussion