Dynamische E-Mail-Sequenzen mit Runtime-Kontext und externen Daten generieren
Fortgeschritten
Dies ist ein Lead Nurturing, Multimodal AI-Bereich Automatisierungsworkflow mit 11 Nodes. Hauptsächlich werden Webhook, Octave, HttpRequest, Agent, LmChatAnthropic und andere Nodes verwendet. Octave, LLM und externe Daten zum Generieren personalisierter E-Mail-Serien verwenden
Voraussetzungen
- •HTTP Webhook-Endpunkt (wird von n8n automatisch generiert)
- •Möglicherweise sind Ziel-API-Anmeldedaten erforderlich
- •Anthropic API Key
Verwendete Nodes (11)
Kategorie
Workflow-Vorschau
Visualisierung der Node-Verbindungen, mit Zoom und Pan
Workflow exportieren
Kopieren Sie die folgende JSON-Konfiguration und importieren Sie sie in n8n
{
"name": "Generate dynamic email sequences with runtime context and external data",
"tags": [],
"nodes": [
{
"id": "sticky-note-main",
"name": "Notiz - Hauptüberblick",
"type": "n8n-nodes-base.stickyNote",
"position": [
450,
-700
],
"parameters": {
"color": 1,
"width": 450,
"height": 500,
"content": "🎯 DYNAMIC EMAIL SEQUENCES WITH RUNTIME CONTEXT\n\nFOR: Growth teams, SDRs, outbound marketers who\nwant to reference real-time prospect information.\n\nSOLVES: Static sequences that can't reference what's\nactually happening at prospect companies right now.\nYou know they're hiring/launched/got funding but\ncan't dynamically reference these timely events.\n\nWORKS:\n1. Webhook gets lead data\n2. External source finds timely context\n3. LLM processes context data\n4. Octave generates sequences with context\n5. Sequences sent to email platform\n\nSETUP: External data source + LLM + Octave\nsequence agent + email platform credentials\n\nCUSTOMIZE: Replace AI agent with your data source\n(jobs, news, enrichment). Configure runtime context\n(WHAT data is) and instructions (HOW to use it).\nCan apply to individual emails or all emails."
},
"typeVersion": 1
},
{
"id": "sticky-note-webhook",
"name": "Notiz - Webhook Einrichtung",
"type": "n8n-nodes-base.stickyNote",
"position": [
40,
-150
],
"parameters": {
"color": 2,
"width": 190,
"height": 100,
"content": "🚀 START HERE\nReplace webhook path.\nConfigure lead source."
},
"typeVersion": 1
},
{
"id": "sticky-note-research",
"name": "Notiz - Kontextrecherche",
"type": "n8n-nodes-base.stickyNote",
"position": [
240,
-150
],
"parameters": {
"color": 4,
"width": 190,
"height": 100,
"content": "🔍 CONTEXT RESEARCH\nReplace with your data source.\nJob boards, news, enrichment."
},
"typeVersion": 1
},
{
"id": "sticky-note-llm",
"name": "Notiz - LLM-Verarbeitung",
"type": "n8n-nodes-base.stickyNote",
"position": [
140,
-300
],
"parameters": {
"color": 5,
"width": 190,
"height": 100,
"content": "🧠 LLM PROCESSING\nAdd your LLM credentials.\nCustomize context extraction."
},
"typeVersion": 1
},
{
"id": "sticky-note-octave",
"name": "Notiz - Octave-Laufzeitumgebung",
"type": "n8n-nodes-base.stickyNote",
"position": [
740,
-150
],
"parameters": {
"color": 3,
"width": 190,
"height": 100,
"content": "⚡ RUNTIME CONTEXT\nOctave + external data.\nConfigure context & instructions."
},
"typeVersion": 1
},
{
"id": "sticky-note-email",
"name": "Notiz - E-Mail-Plattform",
"type": "n8n-nodes-base.stickyNote",
"position": [
1040,
-150
],
"parameters": {
"color": 6,
"width": 190,
"height": 100,
"content": "📧 EMAIL PLATFORM\nDynamic sequences to campaign.\nUpdate platform & variables."
},
"typeVersion": 1
},
{
"id": "07920827-9d73-4099-8b6f-d599be97b929",
"name": "Lead-Daten Webhook",
"type": "n8n-nodes-base.webhook",
"position": [
120,
0
],
"webhookId": "your-webhook-id-here",
"parameters": {
"path": "your-webhook-path-here",
"options": {}
},
"typeVersion": 2
},
{
"id": "4dc666e8-89dd-4647-8aeb-3880fd4aa59e",
"name": "Unternehmenskontext recherchieren",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
320,
0
],
"parameters": {
"text": "=Output the name of an open role that {{ $json.body.companyDomain }} is hiring for. If you can't find a role they are hiring for, make up a basic one that would make sense for them to hire for. Normalize the job title to something that would be used in an internal email (i.e \"software engineer\" instead of \"Sr. Software Engineer II\"). Output just the name of the role and nothing else, with no pretext or posttext. Do NOT make any justification if you can't find a role, just give a dummy role and nothing else. No \"I wasn't able to find...\" BS.",
"options": {},
"promptType": "define"
},
"typeVersion": 2.1
},
{
"id": "45c0b9e7-a035-4469-8a61-7e919502e715",
"name": "LLM-Modell",
"type": "@n8n/n8n-nodes-langchain.lmChatAnthropic",
"position": [
220,
200
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "your-llm-model",
"cachedResultName": "Your LLM Model"
},
"options": {}
},
"credentials": {
"anthropicApi": {
"name": "Your LLM API Credentials"
}
},
"typeVersion": 1.3
},
{
"id": "5a08a3b4-4a19-4112-b97c-b100db4eefd8",
"name": "Sequenz mit Laufzeitkontext generieren",
"type": "n8n-nodes-octavehq.octave",
"position": [
820,
0
],
"parameters": {
"agentOId": "your-octave-sequence-agent-id",
"jobTitle": "={{ $('Lead Data Webhook').item.json.body.jobTitle }}",
"firstName": "={{ $('Lead Data Webhook').item.json.body.firstName }}",
"operation": "runSequence",
"companyName": "={{ $('Lead Data Webhook').item.json.body.companyName }}",
"companyDomain": "={{ $('Lead Data Webhook').item.json.body.companyDomain }}",
"linkedInProfile": "={{ $('Lead Data Webhook').item.json.body.profileURL }}",
"runtimeContextStep1": "=they are hiring a {{ $json.output }}",
"runtimeInstructionsStep1": "mention the role they're hiring for and that's why you reached out"
},
"credentials": {
"octaveApi": {
"name": "Octave API Credentials"
}
},
"typeVersion": 1
},
{
"id": "4ae4986a-547e-4d67-9d68-0774c1dc9ab7",
"name": "Lead zu E-Mail-Kampagne hinzufügen",
"type": "n8n-nodes-base.httpRequest",
"position": [
1120,
0
],
"parameters": {
"url": "https://api.instantly.ai/api/v2/leads",
"method": "POST",
"options": {},
"sendBody": true,
"sendHeaders": true,
"authentication": "genericCredentialType",
"bodyParameters": {
"parameters": [
{
"name": "campaign",
"value": "your-campaign-id-here"
},
{
"name": "email",
"value": "={{ $('Lead Data Webhook').item.json.body.email }}"
},
{
"name": "first_name",
"value": "={{ $('Lead Data Webhook').item.json.body.firstName }}"
},
{
"name": "last_name",
"value": "={{ $('Lead Data Webhook').item.json.body.lastName }}"
},
{
"name": "company_name",
"value": "={{ $('Lead Data Webhook').item.json.body.companyName }}"
},
{
"name": "custom_variables",
"value": "={{ { \"email1\": $json.emails[0].email || \"\", \"subject1\": $json.emails[0].subject || \"\", \"email2\": $json.emails[1].email || \"\", \"subject2\": $json.emails[1].subject || \"\", \"email3\": $json.emails[2].email || \"\", \"subject3\": $json.emails[2].subject || \"\" } }}"
}
]
},
"genericAuthType": "httpBearerAuth",
"headerParameters": {
"parameters": [
{
"name": "Content-Type",
"value": "application/json"
}
]
}
},
"credentials": {
"httpBearerAuth": {
"name": "Email Platform API Key"
}
},
"typeVersion": 4.2
}
],
"active": false,
"pinData": {},
"settings": {
"executionOrder": "v1"
},
"connections": {
"45c0b9e7-a035-4469-8a61-7e919502e715": {
"ai_languageModel": [
[
{
"node": "4dc666e8-89dd-4647-8aeb-3880fd4aa59e",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"07920827-9d73-4099-8b6f-d599be97b929": {
"main": [
[
{
"node": "4dc666e8-89dd-4647-8aeb-3880fd4aa59e",
"type": "main",
"index": 0
}
]
]
},
"4dc666e8-89dd-4647-8aeb-3880fd4aa59e": {
"main": [
[
{
"node": "5a08a3b4-4a19-4112-b97c-b100db4eefd8",
"type": "main",
"index": 0
}
]
]
},
"5a08a3b4-4a19-4112-b97c-b100db4eefd8": {
"main": [
[
{
"node": "4ae4986a-547e-4d67-9d68-0774c1dc9ab7",
"type": "main",
"index": 0
}
]
]
}
}
}Häufig gestellte Fragen
Wie verwende ich diesen Workflow?
Kopieren Sie den obigen JSON-Code, erstellen Sie einen neuen Workflow in Ihrer n8n-Instanz und wählen Sie "Aus JSON importieren". Fügen Sie die Konfiguration ein und passen Sie die Anmeldedaten nach Bedarf an.
Für welche Szenarien ist dieser Workflow geeignet?
Fortgeschritten - Lead-Pflege, Multimodales KI
Ist es kostenpflichtig?
Dieser Workflow ist völlig kostenlos. Beachten Sie jedoch, dass Drittanbieterdienste (wie OpenAI API), die im Workflow verwendet werden, möglicherweise kostenpflichtig sind.
Verwandte Workflows
Komplette Account-basierte Reach-Automatisierung mit Octave-Kontextengine
Automatisierung des Prozesses von ABM-Recherche bis zur Kontaktaufnahme mit Octave, KI und Instantly.ai
Filter
Webhook
Split Out
+
Filter
Webhook
Split Out
19 NodesNalin
Lead-Pflege
KI-gesteuertes Lebensmittelbestellverarbeitungssystem, integriert mit Facebook Messenger, Google Tabellen und Kalender
KI-gesteuertes Lebensmittelbestellverarbeitungssystem, integriert mit Facebook Messenger, Google Tabellen und Kalender
If
Code
Webhook
+
If
Code
Webhook
26 NodesHans Wilhelm Radam
Lead-Pflege
Neu-Ranking #1
Automatisierung des Telefonmarketings durch Web-Scraping, GPT-4o und WhatsApp
Set
Code
Webhook
+
Set
Code
Webhook
48 NodesKhaisa Studio
Lead-Pflege
Intelligente Nachverfolgung von Veranstaltungen und Social Media-Assistent
Automatisierung der Nachfassaktionen für Kampagnen mit mehrkanaligem Outreach über GPT-4, LinkedIn und HubSpot
Code
Filter
Hubspot
+
Code
Filter
Hubspot
25 NodesOneclick AI Squad
Lead-Pflege
09 - Lead-Profil-Verbesserer
Automatisierung der Lead-Anreicherung und personalisierten Ansprache: HubSpot, Phantombuster und GPT
If
Set
Code
+
If
Set
Code
30 NodesAvkash Kakdiya
Lead-Pflege
Intelligente Immobilien-E-Mail- und Telefonmarketing-Kampagne mit KI-generierten Leads
Automatisierung der Immobilienmarketing mit Llama AI, VAPI-Anrufen und Gmail-Kampagnen
Code
Wait
Gmail
+
Code
Wait
Gmail
23 NodesOneclick AI Squad
Lead-Pflege
Workflow-Informationen
Schwierigkeitsgrad
Fortgeschritten
Anzahl der Nodes11
Kategorie2
Node-Typen6
Autor
Nalin
@nalinkrishnanExterne Links
Auf n8n.io ansehen →
Diesen Workflow teilen