Actions6
Overview
This node integrates with Utopian Labs AI to assist in researching and engaging with leads, specifically focusing on writing emails as part of lead engagement workflows. The "Write an Email" operation uses AI agents to generate personalized email content based on the lead's company website and additional lead information.
Common scenarios where this node is beneficial include:
- Automating the creation of outreach emails tailored to potential clients or partners.
- Enhancing sales or marketing workflows by generating context-aware email drafts.
- Testing email generation logic without sending actual emails using mock responses.
Practical example:
A sales team wants to send personalized introduction emails to leads from various companies. By providing the lead's company website and other details, the node generates a customized email draft that can be reviewed or sent automatically.
Properties
| Name | Meaning |
|---|---|
| Lead Company Website | The website URL of the lead's company. This is required and used as a primary input for generating the email content. |
| Callback Url | The URL to which the node will send a callback after processing, typically set to the webhook URL of a Wait node configured to listen for POST requests. |
| Return Mock Response | Boolean flag indicating whether to return a mock response instead of running the actual agent. Useful for testing workflows without triggering real API calls. |
| Agent | The AI agent to use for writing the email. Options: "Copywriting Agent", "Copywriting Agent Light". |
| Language | The language variant to use for the email content. Options include British English, American English, Dutch, German, French, Spanish, Portuguese, Italian. |
| Sender Full Name | The full name of the person sending the email. Used to personalize the email signature or sender information. |
| Additional Fields | A collection of optional fields to provide more context about the lead and their company, including: - Lead Company Name - Lead Company Description - Lead Full Name - Lead Business Email Address (must be valid business email) - Lead LinkedIn Profile URL - Lead Job Title - Lead X/Twitter Handle - Max Research Steps (number of research steps to perform, default 5) - Context (additional context for the operation) - Use Memory (boolean to reuse previous research runs where applicable) |
Output
The node outputs JSON data representing the result of the email writing operation. This typically includes the generated email content and any metadata returned by the Utopian Labs AI service.
- The output JSON array contains one item per input item processed.
- Each item includes the AI-generated email text and possibly other related information.
- If the "Return Mock Response" option is enabled, the output will contain a simulated response useful for testing.
- No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Utopian Labs AI service.
- The node expects a Wait node configured to receive POST webhook calls for handling asynchronous callbacks.
- Proper configuration of the callback URL is necessary to receive results.
- Validation is performed on email addresses and URLs to ensure correctness before making API requests.
Troubleshooting
- Invalid Email Address: If the provided lead business email address is not valid or uses a blocked domain, the node throws an error. Ensure the email is a valid business email format and not from a blocked domain.
- Invalid Website URL: If the lead company website URL is malformed or invalid, an error is thrown. Verify the URL format before input.
- Missing Lead Full Name: When any lead-specific information like email, LinkedIn, job title, or social handle is provided, the lead's full name must also be supplied. Otherwise, the node will error out.
- Callback URL Issues: Make sure the callback URL corresponds to a Wait node set to accept POST requests; otherwise, the workflow may hang waiting for a response.
- API Authentication Errors: Ensure the API key credential is correctly configured and has the necessary permissions.
- Use of Mock Response: If testing with mock responses, remember that no real email content is generated, so downstream nodes expecting real data might fail.