Executeworkflow Executecommandtool. Uses stickyNote, mcpTrigger, executeCommandTool, executeWorkflowTrigger. Event-driven trigger; 14 nodes.
Workflow 3630. Uses mcpTrigger, executeCommandTool, executeWorkflowTrigger, executeCommand. Event-driven trigger; 14 nodes.
magnify-chatbot. Uses chatTrigger, agent, lmChatGroq, memoryBufferWindow. Chat trigger; 8 nodes.
QuantumDefender AI is a next-generation intelligent cybersecurity assistant designed to harness the symbolic strength of quantum computing’s promise alongside cutting-edge AI capabilities. This sophis
Orquestador Normativa. Uses chatTrigger, textClassifier, lmChatOllama, agent. Chat trigger; 12 nodes.
Example agent workflow. Uses chatTrigger, agent, lmChatOllama, httpRequestTool. Chat trigger; 6 nodes.
6 of 6 workflows in this view · Browse all →
FAQ
How many n8n Executecommandtool workflows are in the catalog?
6 n8n workflows in AutomationFlows currently use the Executecommandtool integration — triggers, actions, or both.
How do I connect Executecommandtool in n8n?
After importing the workflow JSON, n8n will prompt for Executecommandtool credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.
Can I combine these with other integrations?
Yes — most Executecommandtool workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.