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 accounts and their connected chats. Specifically, for the Account resource and the Get Connected Chats operation, it retrieves the list of chats connected to a specified social media account on a given platform.

Typical use cases include:

  • Fetching all chat conversations linked to a particular social media account for monitoring or analytics.
  • Integrating chat data into workflows for customer support or engagement automation.
  • Synchronizing chat information from PostPulse into other systems or databases.

For example, you might use this node to get all Telegram chats connected to a specific account ID, then process those chats further in your workflow.

Properties

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

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 connected to the account, typically including details such as chat IDs, names, or other metadata provided by the PostPulse API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the PostPulse API.
  • Needs an API authentication token configured via OAuth2 credentials within n8n.
  • The base URL for API requests is https://api.post-pulse.com.

Troubleshooting

  • Common issues:

    • Invalid or missing Account ID or Platform parameters will cause the API call to fail.
    • Authentication errors if the API token is expired or misconfigured.
    • Network connectivity problems preventing access to the PostPulse API.

  • Error messages:

    • Errors returned from the API will be surfaced as error messages in the node output.
    • If "Continue On Fail" is enabled, errors will be included in the output JSON under an error field instead of stopping execution.

  • Resolutions:

    • Verify that the Account ID and Platform values are correct and correspond to existing accounts.
    • Ensure the API credentials are valid and have not expired.
    • Check network settings and firewall rules to allow outbound HTTPS requests to api.post-pulse.com.

Links and References

Discussion