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 integrates with the Unipile API to interact with various resources, including Messaging. Specifically, the "List Attendees" operation under the Messaging resource retrieves a list of attendees related to messaging events or conversations. This operation is useful for scenarios where you need to fetch participant details from messaging threads, such as in customer support chats, team communications, or event attendee lists.
Practical examples include:
- Fetching all participants involved in a particular messaging conversation.
- Retrieving attendee information for follow-up or analytics.
- Integrating attendee data into workflows for notifications or reporting.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional parameters to refine the attendee list request: |
| - Account ID | Filter attendees by a specific account identifier. |
| - Cursor | Pagination cursor to retrieve the next set of results. |
| - Limit | Maximum number of attendee records to return (minimum 1, default 50). |
Output
The node outputs JSON data containing the list of attendees retrieved from the Unipile Messaging service. The structure typically includes attendee details such as identifiers, names, and possibly contact information depending on the API response.
If binary data were returned (e.g., attachments), it would be included in the binary output field, but this operation focuses on JSON attendee data only.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured via credentials.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing API authentication token will cause authorization errors.
- Providing an invalid cursor may result in empty or error responses.
- Exceeding the limit parameter beyond allowed maximums might cause request failures.
Error messages:
- Authorization errors indicate problems with the API key; verify credentials.
- Validation errors may occur if input parameters like
limitare out of range; ensure they meet specified constraints. - Network or connectivity errors suggest checking the base URL and network access.
Links and References
- Unipile API Documentation (general reference for API endpoints and parameters)
- n8n documentation on HTTP Request Node for understanding API integrations