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 accounts, media, and posts. Specifically, for the Account resource and the Get Connected Chats operation, it retrieves the connected chat sessions associated with a given social media account on a specified platform. This is useful when you want to programmatically access chat conversations linked to an account managed via PostPulse.

Common scenarios:

  • Fetching all chat conversations connected to a particular social media account (e.g., Telegram, Facebook Messenger) for monitoring or analytics.
  • Integrating chat data into workflows for customer support automation or reporting.
  • Synchronizing chat information from PostPulse into other systems.

Example:
You have a Telegram account connected in PostPulse and want to retrieve all active chats for that account to analyze user engagement or trigger follow-up actions in your workflow.

Properties

Name Meaning
Account ID The numeric ID of the social media account to get connected chats for.
Platform The platform name (string) for which to get connected chats. Use the platform value obtained from the "Get Many" accounts operation (e.g., "telegram", "facebook").

Output

The node outputs JSON data representing the connected chats for the specified account and platform. Each item in the output array corresponds to a chat session with details as provided by the PostPulse API.

  • The exact structure depends on the API response but typically includes chat identifiers, participant info, timestamps, and possibly message summaries.
  • No binary data output is indicated for this operation.

Dependencies

  • Requires an authenticated connection to the PostPulse API using OAuth2 credentials.
  • The node expects the base URL https://api.post-pulse.com and uses JSON content-type headers.
  • Proper API credentials must be configured in n8n to authorize requests.

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID or Platform parameters will cause the API call to fail.
    • Authentication errors if the OAuth2 token is expired or misconfigured.
    • If the account does not have any connected chats on the specified platform, the output may be empty.

  • Error messages:

    • Errors returned from the API are caught and can be output as error messages per item if "Continue On Fail" is enabled.
    • Typical errors include "Unauthorized" (check credentials), "Not Found" (invalid account ID), or "Bad Request" (incorrect platform string).

  • Resolution tips:

    • Verify the Account ID and Platform values are correct and correspond to existing connected accounts.
    • Refresh or reconfigure API credentials if authentication fails.
    • Enable "Continue On Fail" to handle partial failures gracefully in batch executions.

Links and References

Discussion