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 integrates with the Unipile API to update an existing email record. It is designed to modify email details by specifying the email's unique identifier and optionally providing additional fields or a raw JSON body for the update. This node is useful in automation workflows where email data needs to be programmatically updated, such as syncing email information from other systems, correcting email metadata, or enriching email records with new data.
Practical examples include:
- Updating the status or tags of an email after processing it in another system.
- Modifying email content or metadata based on user input or external triggers.
- Integrating with CRM or helpdesk tools to keep email records up-to-date automatically.
Properties
| Name | Meaning |
|---|---|
| Email ID | The unique identifier of the email to update. This is required to specify which email to modify. |
| Additional Fields | Optional extra parameters to include in the update request: |
| - Account ID | The ID of the account associated with the email (used when identifying the provider by UID). |
| - Body (JSON) | A raw JSON object representing the full or partial body of the email update payload. This allows sending custom or complex update data directly. |
Output
The node outputs the response from the Unipile API after attempting to update the specified email. The output is structured as JSON data reflecting the updated email resource or the result of the update operation. If the API returns any binary data related to the email (e.g., attachments), it would be included accordingly, but this node primarily deals with JSON responses.
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 configuration.
- Proper permissions on the API key are necessary to perform email updates.
Troubleshooting
- Missing or invalid Email ID: The node requires a valid email identifier. Ensure that the Email ID property is correctly set and corresponds to an existing email in Unipile.
- API authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Malformed JSON in Body (JSON): If using the raw JSON body field, ensure the JSON syntax is correct; otherwise, the API may reject the request.
- Network or connectivity issues: Confirm that the n8n instance can reach the Unipile API endpoint defined in the credentials.
- Unexpected API errors: Check the error message returned by the API for clues, such as rate limits, invalid fields, or server errors.
Links and References
- Unipile API Documentation (example placeholder link)
- n8n documentation on creating and using API credentials
- JSON formatting guides for constructing valid JSON bodies