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 perform operations related to various resources, including emails. Specifically, the "Delete Email" operation allows users to delete an email by specifying its unique identifier. This is useful in scenarios where automated workflows need to manage or clean up email data within the Unipile platform, such as removing outdated or irrelevant emails programmatically.
Practical examples include:
- Automatically deleting emails after processing their content.
- Cleaning up emails from a specific account based on workflow conditions.
- Integrating email management into broader automation pipelines involving other Unipile resources.
Properties
| Name | Meaning |
|---|---|
| Email ID | The unique identifier of the email to be deleted. This is a required string input. |
| Additional Fields | Optional extra parameters; currently supports: |
| - Account ID | The ID of the account associated with the email (used when identifying the provider). |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details about any errors encountered. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured via credentials.
- The node sends HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Missing or invalid Email ID: Since the Email ID is required, omitting it or providing an incorrect value will likely cause the API call to fail. Ensure the Email ID is correct and provided.
- Authentication errors: If the API key or credentials are missing or invalid, the node will not be able to connect to the Unipile API. Verify that the API key credential is correctly set up.
- Account ID mismatch: When using the optional Account ID, ensure it corresponds to the correct account context; otherwise, the deletion may fail or target the wrong resource.
- API connectivity issues: Network problems or incorrect base URL configuration can prevent successful API calls.
Links and References
- Unipile API Documentation (general reference for API endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes