AutomationFlowsRecipes › Executecommand → HTTP Request

Executecommand → HTTP Request

When you need Executecommand and HTTP Request talking to each other, here are the 138 n8n workflows in the catalog that already do it. Each is integration-tagged and privacy-stripped — copy the JSON and import.

Workflows that pair Executecommand with HTTP Request

AI & RAG

This workflow creates a multi-talented AI assistant named Simran that interacts with users via Telegram. It can handle text and voice messages, understand the user's intent, and perform various tasks.

MongoDB, Chain Llm, Google Gemini Chat +11
AI & RAG

RAG CHATBOT Main. Uses telegram, telegramTrigger, lmChatOpenAi, n8n-nodes-mcp. Event-driven trigger; 87 nodes.

Telegram, Telegram Trigger, OpenAI Chat +8
AI & RAG

HeyDinastia. Uses executeCommand, httpRequest, youTube, postgres. Webhook trigger; 66 nodes.

Execute Command, HTTP Request, YouTube +15
Web Scraping

Sign PDF documents with legally-compliant digital signatures using X.509 certificates. Supports multiple PAdES signature levels (B, T, LT, LTA) with optional visible stamps.

Execute Command, HTTP Request, Read Write File +1
Data & Sheets

Workflow Importer. Uses extractFromFile, executeCommand, readWriteFile, httpRequest. Event-driven trigger; 58 nodes.

Execute Command, Read Write File, HTTP Request +3
Web Scraping

This workflow allows you to import any workflow from a file or another n8n instance and map the credentials easily. A multi-form setup guides you through the entire process At the beginning you have t

Execute Command, Read Write File, HTTP Request +3
Slack & Telegram

03 - Command Handler. Uses executeWorkflowTrigger, telegram, executeCommand, postgres. Event-driven trigger; 53 nodes.

Execute Workflow Trigger, Telegram, Execute Command +2
AI & RAG

Who’s it for Creators who want to create faceless videos automatically, while keeping human oversight and quality control.

Read Write File, Agent, OpenAI Chat +7
AI & RAG

My workflow 4. Uses formTrigger, httpRequest, googleDrive, agent. Event-driven trigger; 48 nodes.

Form Trigger, HTTP Request, Google Drive +6
AI & RAG

Video-To-Hugo. Uses httpRequest, lmChatOllama, moveBinaryData, youTube. Event-driven trigger; 47 nodes.

HTTP Request, Ollama Chat, Move Binary Data +5
Social Media

Automated Tiktok Videos. Uses executeCommand, httpRequest, lmChatGroq, chainLlm. Webhook trigger; 45 nodes.

Execute Command, HTTP Request, Groq Chat +3
Slack & Telegram

This n8n workflow provides automated monitoring of Public Key Infrastructure (PKI) components including CA certificates, Certificate Revocation Lists (CRLs), and associated web services. It extracts c

Write Binary File, Execute Command, HTTP Request
AI & RAG

MallanooSploit. Uses openAi, executeCommand, httpRequest. Webhook trigger; 44 nodes.

OpenAI, Execute Command, HTTP Request
Slack & Telegram

PsyCardv2. Uses executeCommand, telegram, readBinaryFile, googleDrive. Webhook trigger; 41 nodes.

Execute Command, Telegram, Read Binary File +2
AI & RAG

Turbo Videogen. Uses lmChatOpenRouter, agent, httpRequest, formTrigger. Event-driven trigger; 41 nodes.

OpenRouter Chat, Agent, HTTP Request +7
AI & RAG

LinkedIn_validator. Uses executeWorkflowTrigger, mySql, executeCommand, chainLlm. Event-driven trigger; 40 nodes.

Execute Workflow Trigger, MySQL, Execute Command +7
AI & RAG

LinkedIn_validator. Uses executeWorkflowTrigger, mySql, executeCommand, chainLlm. Event-driven trigger; 40 nodes.

Execute Workflow Trigger, MySQL, Execute Command +7
Slack & Telegram

Vendorbot Form Filler. Uses executeCommand, gmail, telegram, slack. Event-driven trigger; 39 nodes.

Execute Command, Gmail, Telegram +6
Slack & Telegram

Transcript. Uses httpRequest, telegram, telegramTrigger, readWriteFile. Event-driven trigger; 37 nodes.

HTTP Request, Telegram, Telegram Trigger +4
Social Media

📘 Multi-Photo Facebook Post (Windows Directory) – How to Use ✅ Requirements To run this automation, make sure you have the following:

Read Write File, Execute Command, Facebook Graph Api +1
AI & RAG

veo limpo new. Uses moveBinaryData, httpRequest, chatTrigger, baserow. Webhook trigger; 36 nodes.

Move Binary Data, HTTP Request, Chat Trigger +8
Email & Gmail

sprint-review. Uses httpRequest, jira, gmail, executeCommand. Event-driven trigger; 36 nodes.

HTTP Request, Jira, Gmail +2
AI & RAG

This workflow automates the creation of a daily sports podcast from your favorite news sources. It fetches articles, uses AI to write a digest and a two-person dialogue, and produces a single, merged

Google Gemini Chat, RSS Feed Read, Execute Command +4
Data & Sheets

Mastodon2MemosGitHubNotion. Uses httpRequest, executeCommand, s3, github. Webhook trigger; 34 nodes.

HTTP Request, Execute Command, S3 +2

See more Executecommand workflows · HTTP Request workflows

FAQ

How do I trigger a HTTP Request action from Executecommand?

Most workflows in this list use either a Executecommand webhook trigger (real-time) or a polling trigger (every N minutes). From there, downstream HTTP Request nodes handle the action. Open any workflow's detail page to see the exact node graph.

Do I need both a Executecommand and a HTTP Request account?

Yes — n8n connects to each integration via your own credentials. AutomationFlows strips credential IDs before publishing, so you'll add your own.

Are these Executecommand → HTTP Request workflows free?

Yes — every workflow on AutomationFlows is free to browse and copy. Pro adds a multi-signal QualityScore on every workflow plus bulk JSON download.