n8n workflows

Automate infrastructure, monitoring, and deployment with 57+ pre-built n8n workflows that connect directly to Jarvis agents.

n8n is the workflow automation layer of Jarvis. It connects your agents to external systems, schedules recurring tasks, reacts to events, and chains together operations that span multiple services — without requiring you to write custom integration code.

Jarvis ships with 57+ pre-built workflows covering the most common homelab automation scenarios.

MCP tools

Trigger n8n workflows as MCP tools from inside an agent.

API reference

Call agent and workflow APIs directly from n8n nodes.

Pre-built workflows

Jarvis includes workflows across three categories:

Category	Examples
Infrastructure	Node health checks, disk cleanup, container restarts, mesh rebalancing
Monitoring	Alert routing, metric aggregation, uptime notifications, incident creation
Deployment	Docker image pulls, service rollouts, config propagation, post-deploy verification

Each workflow is ready to use and can be customized from the n8n editor at http://your-jarvis-host:5678.

Trigger a workflow

Workflows run when triggered — by a webhook, a schedule, an event from another system, or directly from a Jarvis agent.

1. Find the workflow ID

   Open the n8n editor at http://your-jarvis-host:5678 and locate the workflow you want to trigger. The workflow ID appears in the URL: /workflow/42.

   Alternatively, list workflows via the Jarvis API:

   curl https://your-jarvis-host/api/tools \
     | jq '.[] | select(.name | startswith("jarvis.workflow"))'
   
2. Enable the webhook trigger

   Open the workflow and confirm the trigger node is active. For webhook-triggered workflows, the trigger node shows the webhook URL — for example:

   http://your-jarvis-host:5678/webhook/deploy-service
   

   Toggle the workflow to Active if it isn’t already.

3. Send the trigger request

   POST to the webhook URL with any payload the workflow expects:

   curl -X POST http://your-jarvis-host:5678/webhook/deploy-service \
     -H "Content-Type: application/json" \
     -d '{
       "service": "monitoring-stack",
       "node": "ai-mini-x1",
       "notify": true
     }'
   
4. Check the execution result

   The webhook returns immediately with an execution ID. To check the result:

   curl http://your-jarvis-host:5678/api/v1/executions/EXECUTION_ID
   

   Executions also appear in the n8n editor under Executions.

Trigger types

Workflows can be triggered in several ways:

• Webhook — an HTTP request hits a unique URL you define in the workflow
• Schedule — cron-style scheduling built into the trigger node
• Event — another workflow, an agent, or an external system emits an event
• Manual — you click Execute Workflow in the n8n editor

Webhook triggers are the most common when integrating with Jarvis agents.

Create a workflow that calls a Jarvis agent

You can use n8n as the orchestrator: trigger a workflow on a schedule or event, then have it call a Jarvis agent to do the reasoning work.

1. Add an HTTP Request node

   In the n8n editor, add an HTTP Request node after your trigger. Set the method to POST and the URL to the agent API endpoint:

   https://your-jarvis-host/agents/invoke
   
2. Set the request body

   In the node’s Body settings, add a JSON body with the agent and task:

   {
     "agent": "hermes",
     "task": "Check disk usage on all nodes and file a ServiceNow incident if any node is above 85%."
   }
   
3. Handle the response

   The agent API responds synchronously with the agent’s output. Add downstream nodes to route based on the result — for example, send a Slack notification if the agent filed an incident.

For long-running agent tasks, use the async agent endpoint and poll for completion using a Wait node followed by an HTTP Request to check status.

Connect workflows to the agent API

Any n8n node that makes HTTP requests can call the Jarvis agent API. The most common patterns are:

Run an agent from a workflow:

curl -X POST https://your-jarvis-host/agents/invoke \
  -H "Authorization: Bearer your-api-key" \
  -H "Content-Type: application/json" \
  -d '{
    "agent": "paperclip",
    "task": "Summarize overnight monitoring alerts and post to the ops channel."
  }'

Trigger a workflow from an agent (using the jarvis.workflow.trigger MCP tool):

When an agent invokes jarvis.workflow.trigger, it POSTs to the n8n webhook on your behalf — so agents and workflows can call each other bidirectionally.

Customize existing workflows

All pre-built workflows are editable. To customize one:

1. Open http://your-jarvis-host:5678 and navigate to Workflows
2. Click the workflow you want to modify
3. Edit nodes, add branches, or change trigger conditions
4. Save and ensure the workflow is set to Active

Editing a pre-built workflow replaces it. If you want to preserve the original, duplicate the workflow first using the … menu.