Unipile icon

Unipile

Interact with Unipile API
Join our community

Actions85

Overview

This node interacts with the Unipile API to list posts associated with a specific user. It is designed to retrieve posts from a user's account, supporting pagination and filtering options such as limiting the number of results or specifying whether the posts are from a company.

Common scenarios where this node is beneficial include:

  • Aggregating social media or communication posts related to a user for analysis or display.
  • Building dashboards that show recent user activity or posts.
  • Automating workflows that require fetching user posts for further processing or notifications.

For example, you could use this node to fetch the latest 50 posts from a user's account, optionally filtering to only company posts, and then process or store these posts in another system.

Properties

Name Meaning
Identifier A required string identifier for the user whose posts are being listed.
Account ID A required string representing the account ID to query posts from.
Additional Fields Optional parameters to refine the query:
- Cursor A string cursor used for pagination to fetch subsequent pages of results.
- Is Company A boolean indicating whether to filter posts to those from a company (true) or not (false).
- Limit A number specifying the maximum number of posts to return (minimum 1, default 50).

Output

The node outputs JSON data containing the list of posts retrieved from the Unipile API for the specified user and account. The structure typically includes post details such as content, timestamps, author information, and any metadata provided by the API.

If the API supports binary data (e.g., attachments or media within posts), the node would handle it accordingly, but based on the provided code and properties, the primary output is JSON-formatted post data.

Dependencies

  • Requires an active connection to the Unipile API.
  • Needs an API authentication token or key configured in the node's credentials (referred generically as "an API key credential").
  • The base URL for the API is dynamically set from the credential's DSN (Data Source Name).
  • No additional external dependencies are indicated.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key or authentication token is correctly configured; otherwise, API requests will fail.
  • Invalid or missing required properties: The Identifier and Account ID fields are mandatory. Omitting them will cause errors.
  • Pagination issues: If using the Cursor field incorrectly, you might receive empty results or repeated data. Use the cursor value returned from previous responses for correct pagination.
  • Limit value errors: Setting the Limit below 1 may cause validation errors; ensure it is at least 1.
  • API rate limits or connectivity problems: Network issues or exceeding API quotas can result in request failures. Check network connectivity and API usage limits.

Links and References

Discussion