Octave icon

Octave

Interact with the Octave V2 API

Actions26

Overview

This node, named "Octave," integrates with the Octave V2 API to generate email sequences tailored for outreach campaigns. Specifically, the Headless - Generate Emails operation creates a multi-step email sequence designed to engage recipients effectively based on customizable parameters such as sequence length, tone, style, and goals.

Typical use cases include:

  • Automating cold outbound email campaigns.
  • Creating follow-up email sequences to nurture leads.
  • Personalizing emails based on recipient and sender details.
  • Generating unique subject lines and varied email content formats (text, HTML, markdown).

For example, a sales team can use this node to automatically generate a 4-step cold outbound email sequence aimed at booking meetings, with each email having a unique subject line and written in a professional tone.

Properties

Name Meaning
Sequence: Steps Number of steps/emails in the generated sequence (minimum 1).
Sequence: Length Length of each email in the sequence; options are Short, Medium, Long, or Mixed.
Sequence: Type Type of email sequence; options are Cold Outbound or Follow Up.
Sequence: Primary Goal Main objective of the sequence; options are Initiate Conversation or Book Meeting.
Sequence: Generate Unique Subject Lines Whether each email should have a unique subject line (true/false).
Sequence: Additional Instructions Extra instructions to guide the email generation process.
Sequence: Example for Intro Email Example text to illustrate the style or content desired for the first email in the sequence.
Sequence: Example for Final Email Example text to illustrate the style or content desired for the final email in the sequence.
Offering: URL URL of the product or service being offered.
Offering: Name Name of the product or service offering.
Offering: Core Value Proposition Core value proposition of the offering; can be plain text or JSON string describing key benefits.
Offering: Key Differentiator What differentiates the offering from competitors; can be plain text or JSON string.
Offering: Customer Outcomes Outcomes customers achieve using the offering; can be plain text or JSON string.
Offering: Additional Info Any additional information about the offering; can be plain text or JSON string.
Recipient: First Name First name of the email recipient.
Recipient: Job Title Job title of the recipient.
Recipient: LinkedIn Profile URL LinkedIn profile URL of the recipient.
Recipient: Additional Info Additional contextual info about the recipient.
Recipient: Company Name Name of the recipient’s company.
Recipient: Company Domain Domain of the recipient’s company (e.g., example.com).
Sender: First Name First name of the email sender.
Sender: Last Name Last name of the email sender.
Sender: Job Title Job title of the sender.
Sender: Company Name Company name of the sender.
Sender: Company Domain Company domain of the sender.
Email: Language Language code for email generation (e.g., "en" for English, "es" for Spanish).
Email: Tone Desired tone of the email, e.g., Professional, Casual, Persuasive.
Email: Style Writing style of the email, e.g., Concise, Detailed.
Email: Output Format Format of the generated email content; options are Text, HTML, or Markdown.
Email: Persona Optional persona to adopt during email generation to influence style or voice.
Additional Context (JSON) A JSON object containing any other custom fields or contextual information to further customize email generation.

Output

The node outputs an array of generated emails corresponding to the requested sequence steps. Each item in the output contains a json field with the generated email content structured according to the selected output format (Text, HTML, or Markdown). The output typically includes:

  • The email body content.
  • Subject lines (unique if enabled).
  • Possibly metadata related to the sequence step.

If binary data were involved (e.g., attachments), it would be summarized here, but this node focuses on textual email generation only.

Dependencies

  • Requires an active connection to the Octave V2 API via an API key credential configured in n8n.
  • No other external dependencies are indicated.
  • Proper API authentication setup in n8n credentials is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Improperly formatted JSON strings in properties like Core Value Proposition or Additional Context may cause parsing errors.
    • Requesting zero or negative sequence steps will likely result in validation errors.
    • Network connectivity issues to the Octave API endpoint.

  • Error Messages:

    • Authentication errors: Verify that the API key credential is correctly set up and has required permissions.
    • JSON parse errors: Ensure all JSON input fields contain valid JSON or plain text as expected.
    • API response errors: Check the error message returned by the API for hints; often caused by invalid parameters or rate limits.

  • Resolution Tips:

    • Validate all JSON inputs before running the node.
    • Use the "Continue On Fail" option cautiously to handle partial failures gracefully.
    • Confirm network access to the Octave API endpoint.
    • Review API usage limits and quotas.

Links and References

Discussion