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 chats associated with a specific attendee. It is designed to retrieve messaging conversations for an attendee, which can be useful in scenarios such as customer support, event management, or any application where tracking attendee communications is necessary.
For example, if you want to fetch all chat conversations of a particular attendee to analyze their interactions or display them in a dashboard, this node operation will provide that data.
Properties
| Name | Meaning |
|---|---|
| Attendee ID | The unique identifier of the attendee whose chats you want to list. (Required) |
| Additional Fields | Optional parameters to refine the query: |
| - Account ID | Filter chats by a specific account identifier. |
| - After | Return chats after a specified timestamp or cursor. |
| - Before | Return chats before a specified timestamp or cursor. |
| - Cursor | Pagination cursor to continue listing from a previous result set. |
| - Limit | Maximum number of chat results to return (minimum 1, default 50). |
Output
The output JSON contains the list of chats related to the specified attendee. Each item in the output represents a chat conversation with details as returned by the Unipile API. The exact structure depends on the API response but typically includes chat identifiers, participants, timestamps, and message summaries.
If binary data were involved (e.g., attachments), it would be included accordingly, but this operation focuses on listing chat metadata only.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for the API is configured via credentials.
- No additional external dependencies are indicated.
Troubleshooting
- Missing or invalid Attendee ID: The operation requires a valid attendee identifier. Ensure this field is provided and correctly formatted.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Pagination issues: When using cursors or limits, ensure values are valid to avoid empty or incomplete results.
- Rate limiting or network errors: Handle API rate limits gracefully and check network connectivity.
Links and References
- Unipile API Documentation (Assumed official docs for further details)
- n8n documentation on HTTP Request Node for understanding API integrations