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
This node interacts with the Unipile API to list messages sent by a specific attendee (sender) within the Messaging resource. It is useful for retrieving communication history or message logs associated with a particular sender ID. Typical use cases include monitoring attendee interactions, auditing message exchanges, or integrating messaging data into workflows for further processing or reporting.
For example, you might use this node to fetch all messages sent by a user during an event or conversation, optionally filtering by date ranges or limiting the number of results returned.
Properties
| Name | Meaning |
|---|---|
| Sender ID | The unique identifier of the sender whose messages you want to list. |
| Additional Fields | Optional parameters to refine the query: |
| - Account ID | Filter messages by a specific account identifier. |
| - After | Return messages sent after this timestamp (string). |
| - Before | Return messages sent before this timestamp (string). |
| - Cursor | Pagination cursor to continue listing from a previous result set. |
| - Limit | Maximum number of messages to return (minimum 1, default 50). |
Output
The node outputs a JSON array of message objects corresponding to the specified sender and filters. Each object represents a single message with its associated metadata as returned by the Unipile API.
If the API supports pagination, the output may also include pagination cursors or tokens to retrieve subsequent pages of results.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured via the node credentials.
- Network access to the Unipile API endpoint is necessary.
Troubleshooting
- Missing or invalid Sender ID: The node requires a valid sender ID; ensure this field is correctly populated.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Rate limits or pagination issues: If many messages exist, use the
cursorandlimitfields to paginate through results. - Date filter format: Ensure
afterandbeforetimestamps are in the correct string format expected by the API. - Empty results: Confirm that the sender ID and filters match existing messages; otherwise, no data will be returned.
Links and References
- Unipile API Documentation (hypothetical link)
- n8n documentation on creating custom nodes