Sebastian/OptiLever This workflow corresponds to n8n.io template #5622 — we link there as the canonical source.
This workflow follows the Agent → Gmail recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"id": "z5I7hevqasiIz2qD",
"name": "SWOT Analysis Generator That Produces PDF Reports",
"tags": [
{
"id": "o58aq7CrdbXQHYA0",
"name": "template",
"createdAt": "2025-06-14T10:20:41.387Z",
"updatedAt": "2025-06-14T10:20:41.387Z"
}
],
"nodes": [
{
"id": "aa51bba9-bf2b-4566-a1af-352e75661ecd",
"name": "When clicking \u2018Test workflow\u2019",
"type": "n8n-nodes-base.manualTrigger",
"position": [
1080,
860
],
"parameters": {},
"typeVersion": 1
},
{
"id": "c3d74eee-3257-4e3d-a51b-fab1ebd67feb",
"name": "Google Sheets",
"type": "n8n-nodes-base.googleSheets",
"position": [
1300,
860
],
"parameters": {
"options": {},
"sheetName": {
"__rl": true,
"mode": "list",
"value": "gid=0",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/19k1nKNIj8J63e4LoR2yVDq2YN5fOFMHBOpMnrakLNOM/edit#gid=0",
"cachedResultName": "Company Info Input"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "19k1nKNIj8J63e4LoR2yVDq2YN5fOFMHBOpMnrakLNOM",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/19k1nKNIj8J63e4LoR2yVDq2YN5fOFMHBOpMnrakLNOM/edit?usp=drivesdk",
"cachedResultName": "SWOT Analysis"
}
},
"typeVersion": 4.5
},
{
"id": "a977708a-036f-4826-8790-8325ad8cae31",
"name": "AI Agent",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
1520,
860
],
"parameters": {
"text": "=**Company Name:** {{ $json[\"Company Name\"] }}\n\n**Industry:** {{ $json.Industry }}\n\n**Business Size:** {{ $json[\"Business Size\"] }}\n\n**Market Region:** {{ $json[\"Market Region\"] }}\n\n**Unique Value Proposition:** {{ $json[\"Unique Value Proposition\"] }}\n\n**Company Overview:** {{ $json[\"Company Overview\"] }}\n\n**Customer Base:** {{ $json[\"Customer Base\"] }}\n\n**Acquired Resources:** {{ $json[\"Acquired Resources\"] }}\n\n**Financials:** {{ $json.Financials }}\n\n**Team Expertise:** {{ $json[\"Team Expertise\"] }}\n\n**Known Weaknesses:** {{ $json[\"Known Weaknesses\"] }}\n\n**Customer Feedback:** {{ $json[\"Customer Feedback\"] }}\n\n**Market Trends:** {{ $json[\"Market Trends\"] }}\n\n**Competitors:** {{ $json.Competitors }}\n\n**Legal/Regulatory Environment:** {{ $json[\"Legal/Regulatory Environment\"] }}\n\n**Tech Developments:** {{ $json[\"Tech Developments\"] }}\n\n**Threats (Potential Threats):** {{ $json[\"Threats (Potential Threats)\"] }}\n\n**Short-Term Goals:** {{ $json[\"Short-Term Goals\"] }}\n\n**Long-Term Goals:** {{ $json[\"Long-Term Goals\"] }}",
"options": {
"systemMessage": "=<system_prompt>\nYOU ARE A STRUCTURED SWOT EXTRACTION AGENT DESIGNED TO PROCESS RAW BUSINESS TEXT AND OUTPUT A CLEAN, PARSEABLE SWOT MAP. YOU **DO NOT INTERPRET, SUMMARIZE, OR ANALYZE**. YOUR ONLY TASK IS TO **EXTRACT PHRASES OR SENTENCES** THAT **CLEARLY ALIGN WITH ONE AND ONLY ONE** OF THE FOUR SWOT CATEGORIES.\n\n### OBJECTIVE ###\nEXTRACT AND STRUCTURE INPUT INFORMATION INTO A JSON OBJECT WITH FOUR ARRAYS:\n- `strengths`: INTERNAL POSITIVE FACTORS\n- `weaknesses`: INTERNAL NEGATIVE FACTORS\n- `opportunities`: EXTERNAL POSITIVE FACTORS\n- `threats`: EXTERNAL NEGATIVE FACTORS\n\nYOU MUST:\n- READ full paragraphs or blocks of business input\n- ISOLATE ONLY SWOT-RELEVANT SENTENCES OR CLAUSES\n- EXCLUDE all neutral, vague, or non-actionable content\n- OUTPUT ONLY the extracted statements as plain strings in their respective arrays\n\n### STRICT RULES ###\n- DO NOT COPY WHOLE PARAGRAPHS\n- DO NOT REWRITE OR REPHRASE CONTENT\n- DO NOT INCLUDE UNCLEAR, MIXED, OR NON-SWOT DATA\n- DO NOT ADD EXPLANATIONS OR ANY TEXT OUTSIDE THE JSON OUTPUT\n\n### CHAIN OF THOUGHTS (MANDATORY LOGIC FLOW) ###\n\n1. **UNDERSTAND** the full input text\n2. **IDENTIFY** standalone sentences or clauses that describe a clear SWOT element\n3. **CLASSIFY** each by determining:\n - INTERNAL + POSITIVE = `strength`\n - INTERNAL + NEGATIVE = `weakness`\n - EXTERNAL + POSITIVE = `opportunity`\n - EXTERNAL + NEGATIVE = `threat`\n4. **ISOLATE** only the specific sentence or clause representing that category\n5. **BUILD** a JSON object structured as:\n\n```json\n{\n \"strengths\": [\"strength 1\", \"strength 2\"],\n \"weaknesses\": [\"weakness 1\", \"weakness 2\"],\n \"opportunities\": [\"opportunity 1\", \"opportunity 2\"],\n \"threats\": [\"threat 1\", \"threat 2\"]\n}\n```\n\n6. **FILTER OUT** anything ambiguous, irrelevant, or non-categorizable\n\n### FEW-SHOT EXAMPLE ###\n\n#### INPUT:\n\"While our logistics suffered under supply chain disruptions in 2021 and 2022, recent upgrades have drastically reduced shipping delays. We now deliver 85% of orders within 2 days. However, cyber risk continues to rise in our sector. There's also a growing demand in Southeast Asia for products like ours.\"\n\n#### OUTPUT:\n```json\n{\n \"strengths\": [\"We now deliver 85% of orders within 2 days\", \"recent upgrades have drastically reduced shipping delays\"],\n \"weaknesses\": [\"logistics suffered under supply chain disruptions in 2021 and 2022\"],\n \"opportunities\": [\"growing demand in Southeast Asia for products like ours\"],\n \"threats\": [\"cyber risk continues to rise in our sector\"]\n}\n```\n\n### WHAT NOT TO DO ###\n\n- DO NOT OUTPUT FULL PARAGRAPHS OR MIXED SENTENCES\n- NEVER INTERPRET IMPLIED MEANING OR CONTEXTUAL HINTS\n- NEVER REPHRASE, REWRITE, OR SUMMARIZE THE USER\u2019S INPUT\n- DO NOT ADD COMMENTS, HEADERS, OR ANY NON-JSON CONTENT\n- DO NOT ASSUME SWOT CATEGORIZATION IF THE SIGNAL IS UNCLEAR\n- AVOID ALL \"FILLER\" OUTPUT \u2014 RETURN ONLY CATEGORIZED, RELEVANT TEXT\n\n</system_prompt>\n"
},
"promptType": "define",
"hasOutputParser": true
},
"typeVersion": 1.8
},
{
"id": "73ce5d23-a2a4-4aa8-86d9-93080461080d",
"name": "Structured Output Parser",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
1700,
1080
],
"parameters": {
"jsonSchemaExample": "{\n \"strengths\": [\"We now deliver 85% of orders within 2 days\", \"recent upgrades have drastically reduced shipping delays\"],\n \"weaknesses\": [\"logistics suffered under supply chain disruptions in 2021 and 2022\"],\n \"opportunities\": [\"growing demand in Southeast Asia for products like ours\"],\n \"threats\": [\"cyber risk continues to rise in our sector\"]\n}"
},
"typeVersion": 1.2
},
{
"id": "14a91c36-ebad-443a-9dcd-0e398f94e0f7",
"name": "OpenAI Chat Model",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
1540,
1080
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4.1-mini",
"cachedResultName": "gpt-4.1-mini"
},
"options": {}
},
"typeVersion": 1.2
},
{
"id": "915ef61b-61dd-4bcc-94cc-e1291a918a24",
"name": "Strengths Analysis",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
1900,
560
],
"parameters": {
"text": "=**Company Name:** {{ $('Google Sheets').item.json[\"Company Name\"] }}\n\n**Industry:** {{ $('Google Sheets').item.json.Industry }}\n\n**Business Size:** {{ $('Google Sheets').item.json[\"Business Size\"] }}\n\n**Market Region:** {{ $('Google Sheets').item.json[\"Market Region\"] }}\n\n**Unique Value Proposition:** {{ $('Google Sheets').item.json[\"Unique Value Proposition\"] }}\n\n**Company Overview:** {{ $('Google Sheets').item.json[\"Company Overview\"] }}\n\n**Customer Base:** {{ $('Google Sheets').item.json[\"Customer Base\"] }}\n\n**Acquired Resources:** {{ $('Google Sheets').item.json[\"Acquired Resources\"] }}\n\n**Financials:** {{ $('Google Sheets').item.json.Financials }}\n\n**Team Expertise:** {{ $('Google Sheets').item.json[\"Team Expertise\"] }}\n\n**Known Weaknesses:** {{ $('Google Sheets').item.json[\"Known Weaknesses\"] }}\n\n**Customer Feedback:** {{ $('Google Sheets').item.json[\"Customer Feedback\"] }}\n\n**Market Trends:** {{ $('Google Sheets').item.json[\"Market Trends\"] }}\n\n**Competitors:** {{ $('Google Sheets').item.json.Competitors }}\n\n**Legal/Regulatory Environment:** {{ $('Google Sheets').item.json[\"Legal/Regulatory Environment\"] }}\n\n**Tech Developments:** {{ $('Google Sheets').item.json[\"Tech Developments\"] }}\n\n**Threats (Potential Threats):** {{ $('Google Sheets').item.json[\"Threats (Potential Threats)\"] }}\n\n**Short-Term Goals:** {{ $('Google Sheets').item.json[\"Short-Term Goals\"] }}\n\n**Long-Term Goals:** {{ $('Google Sheets').item.json[\"Long-Term Goals\"] }}\n\n**STRENGTHS SECTION:** {{ $json.output.strengths }}",
"options": {
"systemMessage": "=<system prompt>\nALWAYS ANSWER TO THE USER IN THE MAIN LANGUAGE OF THEIR MESSAGE; \nYOU ARE A WORLD-CLASS STRATEGIC BUSINESS ANALYST AND INVESTOR REPORT AUTHOR, TASKED WITH CRAFTING A FULLY-FORMATTED \u201cSTRENGTHS\u201d SECTION FOR AN INVESTOR-FACING REPORT. YOUR INPUTS INCLUDE COMPANY OVERVIEW INFORMATION AND A SEPARATELY IDENTIFIED LIST OF SWOT \u201cSTRENGTHS.\u201d YOUR MISSION IS TO TRANSLATE THESE INTO A STRATEGICALLY-ORGANIZED, FULLY-DEVELOPED, AND INVESTOR-PERSUASIVE NARRATIVE THAT SHOWS NOT JUST WHAT THE STRENGTHS ARE \u2014 BUT HOW THEY CREATE SYSTEMIC ADVANTAGE.\n\n<instructions>\n- WRITE A FULLY DEVELOPED, MULTI-PARAGRAPH \u201cSTRENGTHS\u201d SECTION SUITABLE FOR DIRECT INCLUSION IN A PREMIUM INVESTOR REPORT \n- USE MEANINGFUL, STRATEGICALLY DISTINCT SECTION HEADINGS TO ORGANIZE CONTENT \u2014 USE AS MANY AS NEEDED TO REFLECT THE TRUE THEMATIC LANDSCAPE \n- GROUP RELATED STRENGTHS INTO COHESIVE CLUSTERS \u2014 AVOID UNNECESSARY FRAGMENTATION \n- FOR EACH SECTION:\n \u2022 INTERPRET THE STRATEGIC SIGNIFICANCE OF THE STRENGTHS \u2014 NOT JUST RESTATE THEM \n \u2022 CONNECT EACH STRENGTH TO A SPECIFIC BUSINESS ADVANTAGE (e.g., pricing power, defensibility, capital efficiency, customer retention, speed to scale) \n \u2022 GO BEYOND FIRST-ORDER EFFECTS \u2014 EXPLAIN SECONDARY AND COMPOUNDING IMPACTS \n \u2022 WHERE APPROPRIATE, CONTRAST WITH MARKET ALTERNATIVES OR COMPETITOR WEAKNESSES \n \u2022 INCLUDE FORWARD-LOOKING IMPLICATIONS \u2014 HOW STRENGTHS UNLOCK FUTURE REVENUE OR OPTIONALITY \n \u2022 WHEN USING METRICS (E.G. MARGINS, RETENTION), BRIEFLY COMPARE TO INDUSTRY NORMS FOR CONTEXT \n- USE FLUENT STRATEGIC LANGUAGE AND MAINTAIN CONFIDENT, ANALYTICAL TONE \n- INCLUDE A SYNTHESIS PARAGRAPH THAT SHOWS HOW THE STRENGTHS FORM A SELF-REINFORCING SYSTEM OF ADVANTAGE \u2014 VARY METAPHORS (E.G., \u201cECOSYSTEM,\u201d \u201cLOOP,\u201d \u201cMACHINE\u201d) TO AVOID REPETITION\n\n</instructions>\n\n<what not to do>\n- DO NOT REPEAT INPUTS WITHOUT STRATEGIC ANALYSIS \n- DO NOT OVERLOAD PARAGRAPHS WITH RAW DATA \u2014 PRIORITIZE STRATEGIC CLARITY \n- NEVER USE GENERIC STATEMENTS (\u201cthe company is strong at X\u201d) \u2014 MAKE EVERY CLAIM STRATEGICALLY MEANINGFUL \n- DO NOT OMIT ANY STRENGTHS \u2014 BUT YOU MAY COMBINE THEM STRATEGICALLY \n- NEVER PRESENT STRENGTHS IN ISOLATION \u2014 ALWAYS LINK THEM INTO A SYSTEM OF ADVANTAGE \n- AVOID USING THE SAME STRATEGIC METAPHOR MULTIPLE TIMES \u2014 KEEP THE LANGUAGE FRESH AND FLUID \n</what not to do>\n</system prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "03832276-84e9-4452-9fa0-385ce186ade0",
"name": "Weaknesses Analysis",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
1900,
780
],
"parameters": {
"text": "=**Company Name:** {{ $('Google Sheets').item.json[\"Company Name\"] }}\n\n**Industry:** {{ $('Google Sheets').item.json.Industry }}\n\n**Business Size:** {{ $('Google Sheets').item.json[\"Business Size\"] }}\n\n**Market Region:** {{ $('Google Sheets').item.json[\"Market Region\"] }}\n\n**Unique Value Proposition:** {{ $('Google Sheets').item.json[\"Unique Value Proposition\"] }}\n\n**Company Overview:** {{ $('Google Sheets').item.json[\"Company Overview\"] }}\n\n**Customer Base:** {{ $('Google Sheets').item.json[\"Customer Base\"] }}\n\n**Acquired Resources:** {{ $('Google Sheets').item.json[\"Acquired Resources\"] }}\n\n**Financials:** {{ $('Google Sheets').item.json.Financials }}\n\n**Team Expertise:** {{ $('Google Sheets').item.json[\"Team Expertise\"] }}\n\n**Known Weaknesses:** {{ $('Google Sheets').item.json[\"Known Weaknesses\"] }}\n\n**Customer Feedback:** {{ $('Google Sheets').item.json[\"Customer Feedback\"] }}\n\n**Market Trends:** {{ $('Google Sheets').item.json[\"Market Trends\"] }}\n\n**Competitors:** {{ $('Google Sheets').item.json.Competitors }}\n\n**Legal/Regulatory Environment:** {{ $('Google Sheets').item.json[\"Legal/Regulatory Environment\"] }}\n\n**Tech Developments:** {{ $('Google Sheets').item.json[\"Tech Developments\"] }}\n\n**Threats (Potential Threats):** {{ $('Google Sheets').item.json[\"Threats (Potential Threats)\"] }}\n\n**Short-Term Goals:** {{ $('Google Sheets').item.json[\"Short-Term Goals\"] }}\n\n**Long-Term Goals:** {{ $('Google Sheets').item.json[\"Long-Term Goals\"] }}\n\n**WEAKNESSES SECTION:** {{ $json.output.weaknesses }}",
"options": {
"systemMessage": "=<system prompt>\nALWAYS ANSWER TO THE USER IN THE MAIN LANGUAGE OF THEIR MESSAGE; \nYOU ARE A HIGHLY EXPERIENCED STRATEGIC BUSINESS ANALYST AND INVESTOR REPORT AUTHOR. YOUR JOB IS TO CRAFT THE \u201cWEAKNESSES\u201d SECTION OF AN INVESTOR REPORT USING COMPANY BACKGROUND INFORMATION AND A SEPARATELY PROVIDED LIST OF SWOT \u201cWEAKNESSES.\u201d THIS SECTION MUST BALANCE STRATEGIC HONESTY WITH CONSTRUCTIVE FRAMING \u2014 EACH WEAKNESS SHOULD BE EXPLAINED IN TERMS OF STRATEGIC IMPACT, RELEVANCE, AND REMEDIATION.\n\n<instructions>\n- WRITE A COMPLETE, MULTI-PARAGRAPH \u201cWEAKNESSES\u201d SECTION SUITABLE FOR DIRECT INCLUSION IN A SOPHISTICATED INVESTOR REPORT \n- USE STRATEGICALLY RELEVANT SECTION HEADINGS TO ORGANIZE CONTENT \u2014 GROUP RELATED WEAKNESSES TO AVOID FRAGMENTATION; USE AS MANY HEADINGS AS NEEDED FOR CLARITY \n- FOR EACH SECTION:\n \u2022 EXPLAIN WHY THE WEAKNESS MATTERS STRATEGICALLY (e.g., customer risk, margin impact, scalability constraint) \n \u2022 IDENTIFY ANY ROOT CAUSES, SYSTEMIC IMPLICATIONS, OR INTERACTIONS WITH OTHER AREAS OF THE BUSINESS \n \u2022 DETAIL CURRENT OR PLANNED REMEDIATION EFFORTS \u2014 INCLUDING HIRING, SYSTEMS, TECH, OR STRATEGIC SHIFTS \n \u2022 WHEN APPROPRIATE, SHOW HOW THE WEAKNESS MAY BECOME A STRENGTH OVER TIME (E.G., EARLY-STAGE GROWTH PHASE, DISCIPLINED TRADEOFF, PLATFORM LEVERAGING) \n \u2022 MAINTAIN STRATEGIC TONE: NEUTRAL, CALM, CONFIDENT \u2014 NEVER DEFENSIVE OR EMOTIONAL \n- INCLUDE A FINAL SYNTHESIS PARAGRAPH SUMMARIZING THE OVERALL RISK PROFILE AND WHY THE TEAM IS POSITIONED TO EXECUTE THROUGH THESE CONSTRAINTS\n\n</instructions>\n\n<what not to do>\n- NEVER WRITE A SHORT SUMMARY OR ONE-PARAGRAPH RESPONSE \u2014 THIS IS A FULL STRATEGIC SECTION \n- DO NOT PRESENT A BULLET LIST OR SIMPLY REPHRASE INPUTS \u2014 PARAGRAPH-BASED STRATEGIC ANALYSIS IS REQUIRED \n- DO NOT OMIT ANY LISTED WEAKNESSES \u2014 YOU MAY GROUP THEM STRATEGICALLY, BUT EACH MUST BE ADDRESSED \n- DO NOT USE NEGATIVE OR BLAMING LANGUAGE \u2014 THIS IS A PROFESSIONAL INVESTOR DOCUMENT \n- DO NOT MAKE GENERIC OR VAGUE STATEMENTS \u2014 ALWAYS CLARIFY WHY THE ISSUE MATTERS, HOW IT\u2019S BEING ADDRESSED, AND WHAT THE IMPLICATIONS ARE \n- AVOID OVERFRAGMENTING INTO TOO MANY HEADINGS \u2014 GROUP THEMES WHEN POSSIBLE TO MAINTAIN STRATEGIC COHERENCE \n</what not to do>\n</system prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "1fd46f91-2eac-4f08-8d66-8398d2aef814",
"name": "Opportunities Analysis",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
1900,
1000
],
"parameters": {
"text": "=**Company Name:** {{ $('Google Sheets').item.json[\"Company Name\"] }}\n\n**Industry:** {{ $('Google Sheets').item.json.Industry }}\n\n**Business Size:** {{ $('Google Sheets').item.json[\"Business Size\"] }}\n\n**Market Region:** {{ $('Google Sheets').item.json[\"Market Region\"] }}\n\n**Unique Value Proposition:** {{ $('Google Sheets').item.json[\"Unique Value Proposition\"] }}\n\n**Company Overview:** {{ $('Google Sheets').item.json[\"Company Overview\"] }}\n\n**Customer Base:** {{ $('Google Sheets').item.json[\"Customer Base\"] }}\n\n**Acquired Resources:** {{ $('Google Sheets').item.json[\"Acquired Resources\"] }}\n\n**Financials:** {{ $('Google Sheets').item.json.Financials }}\n\n**Team Expertise:** {{ $('Google Sheets').item.json[\"Team Expertise\"] }}\n\n**Known Weaknesses:** {{ $('Google Sheets').item.json[\"Known Weaknesses\"] }}\n\n**Customer Feedback:** {{ $('Google Sheets').item.json[\"Customer Feedback\"] }}\n\n**Market Trends:** {{ $('Google Sheets').item.json[\"Market Trends\"] }}\n\n**Competitors:** {{ $('Google Sheets').item.json.Competitors }}\n\n**Legal/Regulatory Environment:** {{ $('Google Sheets').item.json[\"Legal/Regulatory Environment\"] }}\n\n**Tech Developments:** {{ $('Google Sheets').item.json[\"Tech Developments\"] }}\n\n**Threats (Potential Threats):** {{ $('Google Sheets').item.json[\"Threats (Potential Threats)\"] }}\n\n**Short-Term Goals:** {{ $('Google Sheets').item.json[\"Short-Term Goals\"] }}\n\n**Long-Term Goals:** {{ $('Google Sheets').item.json[\"Long-Term Goals\"] }}\n\n**OPPORTUNITIES SECTION:** {{ $json.output.opportunities }}",
"options": {
"systemMessage": "=<system prompt>\nALWAYS ANSWER TO THE USER IN THE MAIN LANGUAGE OF THEIR MESSAGE; \nYOU ARE A WORLD-CLASS STRATEGIC BUSINESS ANALYST AND INVESTOR REPORT AUTHOR, TASKED WITH WRITING THE \u201cOPPORTUNITIES\u201d SECTION OF A PROFESSIONAL INVESTOR REPORT. YOU ARE GIVEN A COMPANY PROFILE AND A SEPARATE LIST OF SWOT \u201cOPPORTUNITIES.\u201d YOUR ROLE IS TO TRANSLATE THESE INTO A STRATEGICALLY ORGANIZED, FULLY DEVELOPED, AND INVESTOR-PERSUASIVE NARRATIVE THAT SHOWS HOW THESE OPPORTUNITIES CAN DRIVE GROWTH, ADVANTAGE, AND LONG-TERM VALUE CREATION.\n\n<instructions>\n- WRITE A MULTI-PARAGRAPH, INVESTOR-READY \u201cOPPORTUNITIES\u201d SECTION SUITABLE FOR DIRECT INCLUSION IN A STRATEGIC REPORT OR PITCH DECK \n- ORGANIZE OPPORTUNITIES UNDER STRATEGICALLY MEANINGFUL THEMES \u2014 USE AS MANY SECTION HEADINGS AS NEEDED TO GROUP AND EXPLAIN CLEARLY, WITHOUT FRAGMENTING THE NARRATIVE \n- FOR EACH SECTION:\n \u2022 EXPLAIN WHY THE OPPORTUNITY EXISTS (e.g., market demand, regulatory support, changing consumer behavior, adjacent category gaps) \n \u2022 SHOW HOW IT CONNECTS TO THE COMPANY\u2019S EXISTING CAPABILITIES (team, tech stack, brand trust, distribution model, etc.) \n \u2022 ANALYZE THE BUSINESS IMPACT: How could it improve revenue growth, margins, defensibility, retention, or market share? \n \u2022 WHEN RELEVANT, DESCRIBE COMPOUNDING EFFECTS \u2014 HOW OPPORTUNITIES MAY AMPLIFY ONE ANOTHER OR BUILD ON EXISTING STRENGTHS \n \u2022 HIGHLIGHT TIME HORIZONS OR ENTRY POINTS (e.g., near-term pilots, long-term platform bets, policy tailwinds) \n- USE STRATEGIC, FLUENT, AND OPTIMISTIC LANGUAGE \u2014 CONFIDENT BUT GROUNDED \n- INCLUDE A FINAL SYNTHESIS PARAGRAPH THAT SUMMARIZES HOW THESE OPPORTUNITIES CREATE A PIPELINE FOR VALUE CREATION AND STRATEGIC SCALE \n\n</instructions>\n\n<what not to do>\n- NEVER WRITE A SHORT SUMMARY \u2014 THIS IS A STRATEGIC GROWTH ANALYSIS, NOT A ONE-PARAGRAPH OUTLOOK \n- DO NOT JUST RESTATE OR LIST THE INPUT OPPORTUNITIES \u2014 YOU MUST SYNTHESIZE THEM INTO A STRATEGIC NARRATIVE \n- NEVER INTRODUCE OPPORTUNITIES NOT PRESENT IN THE INPUT DATA \n- DO NOT USE HYPE, EMPTY ADJECTIVES, OR UNVERIFIABLE CLAIMS \u2014 MAINTAIN STRATEGIC CREDIBILITY \n- DO NOT OMIT ANY OF THE PROVIDED OPPORTUNITIES \u2014 YOU MAY GROUP THEM INTO THEMES, BUT ALL MUST BE ADDRESSED \n- AVOID OVERFRAGMENTATION \u2014 GROUP OPPORTUNITIES STRATEGICALLY TO MAINTAIN NARRATIVE COHERENCE \n</what not to do>\n</system prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "af460882-1f89-485f-bd6d-0b1e0e72853b",
"name": "Threats Analysis",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
1900,
1220
],
"parameters": {
"text": "=**Company Name:** {{ $('Google Sheets').item.json[\"Company Name\"] }}\n\n**Industry:** {{ $('Google Sheets').item.json.Industry }}\n\n**Business Size:** {{ $('Google Sheets').item.json[\"Business Size\"] }}\n\n**Market Region:** {{ $('Google Sheets').item.json[\"Market Region\"] }}\n\n**Unique Value Proposition:** {{ $('Google Sheets').item.json[\"Unique Value Proposition\"] }}\n\n**Company Overview:** {{ $('Google Sheets').item.json[\"Company Overview\"] }}\n\n**Customer Base:** {{ $('Google Sheets').item.json[\"Customer Base\"] }}\n\n**Acquired Resources:** {{ $('Google Sheets').item.json[\"Acquired Resources\"] }}\n\n**Financials:** {{ $('Google Sheets').item.json.Financials }}\n\n**Team Expertise:** {{ $('Google Sheets').item.json[\"Team Expertise\"] }}\n\n**Known Weaknesses:** {{ $('Google Sheets').item.json[\"Known Weaknesses\"] }}\n\n**Customer Feedback:** {{ $('Google Sheets').item.json[\"Customer Feedback\"] }}\n\n**Market Trends:** {{ $('Google Sheets').item.json[\"Market Trends\"] }}\n\n**Competitors:** {{ $('Google Sheets').item.json.Competitors }}\n\n**Legal/Regulatory Environment:** {{ $('Google Sheets').item.json[\"Legal/Regulatory Environment\"] }}\n\n**Tech Developments:** {{ $('Google Sheets').item.json[\"Tech Developments\"] }}\n\n**Threats (Potential Threats):** {{ $('Google Sheets').item.json[\"Threats (Potential Threats)\"] }}\n\n**Short-Term Goals:** {{ $('Google Sheets').item.json[\"Short-Term Goals\"] }}\n\n**Long-Term Goals:** {{ $('Google Sheets').item.json[\"Long-Term Goals\"] }}\n\n**THREATS SECTION:** {{ $json.output.threats }}",
"options": {
"systemMessage": "=<system prompt>\nALWAYS ANSWER TO THE USER IN THE MAIN LANGUAGE OF THEIR MESSAGE; \nYOU ARE A WORLD-CLASS STRATEGIC BUSINESS ANALYST AND INVESTOR REPORT AUTHOR, TASKED WITH DRAFTING THE \u201cTHREATS\u201d SECTION OF A PROFESSIONAL INVESTOR REPORT. YOU ARE PROVIDED WITH COMPANY INFORMATION AND A SEPARATE LIST OF SWOT \u201cTHREATS.\u201d YOUR JOB IS TO CONVERT THESE INTO A STRATEGICALLY ORGANIZED, FULLY DEVELOPED, AND INVESTOR-READY NARRATIVE THAT EXPLAINS RISK REALITIES WHILE DEMONSTRATING THE COMPANY\u2019S STRATEGIC AWARENESS AND MITIGATION CAPABILITY.\n\n<instructions>\n- WRITE A MULTI-PARAGRAPH \u201cTHREATS\u201d SECTION SUITABLE FOR SOPHISTICATED INVESTORS \n- ORGANIZE THE SECTION UNDER STRATEGICALLY RELEVANT HEADINGS THAT GROUP RELATED RISKS \u2014 USE AS MANY AS NEEDED TO AVOID FRAGMENTATION OR REDUNDANCY \n- FOR EACH THREAT OR GROUP OF RELATED THREATS:\n \u2022 EXPLAIN WHAT THE RISK IS AND WHY IT MATTERS IN STRATEGIC OR OPERATIONAL TERMS (e.g., margin compression, platform reliability, supply continuity, CAC volatility) \n \u2022 SHOW WHY THIS RISK IS PARTICULARLY RELEVANT TO THE COMPANY\u2019S CURRENT STAGE, STRATEGY, OR BUSINESS MODEL \n \u2022 EXPLAIN WHAT THE COMPANY IS DOING TO MONITOR, MITIGATE, OR OFFSET THE RISK \n \u2022 WHEN RELEVANT, IDENTIFY ANY SCENARIOS WHERE THE THREAT COULD BECOME AN ADVANTAGE (E.G., A FORCED INNOVATION PATHWAY OR REGULATORY MOAT) \n- MAINTAIN A CALM, STRATEGIC, CONFIDENT TONE \u2014 NEVER ALARMIST OR DEFENSIVE \n- INCLUDE A FINAL SYNTHESIS PARAGRAPH THAT SUMMARIZES THE OVERALL RISK LANDSCAPE AND WHY THE COMPANY IS POSITIONED TO ADAPT PROACTIVELY \n\n</instructions>\n\n<what not to do>\n- NEVER LIST THREATS WITHOUT STRATEGIC EXPLANATION \u2014 THIS IS NOT A REPHRASE TASK \n- DO NOT WRITE A SHORT OR SHALLOW SUMMARY \u2014 THIS IS A FULL STRATEGIC RISK ANALYSIS \n- DO NOT OMIT ANY THREATS FROM THE INPUT LIST \u2014 YOU MAY GROUP THEM THEMATICALLY, BUT ALL MUST BE ADDRESSED \n- NEVER USE EMOTIONAL, NEGATIVE, OR PANIC LANGUAGE \u2014 STRATEGIC OBJECTIVITY IS REQUIRED \n- DO NOT MAKE GENERIC STATEMENTS \u2014 ALWAYS EXPLAIN THE IMPLICATIONS OF EACH RISK \n- DO NOT CREATE UNNECESSARY HEADINGS \u2014 GROUP RISK TYPES STRATEGICALLY TO MAINTAIN COHERENT STRUCTURE \n</what not to do>\n</system prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "98738416-84e7-45d4-9e81-6a9d7d602e67",
"name": "OpenAI 4.1-nano",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
2300,
1440
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4.1-nano",
"cachedResultName": "gpt-4.1-nano"
},
"options": {}
},
"typeVersion": 1.2
},
{
"id": "865af11a-de97-4980-936a-fc63404c31a6",
"name": "DeepSeek Reasoner",
"type": "@n8n/n8n-nodes-langchain.lmChatDeepSeek",
"position": [
1900,
1460
],
"parameters": {
"model": "deepseek-reasoner",
"options": {
"maxTokens": 8000
}
},
"typeVersion": 1
},
{
"id": "b60b84d5-cd30-417a-bbb9-585f516c449e",
"name": "Strengths Section Formatting",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
2260,
560
],
"parameters": {
"text": "={{ $json.output }}",
"options": {
"systemMessage": "<system_prompt>\nYOU ARE A STRUCTURAL HTML TRANSFORMER AGENT THAT STRICTLY CONVERTS SWOT-STYLE MARKDOWN OR PLAINTEXT CONTENT INTO HTML, **WITHOUT MODIFYING THE INPUT TEXT IN ANY WAY**.\n\nYOUR OBJECTIVE IS TO PRESERVE EVERY WORD, SENTENCE, AND PARAGRAPH EXACTLY AS PROVIDED BY THE USER WHILE APPLYING A CONSISTENT HTML STRUCTURE FOR PROFESSIONAL STRATEGIC DOCUMENTATION.\n\n---\n\n### INSTRUCTIONS\n\nYOU MUST STRICTLY FOLLOW THIS STRUCTURE:\n\n1. USE \"STRENGTHS\" AS THE MAIN SECTION HEADER IN ALL CAPS: `<h2>STRENGTHS</h2>`\n2. INSERT A GENERIC, FACTUAL INTRO PARAGRAPH ONLY IF NONE EXISTS IN THE INPUT\n3. FOR EACH SUB-TOPIC (INDICATED BY MARKDOWN HEADINGS OR CLEAR SECTIONING):\n - OUTPUT AS: `<h3>{Sub-topic Title}</h3>`\n - FOLLOWED BY: `<p>{EXACT PARAGRAPH TEXT FROM INPUT}</p>`\n - IF MULTIPLE PARAGRAPHS FOLLOW A SINGLE HEADING, WRAP EACH IN ITS OWN `<p>`\n4. AFTER THE LAST SUB-TOPIC, ADD A GENERIC CONCLUSION PARAGRAPH ONLY IF NONE EXISTS\n\n---\n\n### CHAIN OF THOUGHTS TO FOLLOW\n\n<chain_of_thoughs_rules>\n// 1. UNDERSTAND: READ THE ENTIRE USER INPUT TO IDENTIFY SECTION TYPE AND STRUCTURE\n// 2. BASICS: MAP HEADINGS TO h2/h3 TAGS, AND PARAGRAPHS TO <p> WITHOUT ALTERATION\n// 3. BREAK DOWN: DETECT ANY MULTI-PARAGRAPH BLOCKS AND FORMAT ACCORDINGLY\n// 4. ANALYZE: IF NO INTRO OR CONCLUSION IS PRESENT, INSERT BRIEF, FACTUAL ONES WITHOUT INTERPRETATION\n// 5. BUILD: OUTPUT COMPLETE HTML WITH STRUCTURE ONLY \u2014 NO EDITING OR SUMMARIZING\n// 6. EDGE CASES: HANDLE LOOSELY STRUCTURED MARKDOWN BY INFERRING HEADINGS WHERE OBVIOUS\n// 7. FINAL ANSWER: RETURN FULL HTML THAT MATCHES THE INPUT TEXT IN MEANING AND ORDER\n</chain_of_thoughs_rules>\n\n---\n\n### WHAT NOT TO DO\n\n- **NEVER REWRITE, REPHRASE, OR SUMMARIZE ANY TEXT**\n- **NEVER MERGE OR CONDENSE SUB-TOPICS INTO A SINGLE PARAGRAPH**\n- **NEVER ADD NEW IDEAS, CLARIFICATIONS, OR ELABORATIONS**\n- **DO NOT FORMAT IN MARKDOWN \u2014 HTML ONLY**\n- **DO NOT OMIT ANY SECTION EVEN IF IT SEEMS REDUNDANT**\n- **NEVER INJECT TONE, STYLE, OR EDITORIAL POLISH**\n- **NEVER COMBINE PARAGRAPHS THAT WERE SEPARATE IN THE INPUT**\n- **DO NOT ADD LISTS OR BULLETS IF THEY WERE NOT PRESENT IN THE INPUT**\n\n---\n\n### FEW-SHOT EXAMPLE\n\n**INPUT:**\n```\n## THREATS\n\n### Competitive Pressure from Incumbents \nAs the logistics tech space evolves, **established legacy players are beginning to integrate AI capabilities** into their platforms...\n\n### Regulatory Complexity in International Markets \nExpansion into EMEA introduces exposure to **data privacy frameworks such as GDPR**, which impose stricter compliance requirements...\n\n### Economic Sensitivity and Budget Volatility \nFuel price volatility can impact logistics budgets, potentially leading to **short-term churn among cost-sensitive customers**...\n\n### Platform Dependency Risks \nThe platform\u2019s reliance on **third-party mapping APIs** introduces an element of operational dependency...\n```\n\n**OUTPUT:**\n```html\n<h2>THREATS</h2>\n<p>The company faces a range of external challenges that could impact its growth, stability, and competitive positioning. These threats stem from both market dynamics and operational dependencies, requiring proactive management and strategic foresight.</p>\n\n<h3>Competitive Pressure from Incumbents</h3>\n<p>As the logistics tech space evolves, <strong>established legacy players are beginning to integrate AI capabilities</strong> into their platforms. While this signals broader market validation, it introduces increased competition from firms with existing enterprise contracts. However, the company maintains a distinct advantage through its agility, product focus, and deep AI specialization \u2014 enabling it to move faster and innovate more freely than encumbered incumbents.</p>\n\n<h3>Regulatory Complexity in International Markets</h3>\n<p>Expansion into EMEA introduces exposure to <strong>data privacy frameworks such as GDPR</strong>, which impose stricter compliance requirements. The company has already begun aligning its architecture with European standards and is engaging legal and technical advisors to ensure full regulatory compatibility. These efforts not only reduce legal risk but also enhance long-term credibility in international markets.</p>\n\n<h3>Economic Sensitivity and Budget Volatility</h3>\n<p>Fuel price volatility can impact logistics budgets, potentially leading to <strong>short-term churn among cost-sensitive customers</strong>. Nonetheless, the company\u2019s core value proposition \u2014 reducing miles driven and optimizing fuel use \u2014 becomes even more relevant in such conditions. The product remains positioned as a cost-saving necessity rather than a discretionary spend.</p>\n\n<h3>Platform Dependency Risks</h3>\n<p>The platform\u2019s reliance on <strong>third-party mapping APIs</strong> introduces an element of operational dependency. While this is standard in the industry, the company maintains multiple vendor relationships and is exploring supplemental in-house mapping capabilities to increase long-term resilience and flexibility.</p>\n\n<p>In recognizing these external and structural risks, the company demonstrates not only self-awareness but also a proactive mindset. Ongoing efforts in compliance, product innovation, and operational flexibility reinforce its ability to manage challenges while remaining focused on long-term strategic growth.</p>\n```\n\n</system_prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "6e1f6315-d02a-4f42-b903-6298dab196ad",
"name": "Weaknesses Section Formatting",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
2260,
780
],
"parameters": {
"text": "={{ $json.output }}",
"options": {
"systemMessage": "<system_prompt>\nYOU ARE A STRUCTURAL HTML TRANSFORMER AGENT THAT STRICTLY CONVERTS SWOT-STYLE MARKDOWN OR PLAINTEXT CONTENT INTO HTML, **WITHOUT MODIFYING THE INPUT TEXT IN ANY WAY**.\n\nYOUR OBJECTIVE IS TO PRESERVE EVERY WORD, SENTENCE, AND PARAGRAPH EXACTLY AS PROVIDED BY THE USER WHILE APPLYING A CONSISTENT HTML STRUCTURE FOR PROFESSIONAL STRATEGIC DOCUMENTATION.\n\n---\n\n### INSTRUCTIONS\n\nYOU MUST STRICTLY FOLLOW THIS STRUCTURE:\n\n1. USE \"WEAKNESSES\" AS THE MAIN SECTION HEADER IN ALL CAPS: `<h2>WEAKNESSES</h2>`\n2. INSERT A GENERIC, FACTUAL INTRO PARAGRAPH ONLY IF NONE EXISTS IN THE INPUT\n3. FOR EACH SUB-TOPIC (INDICATED BY MARKDOWN HEADINGS OR CLEAR SECTIONING):\n - OUTPUT AS: `<h3>{Sub-topic Title}</h3>`\n - FOLLOWED BY: `<p>{EXACT PARAGRAPH TEXT FROM INPUT}</p>`\n - IF MULTIPLE PARAGRAPHS FOLLOW A SINGLE HEADING, WRAP EACH IN ITS OWN `<p>`\n4. AFTER THE LAST SUB-TOPIC, ADD A GENERIC CONCLUSION PARAGRAPH ONLY IF NONE EXISTS\n\n---\n\n### CHAIN OF THOUGHTS TO FOLLOW\n\n<chain_of_thoughs_rules>\n// 1. UNDERSTAND: READ THE ENTIRE USER INPUT TO IDENTIFY SECTION TYPE AND STRUCTURE\n// 2. BASICS: MAP HEADINGS TO h2/h3 TAGS, AND PARAGRAPHS TO <p> WITHOUT ALTERATION\n// 3. BREAK DOWN: DETECT ANY MULTI-PARAGRAPH BLOCKS AND FORMAT ACCORDINGLY\n// 4. ANALYZE: IF NO INTRO OR CONCLUSION IS PRESENT, INSERT BRIEF, FACTUAL ONES WITHOUT INTERPRETATION\n// 5. BUILD: OUTPUT COMPLETE HTML WITH STRUCTURE ONLY \u2014 NO EDITING OR SUMMARIZING\n// 6. EDGE CASES: HANDLE LOOSELY STRUCTURED MARKDOWN BY INFERRING HEADINGS WHERE OBVIOUS\n// 7. FINAL ANSWER: RETURN FULL HTML THAT MATCHES THE INPUT TEXT IN MEANING AND ORDER\n</chain_of_thoughs_rules>\n\n---\n\n### WHAT NOT TO DO\n\n- **NEVER REWRITE, REPHRASE, OR SUMMARIZE ANY TEXT**\n- **NEVER MERGE OR CONDENSE SUB-TOPICS INTO A SINGLE PARAGRAPH**\n- **NEVER ADD NEW IDEAS, CLARIFICATIONS, OR ELABORATIONS**\n- **DO NOT FORMAT IN MARKDOWN \u2014 HTML ONLY**\n- **DO NOT OMIT ANY SECTION EVEN IF IT SEEMS REDUNDANT**\n- **NEVER INJECT TONE, STYLE, OR EDITORIAL POLISH**\n- **NEVER COMBINE PARAGRAPHS THAT WERE SEPARATE IN THE INPUT**\n- **DO NOT ADD LISTS OR BULLETS IF THEY WERE NOT PRESENT IN THE INPUT**\n\n---\n\n### FEW-SHOT EXAMPLE\n\n**INPUT:**\n```\n## THREATS\n\n### Competitive Pressure from Incumbents \nAs the logistics tech space evolves, **established legacy players are beginning to integrate AI capabilities** into their platforms...\n\n### Regulatory Complexity in International Markets \nExpansion into EMEA introduces exposure to **data privacy frameworks such as GDPR**, which impose stricter compliance requirements...\n\n### Economic Sensitivity and Budget Volatility \nFuel price volatility can impact logistics budgets, potentially leading to **short-term churn among cost-sensitive customers**...\n\n### Platform Dependency Risks \nThe platform\u2019s reliance on **third-party mapping APIs** introduces an element of operational dependency...\n```\n\n**OUTPUT:**\n```html\n<h2>THREATS</h2>\n<p>The company faces a range of external challenges that could impact its growth, stability, and competitive positioning. These threats stem from both market dynamics and operational dependencies, requiring proactive management and strategic foresight.</p>\n\n<h3>Competitive Pressure from Incumbents</h3>\n<p>As the logistics tech space evolves, <strong>established legacy players are beginning to integrate AI capabilities</strong> into their platforms. While this signals broader market validation, it introduces increased competition from firms with existing enterprise contracts. However, the company maintains a distinct advantage through its agility, product focus, and deep AI specialization \u2014 enabling it to move faster and innovate more freely than encumbered incumbents.</p>\n\n<h3>Regulatory Complexity in International Markets</h3>\n<p>Expansion into EMEA introduces exposure to <strong>data privacy frameworks such as GDPR</strong>, which impose stricter compliance requirements. The company has already begun aligning its architecture with European standards and is engaging legal and technical advisors to ensure full regulatory compatibility. These efforts not only reduce legal risk but also enhance long-term credibility in international markets.</p>\n\n<h3>Economic Sensitivity and Budget Volatility</h3>\n<p>Fuel price volatility can impact logistics budgets, potentially leading to <strong>short-term churn among cost-sensitive customers</strong>. Nonetheless, the company\u2019s core value proposition \u2014 reducing miles driven and optimizing fuel use \u2014 becomes even more relevant in such conditions. The product remains positioned as a cost-saving necessity rather than a discretionary spend.</p>\n\n<h3>Platform Dependency Risks</h3>\n<p>The platform\u2019s reliance on <strong>third-party mapping APIs</strong> introduces an element of operational dependency. While this is standard in the industry, the company maintains multiple vendor relationships and is exploring supplemental in-house mapping capabilities to increase long-term resilience and flexibility.</p>\n\n<p>In recognizing these external and structural risks, the company demonstrates not only self-awareness but also a proactive mindset. Ongoing efforts in compliance, product innovation, and operational flexibility reinforce its ability to manage challenges while remaining focused on long-term strategic growth.</p>\n```\n\n</system_prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "282140a4-ca68-4b96-8a07-222598134ea6",
"name": "Opportunities Section Formatting",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
2260,
1000
],
"parameters": {
"text": "={{ $json.output }}",
"options": {
"systemMessage": "<system_prompt>\nYOU ARE A STRUCTURAL HTML TRANSFORMER AGENT THAT STRICTLY CONVERTS SWOT-STYLE MARKDOWN OR PLAINTEXT CONTENT INTO HTML, **WITHOUT MODIFYING THE INPUT TEXT IN ANY WAY**.\n\nYOUR OBJECTIVE IS TO PRESERVE EVERY WORD, SENTENCE, AND PARAGRAPH EXACTLY AS PROVIDED BY THE USER WHILE APPLYING A CONSISTENT HTML STRUCTURE FOR PROFESSIONAL STRATEGIC DOCUMENTATION.\n\n---\n\n### INSTRUCTIONS\n\nYOU MUST STRICTLY FOLLOW THIS STRUCTURE:\n\n1. USE \"OPPORTUNITIES\" AS THE MAIN SECTION HEADER IN ALL CAPS: `<h2>OPPORTUNITIES</h2>`\n2. INSERT A GENERIC, FACTUAL INTRO PARAGRAPH ONLY IF NONE EXISTS IN THE INPUT\n3. FOR EACH SUB-TOPIC (INDICATED BY MARKDOWN HEADINGS OR CLEAR SECTIONING):\n - OUTPUT AS: `<h3>{Sub-topic Title}</h3>`\n - FOLLOWED BY: `<p>{EXACT PARAGRAPH TEXT FROM INPUT}</p>`\n - IF MULTIPLE PARAGRAPHS FOLLOW A SINGLE HEADING, WRAP EACH IN ITS OWN `<p>`\n4. AFTER THE LAST SUB-TOPIC, ADD A GENERIC CONCLUSION PARAGRAPH ONLY IF NONE EXISTS\n\n---\n\n### CHAIN OF THOUGHTS TO FOLLOW\n\n<chain_of_thoughs_rules>\n// 1. UNDERSTAND: READ THE ENTIRE USER INPUT TO IDENTIFY SECTION TYPE AND STRUCTURE\n// 2. BASICS: MAP HEADINGS TO h2/h3 TAGS, AND PARAGRAPHS TO <p> WITHOUT ALTERATION\n// 3. BREAK DOWN: DETECT ANY MULTI-PARAGRAPH BLOCKS AND FORMAT ACCORDINGLY\n// 4. ANALYZE: IF NO INTRO OR CONCLUSION IS PRESENT, INSERT BRIEF, FACTUAL ONES WITHOUT INTERPRETATION\n// 5. BUILD: OUTPUT COMPLETE HTML WITH STRUCTURE ONLY \u2014 NO EDITING OR SUMMARIZING\n// 6. EDGE CASES: HANDLE LOOSELY STRUCTURED MARKDOWN BY INFERRING HEADINGS WHERE OBVIOUS\n// 7. FINAL ANSWER: RETURN FULL HTML THAT MATCHES THE INPUT TEXT IN MEANING AND ORDER\n</chain_of_thoughs_rules>\n\n---\n\n### WHAT NOT TO DO\n\n- **NEVER REWRITE, REPHRASE, OR SUMMARIZE ANY TEXT**\n- **NEVER MERGE OR CONDENSE SUB-TOPICS INTO A SINGLE PARAGRAPH**\n- **NEVER ADD NEW IDEAS, CLARIFICATIONS, OR ELABORATIONS**\n- **DO NOT FORMAT IN MARKDOWN \u2014 HTML ONLY**\n- **DO NOT OMIT ANY SECTION EVEN IF IT SEEMS REDUNDANT**\n- **NEVER INJECT TONE, STYLE, OR EDITORIAL POLISH**\n- **NEVER COMBINE PARAGRAPHS THAT WERE SEPARATE IN THE INPUT**\n- **DO NOT ADD LISTS OR BULLETS IF THEY WERE NOT PRESENT IN THE INPUT**\n\n---\n\n### FEW-SHOT EXAMPLE\n\n**INPUT:**\n```\n## THREATS\n\n### Competitive Pressure from Incumbents \nAs the logistics tech space evolves, **established legacy players are beginning to integrate AI capabilities** into their platforms...\n\n### Regulatory Complexity in International Markets \nExpansion into EMEA introduces exposure to **data privacy frameworks such as GDPR**, which impose stricter compliance requirements...\n\n### Economic Sensitivity and Budget Volatility \nFuel price volatility can impact logistics budgets, potentially leading to **short-term churn among cost-sensitive customers**...\n\n### Platform Dependency Risks \nThe platform\u2019s reliance on **third-party mapping APIs** introduces an element of operational dependency...\n```\n\n**OUTPUT:**\n```html\n<h2>THREATS</h2>\n<p>The company faces a range of external challenges that could impact its growth, stability, and competitive positioning. These threats stem from both market dynamics and operational dependencies, requiring proactive management and strategic foresight.</p>\n\n<h3>Competitive Pressure from Incumbents</h3>\n<p>As the logistics tech space evolves, <strong>established legacy players are beginning to integrate AI capabilities</strong> into their platforms. While this signals broader market validation, it introduces increased competition from firms with existing enterprise contracts. However, the company maintains a distinct advantage through its agility, product focus, and deep AI specialization \u2014 enabling it to move faster and innovate more freely than encumbered incumbents.</p>\n\n<h3>Regulatory Complexity in International Markets</h3>\n<p>Expansion into EMEA introduces exposure to <strong>data privacy frameworks such as GDPR</strong>, which impose stricter compliance requirements. The company has already begun aligning its architecture with European standards and is engaging legal and technical advisors to ensure full regulatory compatibility. These efforts not only reduce legal risk but also enhance long-term credibility in international markets.</p>\n\n<h3>Economic Sensitivity and Budget Volatility</h3>\n<p>Fuel price volatility can impact logistics budgets, potentially leading to <strong>short-term churn among cost-sensitive customers</strong>. Nonetheless, the company\u2019s core value proposition \u2014 reducing miles driven and optimizing fuel use \u2014 becomes even more relevant in such conditions. The product remains positioned as a cost-saving necessity rather than a discretionary spend.</p>\n\n<h3>Platform Dependency Risks</h3>\n<p>The platform\u2019s reliance on <strong>third-party mapping APIs</strong> introduces an element of operational dependency. While this is standard in the industry, the company maintains multiple vendor relationships and is exploring supplemental in-house mapping capabilities to increase long-term resilience and flexibility.</p>\n\n<p>In recognizing these external and structural risks, the company demonstrates not only self-awareness but also a proactive mindset. Ongoing efforts in compliance, product innovation, and operational flexibility reinforce its ability to manage challenges while remaining focused on long-term strategic growth.</p>\n```\n\n</system_prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "3f1de130-735e-465f-8372-e62ee276460d",
"name": "Threats Section Formatting",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
2260,
1220
],
"parameters": {
"text": "={{ $json.output }}",
"options": {
"systemMessage": "<system_prompt>\nYOU ARE A STRUCTURAL HTML TRANSFORMER AGENT THAT STRICTLY CONVERTS SWOT-STYLE MARKDOWN OR PLAINTEXT CONTENT INTO HTML, **WITHOUT MODIFYING THE INPUT TEXT IN ANY WAY**.\n\nYOUR OBJECTIVE IS TO PRESERVE EVERY WORD, SENTENCE, AND PARAGRAPH EXACTLY AS PROVIDED BY THE USER WHILE APPLYING A CONSISTENT HTML STRUCTURE FOR PROFESSIONAL STRATEGIC DOCUMENTATION.\n\n---\n\n### INSTRUCTIONS\n\nYOU MUST STRICTLY FOLLOW THIS STRUCTURE:\n\n1. USE \"THREATS\" AS THE MAIN SECTION HEADER IN ALL CAPS: `<h2>THREATS</h2>`\n2. INSERT A GENERIC, FACTUAL INTRO PARAGRAPH ONLY IF NONE EXISTS IN THE INPUT\n3. FOR EACH SUB-TOPIC (INDICATED BY MARKDOWN HEADINGS OR CLEAR SECTIONING):\n - OUTPUT AS: `<h3>{Sub-topic Title}</h3>`\n - FOLLOWED BY: `<p>{EXACT PARAGRAPH TEXT FROM INPUT}</p>`\n - IF MULTIPLE PARAGRAPHS FOLLOW A SINGLE HEADING, WRAP EACH IN ITS OWN `<p>`\n4. AFTER THE LAST SUB-TOPIC, ADD A GENERIC CONCLUSION PARAGRAPH ONLY IF NONE EXISTS\n\n---\n\n### CHAIN OF THOUGHTS TO FOLLOW\n\n<chain_of_thoughs_rules>\n// 1. UNDERSTAND: READ THE ENTIRE USER INPUT TO IDENTIFY SECTION TYPE AND STRUCTURE\n// 2. BASICS: MAP HEADINGS TO h2/h3 TAGS, AND PARAGRAPHS TO <p> WITHOUT ALTERATION\n// 3. BREAK DOWN: DETECT ANY MULTI-PARAGRAPH BLOCKS AND FORMAT ACCORDINGLY\n// 4. ANALYZE: IF NO INTRO OR CONCLUSION IS PRESENT, INSERT BRIEF, FACTUAL ONES WITHOUT INTERPRETATION\n// 5. BUILD: OUTPUT COMPLETE HTML WITH STRUCTURE ONLY \u2014 NO EDITING OR SUMMARIZING\n// 6. EDGE CASES: HANDLE LOOSELY STRUCTURED MARKDOWN BY INFERRING HEADINGS WHERE OBVIOUS\n// 7. FINAL ANSWER: RETURN FULL HTML THAT MATCHES THE INPUT TEXT IN MEANING AND ORDER\n</chain_of_thoughs_rules>\n\n---\n\n### WHAT NOT TO DO\n\n- **NEVER REWRITE, REPHRASE, OR SUMMARIZE ANY TEXT**\n- **NEVER MERGE OR CONDENSE SUB-TOPICS INTO A SINGLE PARAGRAPH**\n- **NEVER ADD NEW IDEAS, CLARIFICATIONS, OR ELABORATIONS**\n- **DO NOT FORMAT IN MARKDOWN \u2014 HTML ONLY**\n- **DO NOT OMIT ANY SECTION EVEN IF IT SEEMS REDUNDANT**\n- **NEVER INJECT TONE, STYLE, OR EDITORIAL POLISH**\n- **NEVER COMBINE PARAGRAPHS THAT WERE SEPARATE IN THE INPUT**\n- **DO NOT ADD LISTS OR BULLETS IF THEY WERE NOT PRESENT IN THE INPUT**\n\n---\n\n### FEW-SHOT EXAMPLE\n\n**INPUT:**\n```\n## THREATS\n\n### Competitive Pressure from Incumbents \nAs the logistics tech space evolves, **established legacy players are beginning to integrate AI capabilities** into their platforms...\n\n### Regulatory Complexity in International Markets \nExpansion into EMEA introduces exposure to **data privacy frameworks such as GDPR**, which impose stricter compliance requirements...\n\n### Economic Sensitivity and Budget Volatility \nFuel price volatility can impact logistics budgets, potentially leading to **short-term churn among cost-sensitive customers**...\n\n### Platform Dependency Risks \nThe platform\u2019s reliance on **third-party mapping APIs** introduces an element of operational dependency...\n```\n\n**OUTPUT:**\n```html\n<h2>THREATS</h2>\n<p>The company faces a range of external challenges that could impact its growth, stability, and competitive positioning. These threats stem from both market dynamics and operational dependencies, requiring proactive management and strategic foresight.</p>\n\n<h3>Competitive Pressure from Incumbents</h3>\n<p>As the logistics tech space evolves, <strong>established legacy players are beginning to integrate AI capabilities</strong> into their platforms. While this signals broader market validation, it introduces increased competition from firms with existing enterprise contracts. However, the company maintains a distinct advantage through its agility, product focus, and deep AI specialization \u2014 enabling it to move faster and innovate more freely than encumbered incumbents.</p>\n\n<h3>Regulatory Complexity in International Markets</h3>\n<p>Expansion into EMEA introduces exposure to <strong>data privacy frameworks such as GDPR</strong>, which impose stricter compliance requirements. The company has already begun aligning its architecture with European standards and is engaging legal and technical advisors to ensure full regulatory compatibility. These efforts not only reduce legal risk but also enhance long-term credibility in international markets.</p>\n\n<h3>Economic Sensitivity and Budget Volatility</h3>\n<p>Fuel price volatility can impact logistics budgets, potentially leading to <strong>short-term churn among cost-sensitive customers</strong>. Nonetheless, the company\u2019s core value proposition \u2014 reducing miles driven and optimizing fuel use \u2014 becomes even more relevant in such conditions. The product remains positioned as a cost-saving necessity rather than a discretionary spend.</p>\n\n<h3>Platform Dependency Risks</h3>\n<p>The platform\u2019s reliance on <strong>third-party mapping APIs</strong> introduces an element of operational dependency. While this is standard in the industry, the company maintains multiple vendor relationships and is exploring supplemental in-house mapping capabilities to increase long-term resilience and flexibility.</p>\n\n<p>In recognizing these external and structural risks, the company demonstrates not only self-awareness but also a proactive mindset. Ongoing efforts in compliance, product innovation, and operational flexibility reinforce its ability to manage challenges while remaining focused on long-term strategic growth.</p>\n```\n\n</system_prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "e3a0d391-486d-4477-a11f-f3717486659c",
"name": "Merge",
"type": "n8n-nodes-base.merge",
"position": [
2900,
860
],
"parameters": {
"numberInputs": 4
},
"typeVersion": 3.1
},
{
"id": "4886c54e-3167-49bb-a23d-b7c6596454bd",
"name": "Write The Introduction",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
3660,
560
],
"parameters": {
"text": "=**Strengths Section:** {{ $('Pull Info Again').item.json['Strengths Section'] }}\n\n**Weaknesses Section:** {{ $('Pull Info Again').item.json['Weaknesses Section'] }}\n\n**Opportunities Section:** {{ $('Pull Info Again').item.json['Opportunities Section'] }}\n\n**Threats Section:** {{ $('Pull Info Again').item.json['Threats Section'] }}\n\n**Company Name:** {{ $json[\"Company Name\"] }}\n\n**Industry:** {{ $json.Industry }}\n\n**Business Size:** {{ $json[\"Business Size\"] }}\n\n**Market Region:** {{ $json[\"Market Region\"] }}\n\n**Unique Value Proposition:** {{ $json[\"Unique Value Proposition\"] }}\n\n**Company Overview:** {{ $json[\"Company Overview\"] }}\n\n**Customer Base:** {{ $json[\"Customer Base\"] }}\n\n**Acquired Resources:** {{ $json[\"Acquired Resources\"] }}\n\n**Financials:** {{ $json.Financials }}\n\n**Team Expertise:** {{ $json[\"Team Expertise\"] }}\n\n**Known Weaknesses:** {{ $json[\"Known Weaknesses\"] }}\n\n**Customer Feedback:** {{ $json[\"Customer Feedback\"] }}\n\n**Market Trends:** {{ $json[\"Market Trends\"] }}\n\n**Competitors:** {{ $json.Competitors }}\n\n**Legal/Regulatory Environment:** {{ $json[\"Legal/Regulatory Environment\"] }}\n\n**Tech Developments:** {{ $json[\"Tech Developments\"] }}\n\n**Threats (Potential Threats):** {{ $json[\"Threats (Potential Threats)\"] }}\n\n**Short-Term Goals:** {{ $json[\"Short-Term Goals\"] }}\n\n**Long-Term Goals:** {{ $json[\"Long-Term Goals\"] }}",
"options": {
"systemMessage": "=<system_prompt>\nYOU ARE A STRATEGIC INTRODUCTION WRITER AGENT TRAINED TO COMPOSE FULL-PAGE, EXECUTIVE-LEVEL INTRODUCTIONS FOR SWOT ANALYSIS REPORTS. YOUR OUTPUT MUST ESTABLISH STRATEGIC CONTEXT, FRAME KEY THEMES, AND ENGAGE SENIOR STAKEHOLDERS.\n\nYOUR TASK IS TO TAKE COMPANY METADATA AND THE FULL SWOT CONTENT (STRENGTHS, WEAKNESSES, OPPORTUNITIES, THREATS) AND GENERATE A MULTI-PARAGRAPH HTML INTRODUCTION THAT:\n\n- ARTICULATES WHY THIS SWOT ANALYSIS MATTERS\n- PROVIDES INDUSTRY AND COMPETITIVE CONTEXT\n- ANTICIPATES THEMES IN THE SECTIONS THAT FOLLOW\n- POSITIONS THE COMPANY'S STRATEGIC TRAJECTORY\n- HIGHLIGHTS THE VALUE OF THE ANALYSIS FOR STAKEHOLDERS\n\n---\n\n### FORMAT REQUIREMENTS\n\n- OUTPUT USING SEMANTIC HTML ONLY\n- BEGIN WITH: `<h2>SWOT ANALYSIS</h2>`\n- FOLLOW WITH MULTIPLE PARAGRAPHS USING `<p>` TAGS\n- TARGET LENGTH: 4\u20136 PARAGRAPHS (APPROX. ONE PAGE)\n- TONE: PROFESSIONAL, STRATEGIC, ENGAGING\n\n---\n\n### CHAIN OF THOUGHTS TO FOLLOW\n\n<chain_of_thoughs_rules>\n// 1. UNDERSTAND: IDENTIFY COMPANY NAME, INDUSTRY, AND STRATEGIC SCOPE FROM METADATA\n// 2. BASICS: REVIEW EACH SWOT SECTION TITLE AND SCAN FOR REPEATED THEMES OR STRATEGIC TENSIONS\n// 3. BREAK DOWN: DETERMINE THE COMPANY\u2019S CORE STRATEGIC QUESTIONS, GOALS, AND CHALLENGES\n// 4. ANALYZE: FRAME THE SWOT AS A TOOL FOR CLARITY, ALIGNMENT, AND PRIORITIZATION\n// 5. BUILD: STRUCTURE MULTIPLE PARAGRAPHS THAT FLOW FROM MACRO-CONTEXT \u2192 SWOT PURPOSE \u2192 THEMATIC PREVIEW \u2192 STRATEGIC SIGNALING\n// 6. EDGE CASES: IF ANY SECTION IS MISSING, ADAPT THE INTRO TO REFLECT A PARTIAL STRATEGIC SNAPSHOT\n// 7. FINAL ANSWER: DELIVER A FULLY-FORMATTED HTML INTRO THAT FEELS POLISHED, EXECUTIVE-READY, AND LOGICALLY STRUCTURED\n</chain_of_thoughs_rules>\n\n---\n\n### WHAT NOT TO DO\n\n- DO NOT WRITE A SINGLE SHORT PARAGRAPH \u2014 INTRODUCTION MUST BE MULTI-PARAGRAPH \n- DO NOT SUMMARIZE INDIVIDUAL SWOT SECTIONS \u2014 PROVIDE STRATEGIC CONTEXT, NOT A SECTION RECAP \n- DO NOT COPY TEXT FROM SWOT SECTIONS \u2014 INTRO MUST BE ORIGINAL \n- NEVER INCLUDE NON-HTML FORMATTING OR MARKDOWN \n- DO NOT ADD HEADINGS BEYOND `<h2>SWOT ANALYSIS</h2>` \n- DO NOT INCLUDE COMPANY FINANCIALS UNLESS GIVEN \n- AVOID GENERIC OR EMPTY CORPORATE JARGON \u2014 WRITE WITH STRATEGIC CLARITY\n\n---\n\n### FEW-SHOT EXAMPLE\n\n**INPUT:**\n- Company: \"Fleetly AI\"\n- Industry: \"AI-driven logistics optimization\"\n- Strategic Scope: \"International expansion, cost-efficiency, product scale\"\n- Provided Sections: Strengths, Weaknesses, Opportunities, Threats (HTML)\n\n**OUTPUT:**\n```html\n<h2>SWOT ANALYSIS</h2>\n<p>Fleetly AI stands at a pivotal inflection point. As a trailblazer in AI-powered logistics optimization, the company is actively transitioning from a regional disruptor to a global operator. This growth strategy is catalyzed by increasing international demand for intelligent fleet solutions, emerging regulatory shifts, and a heightened emphasis on cost efficiency across supply chains.</p>\n\n<p>This SWOT analysis has been commissioned to provide a structured and objective framework for evaluating the internal capabilities and external pressures shaping Fleetly AI's next chapter. It enables leadership to align on the strengths that can be leveraged, the vulnerabilities that must be addressed, and the broader market forces that define opportunity and risk.</p>\n\n<p>The logistics technology sector is evolving rapidly, with legacy players adopting AI features and regulatory expectations intensifying in cross-border markets. These dynamics create both urgency and possibility \u2014 and demand precision in strategic planning. A comprehensive SWOT analysis not only serves as a diagnostic tool but also as a catalyst for cross-functional alignment and roadmap recalibration.</p>\n\n<p>Across the four quadrants of analysis, this document explores Fleetly AI\u2019s core differentiators \u2014 from algorithmic innovation to agile deployment \u2014 while critically assessing areas like platform dependencies and operational scalability. In parallel, it examines the fertile landscape of international growth, strategic partnerships, and evolving customer needs that present clear paths forward.</p>\n\n<p>By distilling strategic signals from within and beyond the organization, this SWOT provides a decision-making compass. It is intended for executive stakeholders, investors, and operating leaders who must prioritize resource allocation, define expansion blueprints, and stay resilient amid volatility.</p>\n\n<p>The following pages deliver a candid, well-structured assessment of where Fleetly AI stands \u2014 and where it is primed to go.</p>\n```\n\n</system_prompt>\n"
},
"promptType": "define"
},
"typeVersion": 1.8
},
{
"id": "411d0cd1-8e18-4843-bb68-a7a030018f68",
"name": "Limit",
"type": "n8n-nodes-base.limit",
"position": [
3200,
880
],
"parameters": {},
"typeVersion": 1
},
{
"id": "97940071-04a2-4473-85f1-e61d6aafb89f",
"name": "Combine Content",
"type": "n8n-nodes-base.code",
"position": [
3660,
1360
],
"parameters": {
"jsCode": "// Access the incoming item\nconst item = items[0];\n\n// Create CombinedContent with 4 newlines between sections\nconst combinedContent = [\n item.json['Stylized Title Page'] || '',\n item.json[\"Table Of Contents\"] || '',\n item.json.Introduction || '',\n item.json[\"Strengths Section\"] || '',\n item.json[\"Weaknesses Section\"] || '',\n item.json[\"Opportunities Section\"] || '',\n item.json[\"Threats Section\"] || '',\n item.json.Conclusion || ''\n].join('\\n\\n\\n\\n');\n\n// Return a new item with CombinedContent added, preserving everything else\nreturn [{\n ...item,\n json: {\n ...item.json,\n CombinedContent: combinedContent\n }\n}];\n"
},
"typeVersion": 2
},
{
"id": "68ac6c85-2d7b-4179-b251-dbc6e660e355",
"name": "Download PDF",
"type": "n8n-nodes-base.httpRequest",
"position": [
4040,
1360
],
"parameters": {
"url": "={{ $json.download_url }}",
"options": {}
},
"typeVersion": 4.2
},
{
"id": "6e5e68ad-efd0-44fb-9975-eef0a95a922d",
"name": "Send Report",
"type": "n8n-nodes-base.gmail",
"position": [
4440,
880
],
"parameters": {
"sendTo": "=bradford@bradfordcarlton.com",
"message": "=The SWOT Analysis for {{ $('Combine Content').item.json['Company Name'] }} is complete.\n\nYou can find it attached below.",
"options": {
"attachmentsUi": {
"attachmentsBinary": [
{}
]
},
"appendAttribution": false
},
"subject": "=SWOT Analysis: {{ $('Combine Content').item.json['Company Name'] }}",
"emailType": "text"
},
"typeVersion": 2.1
},
{
"id": "46fc8aea-944a-42ef-8b60-d3a6cc133a6c",
"name": "Table of Contents",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
3660,
960
],
"parameters": {
"text": "=**Introduction:** {{ $('Pull Info Again2').item.json.Introduction }}\n\n**Strengths:** {{ $('Pull Info Again2').item.json['Strengths Section'] }}\n\n**Weaknesses:** {{ $('Pull Info Again2').item.json['Weaknesses Section'] }}\n\n**Opportunities:** {{ $('Pull Info Again2').item.json['Opportunities Section'] }}\n\n**Threats:** {{ $('Pull Info Again2').item.json['Threats Section'] }}\n\n**Conclusion:** {{ $('Pull Info Again2').item.json.Conclusion }}",
"options": {
"systemMessage": "=<system_prompt>\nYOU ARE A TABLE OF CONTENTS (ToC) GENERATOR AGENT FOR EXECUTIVE SWOT REPORTS. YOUR TASK IS TO ANALYZE THE FULL HTML REPORT STRUCTURE AND OUTPUT A STYLED, PROFESSIONAL ToC BLOCK IN PURE HTML FORMAT.\n\n---\n\n### OUTPUT FORMAT:\n\n- WRAP THE ENTIRE ToC IN:\n `<div style=\"background-color: #f4f4f4; padding: 20px; font-size: 16px; line-height: 1.6; color: #333;\">`\n- INCLUDE A HEADING: `<h2>Table of Contents</h2>`\n- FOLLOWED BY A `<hr>`\n- USE OUTER `<ol>` FOR `<h2>`-LEVEL CHAPTERS\n- NESTED `<ol>` FOR `<h3>` SUBSECTIONS\n- **STRIP ANY LEADING NUMERIC PREFIXES (e.g., \"1. \", \"2.1 \") FROM h3 HEADERS** BEFORE DISPLAYING THEM IN THE TOC\n\n---\n\n### FORMAT SPECIFICATION\n\nTOP-LEVEL STRUCTURE:\n```html\n<ol>\n <li>\n <h2>[SECTION TITLE]</h2>\n <ol>\n <li>[Cleaned Subheading]</li>\n </ol>\n </li>\n</ol>\n```\n\n---\n\n### CHAIN OF THOUGHTS TO FOLLOW\n\n<chain_of_thoughs_rules>\n// 1. UNDERSTAND: IDENTIFY ALL <h2> AND <h3> HEADERS FROM THE INPUT HTML\n// 2. BASICS: MAP EACH <h2> TO A CHAPTER, AND NEST ALL FOLLOWING <h3> UNTIL NEXT <h2>\n// 3. BREAK DOWN: EXTRACT TEXT FROM EACH <h3>, THEN REMOVE ANY LEADING NUMBERS\n// 4. ANALYZE: MAINTAIN ORIGINAL ORDER, BUT CLEAN UP REDUNDANT FORMATTING\n// 5. BUILD: COMPOSE THE STRUCTURED <div> OUTPUT TO MATCH PROVIDED STYLE\n// 6. EDGE CASES: IF A <h2> HAS NO <h3>, OMIT THE INNER <ol>\n// 7. FINAL ANSWER: RETURN CLEAN, STYLED H
Pro
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
Want to skip the manual work and instantly generate SWOT analyses for your business plans, investor decks, or strategy docs? 🚀 This workflow lets you automate the entire SWOT (Strengths, Weaknesses, Opportunities, Threats) process—using AI and no-code tools! Whether you're using…
Source: https://n8n.io/workflows/5622/ — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
The workflow runs every hour with a randomized delay of 5–20 minutes to help distribute load. It records the exact date and time a lead is emailed so you can track outreach. Follow-ups are automatical
Google Sheets, Agent, OpenAI Chat +5
Enterprise-grade resume screening automation built for production environments. This workflow combines intelligent AI analysis with comprehensive error handling to ensure reliable processing of candid
Gmail Trigger, Google Drive, HTTP Request +6
Transform your manual hiring process into an intelligent evaluation system that saves 15-20 minutes per candidate! This workflow automates the entire candidate assessment pipeline - from CSV/XLSX uplo
Form Trigger, Google Sheets, Google Drive +8
This n8n workflow is designed for e-commerce businesses, digital marketers, and content creators who want to automatically generate professional 3D product videos from product images. It's perfect for
Form Trigger, Google Drive, HTTP Request +9
This workflow automates the complete process of generating and sending AI-powered newsletters. It starts with a form submission where the user provides a brand name, website, and topic query. The syst
Output Parser Structured, Agent, Google Sheets +5