Skip to main content
Hermes is Jarvis’s communication and coordination agent. While Paperclip focuses on general task orchestration, Hermes specializes in message routing, event-driven coordination, and structured handoffs — between agents, between systems, and between your platform and the outside world.

​
What Hermes handles

Hermes is the right agent when your task involves:
  • Notifications and alerts — sending messages to Slack, email, webhooks, or other channels
  • Cross-agent coordination — passing context and results between Paperclip and Claude Code
  • Event-driven workflows — triggering actions in response to system events or external signals
  • Structured communication — formatting and routing outputs to downstream consumers
  • Status reporting — summarizing results from other agents and distributing them
For infrastructure execution, use Paperclip. For code work, use Claude Code.

​
Typical Hermes workflow

1

Trigger Hermes with an event or task

Hermes can be invoked directly via the API or triggered automatically by an n8n workflow when an event fires.
curl -X POST https://your-jarvis-host/agents/invoke \
  -H "Content-Type: application/json" \
  -d '{
    "agent": "hermes",
    "task": "Send a Slack alert when any brain mesh node reports CPU usage above 90%."
  }'
2

Hermes evaluates the message and recipients

Hermes determines the appropriate channel, format, and recipients based on your task and the registered integrations.
3

External systems are contacted

Hermes calls the relevant integration — Slack, webhook, SMTP, or a custom endpoint — to deliver the message or trigger the action.
4

Confirmation is returned

Hermes returns delivery confirmation and any responses from the external system, so you can verify the handoff succeeded.

​
Invoke Hermes

​
Via API

curl -X POST https://your-jarvis-host/agents/invoke \
  -H "Content-Type: application/json" \
  -d '{
    "agent": "hermes",
    "task": "Your communication or coordination task here."
  }'

​
With routing options

{
  "agent": "hermes",
  "task": "Summarize today's deployment activity and post it to the #ops Slack channel.",
  "options": {
    "channel": "slack",
    "destination": "#ops"
  }
}
See the agents API reference for the full request schema.

​
Example usage

​
Cross-agent handoff

Hermes can receive results from Paperclip and route them to an external system: 
{
  "agent": "hermes",
  "task": "Take the disk usage report from Paperclip and open a ServiceNow change request for each node flagged for cleanup.",
  "context": {
    "source_agent": "paperclip",
    "report_id": "disk-scan-2026-04-04"
  }
}

​
Event notification

{
  "agent": "hermes",
  "task": "When the n8n monitoring workflow fires a critical alert, send an SMS to the on-call engineer and log the event to memory."
}

​
How Hermes coordinates with other agents

Hermes acts as the messaging layer between agents. When Paperclip completes a task that produces output for another system, Hermes handles the handoff — formatting the output, selecting the right channel, and confirming delivery. Hermes can also receive incoming signals (webhooks, events) and route them to the appropriate agent for processing.

​
Supported integrations

Hermes works with any integration registered in your Jarvis environment:
  • Slack — post messages, alerts, and summaries to channels
  • Webhooks — fire outbound HTTP requests to internal or external endpoints
  • n8n — trigger or respond to n8n workflows
  • Memory — write structured summaries to Qdrant or Mem0 for later retrieval
  • ServiceNow — create and update records as part of a coordination flow
  • SMTP — send email notifications for alerts or reports
For the full integration list, see integrations.