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 emails from a specified account. It is useful for workflows that need to retrieve and process email data, such as automating email monitoring, filtering, or archiving tasks. For example, you could use this node to fetch recent emails from a particular folder or filter emails by sender or recipient addresses.
Properties
| Name | Meaning |
|---|---|
| Account ID | The ID of the account to use. This identifies which email account to query. |
| Additional Fields | Optional filters and parameters to refine the email list request: |
| - After | Return emails after this date/time. |
| - Any Email | Filter by any matching email address (comma-separated). |
| - Before | Return emails before this date/time. |
| - Cursor | A cursor used for pagination to continue listing from a previous point. |
| - Folder | Filter emails by folder provider ID. |
| - From | Filter by sender email address. |
| - Include Headers | Whether to include full email headers in the response (true/false). |
| - Limit | Maximum number of results to return (minimum 1). |
| - Meta Only | Whether to return only metadata, omitting large email bodies (true/false). |
| - Thread ID | Filter by email thread identifier. |
| - To | Filter by recipient email address. |
Output
The node outputs a JSON array where each item represents an email matching the specified criteria. Each email object typically contains metadata such as sender, recipient, subject, date, and optionally full headers or body content depending on the Include Headers and Meta Only options. If binary data were included (e.g., attachments), it would be represented separately, but this node focuses on JSON email data.
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 Account ID: Ensure the Account ID is provided and correct; otherwise, the API will not return emails.
- API authentication errors: Verify that the API key credential is valid and has necessary permissions.
- Pagination issues: When using the
Cursorfield for pagination, ensure the cursor value is correctly passed from previous responses. - Date filters format: The
AfterandBeforefields expect valid date-time strings; incorrect formats may cause errors or empty results. - Limit too high or low: The
Limitmust be at least 1; setting it too high might lead to performance issues or API rate limits.
Links and References
- Unipile API Documentation (hypothetical link for reference)
- n8n documentation on HTTP Request Node for understanding API interactions