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 retrieve detailed information about a specific email. It is designed to fetch an email by its unique identifier, optionally including additional data such as account context or email headers.
This node is beneficial in scenarios where you need to programmatically access email content and metadata from Unipile within an n8n workflow. For example, it can be used to automate processing of incoming emails, integrate email data into CRM systems, or trigger actions based on email content.
Practical examples:
- Fetching an email by ID to analyze its content and extract actionable information.
- Retrieving email headers for compliance or auditing purposes.
- Accessing emails associated with a particular account when managing multiple accounts.
Properties
| Name | Meaning |
|---|---|
| Email ID | The unique identifier of the email to retrieve. This is required. |
| Additional Fields | Optional extra parameters: |
| - Account ID: The ID of the account to scope the request (useful when using provider UID). | |
| - Include Headers: Boolean flag to specify whether to include email headers in the response. |
Output
The node outputs JSON data representing the retrieved email. The structure includes all standard email fields such as sender, recipient, subject, body, and optionally headers if requested.
If the "Include Headers" option is enabled, the output will contain the email headers alongside other email details.
No binary data output is indicated by the source code.
Dependencies
- Requires an active connection to the Unipile API via an API key credential configured in n8n.
- The base URL for API requests is taken from the credential's DSN configuration.
- Proper permissions to access the specified email and account are necessary.
Troubleshooting
- Missing or invalid Email ID: The node requires a valid email ID; ensure this is provided and correct.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Account ID mismatch: If specifying an Account ID, confirm it matches the email's actual account context.
- Network issues: Check connectivity to the Unipile API endpoint.
- Unexpected response format: Ensure the API version and endpoint have not changed; update the node or credentials accordingly.
Links and References
- Unipile API Documentation (example placeholder link)
- n8n documentation on creating custom nodes