我的工作流
中级
这是一个Content Creation, Multimodal AI领域的自动化工作流,包含 13 个节点。主要使用 Merge, LinkedIn, Agent, ScheduleTrigger, OpenAi 等节点。 使用 Google Gemini 内容和 DALL-E 图像自动化 LinkedIn 帖子
前置要求
- •LinkedIn API 凭证
- •OpenAI API Key
- •Google Gemini API Key
工作流预览
可视化展示节点连接关系,支持缩放和平移
导出工作流
复制以下 JSON 配置到 n8n 导入,即可使用此工作流
{
"name": "我的工作流",
"nodes": [
{
"id": "48b99b67-04f6-4a6f-8dad-195d85aa4ef0",
"name": "计划触发器1",
"type": "n8n-nodes-base.scheduleTrigger",
"position": [
-1520,
100
],
"parameters": {
"rule": {
"interval": [
{
"field": "hours",
"hoursInterval": 6
}
]
}
},
"typeVersion": 1.2
},
{
"id": "73b48372-4f64-4547-bc7d-65d23094305a",
"name": "Google Gemini聊天模型1",
"type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
"position": [
-1260,
300
],
"parameters": {
"options": {
"temperature": 0.8
},
"modelName": "models/gemini-2.0-flash"
},
"credentials": {
"googlePalmApi": {
"id": "Your_Gemini_API",
"name": "Gemini API"
}
},
"typeVersion": 1
},
{
"id": "ce7265ec-e86e-48ef-9166-440a8caaad02",
"name": "结构化输出解析器6",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
-1040,
300
],
"parameters": {
"jsonSchemaExample": "[{\n \"title\": \"AI as Your First Content Hire: Why Founders Shouldn't Wait to Outsource Creation\",\n \"rationale\": \"Most solopreneurs delay content scaling because they think hiring a ghostwriter is the next step — but AI can handle 80% with proper systems. This shifts content from a creative bottleneck to a scalable growth lever.\",\n \"hook\": \"Ghostwriters are outdated. Train GPT once, and it ships LinkedIn gold in your voice daily. Welcome to hands-free thought leadership.\"\n }]"
},
"typeVersion": 1.2
},
{
"id": "88f55c81-7535-43fc-862e-9f77069d2780",
"name": "Google Gemini 聊天模型2",
"type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
"position": [
-820,
320
],
"parameters": {
"options": {
"temperature": 0.8
},
"modelName": "models/gemini-2.0-flash"
},
"credentials": {
"googlePalmApi": {
"id": "Your_Gemini_API",
"name": "Gemini API"
}
},
"typeVersion": 1
},
{
"id": "479b4c3e-3944-41c1-8f84-26fe094fe767",
"name": "结构化输出解析器7",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
-620,
320
],
"parameters": {
"jsonSchemaExample": "{\n \"post title\": \"Exciting New Feature Launch 🚀\",\n \"post content\": \"After months of collaboration, testing, and fine-tuning, we're thrilled to introduce our latest product feature: Smart Insights. It helps users uncover meaningful patterns in their data with just a few clicks. This wouldn't have been possible without our incredible team and supportive community. We're excited for what's next — and we'd love your feedback!\",\n \"image description\": \"A laptop screen showcasing the new Smart Insights dashboard with colorful charts and graphs, surrounded by a team clapping in the background.\"\n}"
},
"typeVersion": 1.2
},
{
"id": "0dcd6b17-e5b6-498a-bdd3-b7f72c9d6458",
"name": "内容主题生成器",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
-1220,
100
],
"parameters": {
"text": "\"You are a seasoned AI marketing strategist with deep knowledge in DevOps, MLOps, Cloud Engineering, ML Engineering, and AI Engineering for cloud-based systems. Your task is to generate high-value content topics that align with technical leadership expertise and resonate deeply with CTOs, Heads of Engineering, VPs of Engineering, CXOs, and Founders.\nCRITICAL: Generate completely fresh, unique topics each time. Avoid repeating similar themes, angles, or approaches from previous generations.\nThese topics will later be expanded into posts by another agent and must highlight pain points or key trends in engineering leadership.\n🔍 What to Focus On: Generate content topics (not full content) based on these strategic themes, but rotate focus areas and explore different angles each time:\nMLOps & ML deployment challenges and solutions\nCloud engineering & cloud cost optimization strategies\nDevOps & CI/CD pipeline optimization\nCloud-native AI/ML product delivery and scaling\nAI/ML application scalability and governance\nEngineering team leadership and technical decision-making\n🎯 Variety Requirements:\nMix different content types: lessons learned, contrarian takes, industry observations, practical tips, future predictions, case studies, team challenges\nRotate between technical depth levels (high-level strategy vs. hands-on implementation)\nAlternate between problem-focused and solution-focused angles\nInclude seasonal/current trends and emerging technologies\nVary emotional tones: urgent, curious, controversial, helpful, forward-thinking\nHas to have a click-bait to attract target audience, and title has to have question. \n✅ Your Output Per Topic: For each idea, generate the following:\nTopic Title or Core Idea (1 line) - Must be intuitive and preferably framed as a question around the target audience's pain point\nShort Rationale (1–2 sentences on why this topic matters to engineering leaders)\nSuggested Angle or Hook (1 LinkedIn-style framing or contrarian take that provokes thought)\n💡 Style Guide: Keep ideas insightful, actionable, and technically grounded\nFavor engineering leadership perspective: practical, solution-oriented, and slightly contrarian when it adds value\nFocus on real-world engineering challenges, team scaling, and technical strategy\nAvoid hype or generic buzzwords — focus on clarity, practical insights, and utility for engineering leaders\nGenerate topics that feel completely different from typical LinkedIn engineering content\"\n",
"options": {},
"promptType": "define",
"hasOutputParser": true
},
"typeVersion": 1.8
},
{
"id": "ad704a2a-1c73-4b45-af2c-b0287a26d2e6",
"name": "内容创建器",
"type": "@n8n/n8n-nodes-langchain.chainLlm",
"position": [
-860,
100
],
"parameters": {
"text": "=\"“You are a seasoned Copy Writer with deep knowledge in DevOps, MLOps, Cloud Engineering, ML Engineering, and AI Engineering for cloud-based systems. Your task is to write creative, and curiosity-driven LinkedIn post Based on the topic: [INSERT SELECTED TOPIC] targeted at engineering leaders (CTOs, Heads of Engineering, VPs, Founders, CXOs) who are actively building or scaling AI/ML solutions in the cloud.\nYour persona is that of a knowledgeable, practical, and forward-thinking technical leader who understands the real-world engineering challenges faced by CTOs, Heads of Engineering, VPs of Engineering, CXOs, and Founders. Your goal is to provide immense technical value and position the author as a trusted expert in the engineering leadership space.\n\n\nThese posts must highlight pain points or key trends in:\nMLOps & ML deployment\n\n\nCloud engineering & cloud cost optimization\n\n\nDevOps & CI/CD challenges\n\n\nCloud-native AI/ML product delivery\n\n\nAI/ML application scalability and governance\nThe posts should be designed to provoke thought, start conversations, and position the author as a trusted expert. Each post should be clear, and impactful.”\n\n\n\nCRITICAL: Create completely unique content each time. Vary your writing style, structure, examples, and approach to ensure no two posts feel similar or repetitive.\nYour Task: Based on the provided Topic, Rationale, and Hook, write a complete LinkedIn post.\nInput:\nTitle/Idea: {{ $json.output[0].title }}\nRationale: {{ $json.output[0].rationale }}\nHook: {{ $json.output[0].hook }}\nFORBIDDEN PHRASES - NEVER USE:\n\"Let's be honest\"\n\"Delve into\"\n\"At its core\"\n\"It's important to note\"\n\"In today's world\"\n\"A testament to\"\n\"Navigating the landscape\"\n\"Paradigm shift\"\n\"Aims to explore\"\n\"It's not this, it's that\"\n\"Conquer\"\nFreshness & Variety Requirements:\nRotate opening styles: questions, bold statements, personal anecdotes, industry observations, contrarian takes, statistics, scenarios\nMix content structures: story-driven, list-based, problem-solution, comparison, prediction, reflection\nVary examples: different companies, technologies, team sizes, industries, time periods\nAlternate emotional tones: urgent, curious, empathetic, confident, thought-provoking, practical\nUse diverse vocabulary and sentence structures to avoid repetitive phrasing\nInclude different types of insights: technical, strategic, people-focused, process-oriented, future-focused\nStrict Formatting & Style Rules:\nStart Strong: Begin the post immediately with the powerful hook that addresses a specific engineering pain point.\nStructure for Skimming:\nUse short paragraphs (1-3 lines each) for easy mobile reading.\nInclude practical examples, insights, or observations related to DevOps, MLOps, Cloud Engineering, or ML Engineering.\nNo separate titles for each paragraph in the final post.\nEducational & Friendly Tone: Write in a practical, helpful, and friendly tone—never salesy or filled with jargon. Use \"you\" and \"I\" to create direct connection with engineering leaders.\nAdd Personality: Use 1-2 emojis sparingly and only if it adds a friendly tone.\nVary Sentence Lengths: Mix short and longer sentences for a natural, human tone.\nCall to Action (CTA): ALWAYS end the post with a direct question or invitation for comments that encourages engagement (e.g., \"How do you handle this in your team?\"). Vary the CTA format each time.\nHashtags: Include no more than 8 relevant hashtags at the end focusing on engineering leadership topics. Rotate hashtag combinations.\nWord Limit: Keep total post length under 250 words.\nFocus Areas for Content: Address pain points such as:\nSlow deployments and CI/CD challenges\nCloud cost overruns and optimization\nDifficulty in scaling ML/AI systems\nSecurity & compliance concerns in cloud pipelines\nHiring bottlenecks for cloud or ML ops talent\nComplex release processes and team coordination\nMake each post feel like it's written by a different engineering leader with unique perspectives and experiences.\"\n\n",
"promptType": "define",
"hasOutputParser": true
},
"typeVersion": 1.6
},
{
"id": "9f572b49-aa81-489f-af97-3472556a4bde",
"name": "Google Gemini 聊天模型3",
"type": "@n8n/n8n-nodes-langchain.lmChatGoogleGemini",
"position": [
-220,
380
],
"parameters": {
"options": {
"temperature": 0.8
},
"modelName": "models/gemini-2.0-flash"
},
"credentials": {
"googlePalmApi": {
"id": "Your_Gemini_API",
"name": "Gemini API"
}
},
"typeVersion": 1
},
{
"id": "80cc156c-7e06-42f7-8b45-f949f46486d8",
"name": "结构化输出解析器3",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
-40,
400
],
"parameters": {
"jsonSchemaExample": "{\n \"post title\": \"Exciting New Feature Launch 🚀\",\n \"post content\": \"After months of collaboration, testing, and fine-tuning, we're thrilled to introduce our latest product feature: Smart Insights. It helps users uncover meaningful patterns in their data with just a few clicks. This wouldn't have been possible without our incredible team and supportive community. We're excited for what's next — and we'd love your feedback!\",\n \"image description\": \"A laptop screen showcasing the new Smart Insights dashboard with colorful charts and graphs, surrounded by a team clapping in the background.\",\n\"Hashtags\":[\"#AI\",\"#Automation\"]\n}"
},
"typeVersion": 1.2
},
{
"id": "056f597f-c921-477a-bf00-021b30069997",
"name": "创建帖子",
"type": "n8n-nodes-base.linkedIn",
"position": [
320,
60
],
"parameters": {
"text": "={{ $('Content Creator').item.json.output['post content'] }}\n\n{{ $json.output.Hashtags.join(' ') }}\n",
"person": "-GZMQPAt4k",
"additionalFields": {},
"shareMediaCategory": "IMAGE"
},
"credentials": {
"linkedInOAuth2Api": {
"id": "YOUR_LinkedIN_Credenticail_ID",
"name": "LinkedIn account 3"
}
},
"typeVersion": 1
},
{
"id": "7c001e40-0f04-49b9-93d7-b3ee54da9519",
"name": "合并",
"type": "n8n-nodes-base.merge",
"position": [
80,
60
],
"parameters": {
"mode": "combine",
"options": {},
"combineBy": "combineByPosition"
},
"typeVersion": 3.2
},
{
"id": "e2442399-c2a4-460e-9dc3-ff2bfb5cf18d",
"name": "话题标签生成器 / SEO",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
-240,
180
],
"parameters": {
"text": "=You are a world-class LinkedIn Growth and SEO Strategist.\n\n**Your Context:**\n- **Company:** Intuz Solutions\n- **Specialty:** Cloud Computing, ERP/CRM Software Solution, AR/VR Apps, Workflow Automation System, Chatbot Development, Mobile & Web Apps, IoT, AI Consultation, AI PoC Development, and Custom AI App Development\n- **Target Audience:** Solopreneurs, content creators, and digital-first founders.\n- **Goal:** Maximize the visibility and engagement of our LinkedIn content with our ideal audience.\n\n**Your Task:**\nAnalyze the following LinkedIn post content and generate a strategic list of hashtags.\n\n**Post Content to Analyze:**\nTitle: {{ $json.output['post title'] }}\nContent: {{ $json.output['post content'] }}\n\n**Generate Hashtags in These 4 Categories:**\n1. **Broad Industry (2-3 hashtags):** High-volume tags for wide reach (e.g., #AI, #Automation, #Marketing).\n2. **Niche Topic (3-4 hashtags):** Specific tags directly related to the post's core message (e.g., #Cloud, #LinkedInStrategy, #AIworkflows).\n3. **Target Audience (2-3 hashtags):** Tags your ideal customer follows or identifies with (e.g., #Solopreneur, #Startups, #FounderLife).\n4. **Branded (1 hashtag):** A unique tag for our community (e.g., #Intuz).\n\nPlease ensure all hashtags start with # and are relevant to the provided content.",
"options": {},
"promptType": "define",
"hasOutputParser": true
},
"typeVersion": 1.8
},
{
"id": "a66121ec-9193-45cb-bcfe-175ace031c18",
"name": "生成图片",
"type": "@n8n/n8n-nodes-langchain.openAi",
"position": [
-220,
0
],
"parameters": {
"prompt": "=Generate an image for a linkedin post this is the description: {{ $json.output['image description'] }} .The images should be realistic for linkedin.",
"options": {
"size": "1024x1024"
},
"resource": "image"
},
"credentials": {
"openAiApi": {
"id": "YOUR_OPEN_AI_API",
"name": "OpenAi API"
}
},
"typeVersion": 1.8
}
],
"connections": {
"Merge": {
"main": [
[
{
"node": "Create a post",
"type": "main",
"index": 0
}
]
]
},
"Content Creator": {
"main": [
[
{
"node": "Hashtag Generator / SEO",
"type": "main",
"index": 0
},
{
"node": "Generate an image",
"type": "main",
"index": 0
}
]
]
},
"Generate an image": {
"main": [
[
{
"node": "Merge",
"type": "main",
"index": 0
}
]
]
},
"Schedule Trigger1": {
"main": [
[
{
"node": "Content Topic Generator",
"type": "main",
"index": 0
}
]
]
},
"Content Topic Generator": {
"main": [
[
{
"node": "Content Creator",
"type": "main",
"index": 0
}
]
]
},
"Hashtag Generator / SEO": {
"main": [
[
{
"node": "Merge",
"type": "main",
"index": 1
}
]
]
},
"Google Gemini Chat Model1": {
"ai_languageModel": [
[
{
"node": "Content Topic Generator",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Google Gemini Chat Model2": {
"ai_languageModel": [
[
{
"node": "Content Creator",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Google Gemini Chat Model3": {
"ai_languageModel": [
[
{
"node": "Hashtag Generator / SEO",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Structured Output Parser3": {
"ai_outputParser": [
[
{
"node": "Hashtag Generator / SEO",
"type": "ai_outputParser",
"index": 0
}
]
]
},
"Structured Output Parser6": {
"ai_outputParser": [
[
{
"node": "Content Topic Generator",
"type": "ai_outputParser",
"index": 0
}
]
]
},
"Structured Output Parser7": {
"ai_outputParser": [
[
{
"node": "Content Creator",
"type": "ai_outputParser",
"index": 0
}
]
]
}
}
}常见问题
如何使用这个工作流?
复制上方的 JSON 配置代码,在您的 n8n 实例中创建新工作流并选择「从 JSON 导入」,粘贴配置后根据需要修改凭证设置即可。
这个工作流适合什么场景?
中级 - 内容创作, 多模态 AI
需要付费吗?
本工作流完全免费,您可以直接导入使用。但请注意,工作流中使用的第三方服务(如 OpenAI API)可能需要您自行付费。
相关工作流推荐
实时 - 使用Gemini和Creatomate自动化病毒式AI视频制作与发布
使用Gemini和Creatomate自动化AI视频创作与多平台发布
Set
Code
Wait
+15
47 节点Intuz
内容创作
使用GPT-5和fal.ai图像从关键词到WordPress自动化SEO博客流程
使用GPT-5和fal.ai图像从关键词到WordPress自动化SEO博客流程
Set
Code
Wait
+20
96 节点Paul
内容创作
内容聚合
使用Gemini AI从网站文章自动化社交媒体帖子发布到LinkedIn和X/Twitter
If
Set
Xml
+16
34 节点Vadim
内容创作
WordPress + 社交媒体
基于GPT/Gemini和WordPress的自动化博客创建与多平台发布
If
Set
Switch
+18
44 节点Khairul Muhtadin
内容创作
LinkedIn和X病毒内容自动引擎
使用AI生成和发布自动创建LinkedIn和X的病毒内容
If
Set
Wait
+26
156 节点Diptamoy Barman
内容创作
使用Perplexity和GPT为WordPress创建SEO优化博客,包含关键词和媒体
使用Perplexity和GPT为WordPress创建SEO优化博客,包含关键词和媒体
Set
Code
Limit
+22
124 节点Paul
内容创作
工作流信息
难度等级
中级
节点数量13
分类2
节点类型8
作者
Intuz
@intuzA boutique tech consulting company, helping businesses with custom AI/ML, Workflow Automations, and software development.
外部链接
在 n8n.io 查看 →
分享此工作流