AutomationFlows › Executecommand

n8n workflows for Executecommand.

All n8n workflows that use the Executecommand integration. Each is integration-tagged, privacy-stripped, and importable into your n8n instance in one click.
AI & RAG
Clara Agent Pipeline (local)

Clara Agent Pipeline (Local). Uses executeCommand. Event-driven trigger; 2 nodes.

Execute Command
General
Scraper Statup

Scraper statup. Uses executeCommand. Webhook trigger; 2 nodes.

Execute Command
General
Paren Pulse — Weekly Snapshot to #data

Paren Pulse — weekly snapshot to #Data. Uses executeCommand. Scheduled trigger; 2 nodes.

Execute Command

3 of 403 workflows on page 3 of 3 · Browse all →

FAQ

How many n8n Executecommand workflows are in the catalog?

403 n8n workflows in AutomationFlows currently use the Executecommand integration — triggers, actions, or both.

How do I connect Executecommand in n8n?

After importing the workflow JSON, n8n will prompt for Executecommand 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 Executecommand workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.