Actions85
- Account Actions
- Calendar Actions
- Email Actions
- LinkedIn Actions
- Close Job Posting
- Create Job Posting
- Download Applicant Resume
- Edit Job Posting
- Endorse Skill
- Get Company Profile
- Get Hiring Project by ID
- Get Hiring Projects
- Get Inmail Balance
- Get Job Applicant
- Get Job Applicants
- Get Job Offer
- Get Job Postings
- Get Raw Data
- Perform Action on Member
- Publish Job Posting
- Search
- Search Parameters
- Solve Job Publishing Checkpoint
- Messaging Actions
- Post Actions
- User Actions
- Webhook Actions
Overview
The node interacts with the Unipile API to list the accounts that a specific user is following. This operation is useful for scenarios where you want to retrieve and analyze the social connections or followed accounts of a user within the Unipile platform. For example, marketers might use this to understand user interests or to tailor content based on followed accounts.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose following list you want to retrieve. |
| Account ID | The account identifier associated with the user context in Unipile. |
| Additional Fields | Optional parameters to refine the request: |
| - Cursor | A pagination cursor to fetch the next set of results. |
| - Limit | Maximum number of results to return (minimum 1, default 50). |
Output
The node outputs JSON data containing the list of accounts that the specified user is following. The structure typically includes details about each followed account such as identifiers and metadata provided by the Unipile API. There is no indication that binary data is returned by this operation.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured via credentials.
- Proper network access to the Unipile API endpoint is necessary.
Troubleshooting
- Missing or invalid User ID or Account ID: Ensure both are provided and correctly formatted; these are required fields.
- API authentication errors: Verify that the API key credential is valid and has appropriate permissions.
- Pagination issues: If using the cursor parameter, ensure it is correctly obtained from previous responses to avoid empty or repeated results.
- Rate limiting or API errors: Handle HTTP error responses gracefully; check API limits and retry policies.
Links and References
- Unipile API Documentation (Assumed, replace with actual link if available)
- n8n documentation on HTTP Request Node for understanding API integrations