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 perform various operations on different resources, including email management. Specifically, for the Email resource and the Create Draft operation, it allows users to create an email draft by sending a raw JSON body representing the draft content. This is useful in scenarios where you want to programmatically prepare email drafts within workflows before sending or further processing them.
Practical examples include:
- Automatically saving email drafts based on form submissions or CRM data.
- Preparing templated emails for review before sending.
- Integrating with other systems to generate draft emails dynamically.
Properties
| Name | Meaning |
|---|---|
| Body (JSON) | Raw JSON body to send when creating a draft. This should contain the full draft details. |
Output
The node outputs the response from the Unipile API after attempting to create the email draft. The output is structured as JSON data under the json field, which typically contains information about the created draft such as its ID, status, and any metadata returned by the API.
If the API supports returning binary data related to the draft (e.g., attachments), the node would handle that accordingly, but based on the provided code and properties, the primary output is JSON.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for the API is configured via credentials.
- The node sends requests with headers specifying JSON content type and expects JSON responses.
Troubleshooting
- Invalid JSON Body: If the JSON provided in the "Body (JSON)" property is malformed, the API will likely reject the request. Ensure the JSON is valid and correctly formatted.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key credential is properly set up.
- API Endpoint Issues: If the base URL or endpoint paths are misconfigured, requests may fail. Confirm the credential's DSN (base URL) is correct.
- Unexpected API Responses: If the API changes or returns errors, check the response message for clues and verify the JSON body matches the expected schema.
Links and References
- Unipile API Documentation (Assumed official API docs)
- n8n documentation on Creating Custom Nodes