Skip to main content
Hermes supports both of Automate It’s integration surfaces. Use the skill if you want the guided workflow; use MCP if you just want the tools.

​
Get an API key

Both options below authenticate with a scoped ak_… key — Hermes has no OAuth flow for Automate It, so create the key first:
  1. In the Automate It web app, click your avatar at the bottom of the sidebar to reach Profile (https://automate.it.com/app/<workspace-slug>/settings/profile). Keys can’t be minted from the mobile apps.
  2. Under Developer API Keys, click Create Key.
  3. Name it something you’ll recognize (“Hermes agent”) and tick tasks:read, tasks:write, content:write, and skills:read — enough to create tasks, submit content into review, and read your workspace’s voice and formatting skills.
  4. Copy the ak_… secret. It’s shown once; it’s the ak_your_key value you put in ~/.hermes/.env below. Don’t paste it into a chat message.
The full scope table is in API keys & scopes. Hermes reads AgentSkills-format skill folders from ~/.hermes/skills/. Install from ClawHub into Hermes’ skills directory:
Hermes’ URL-based skills install handles single files only — the Automate It skill is a folder (SKILL.md + ait.mjs), so install it via the ClawHub CLI as above.
Install the CLI the skill drives, then put the key in ~/.hermes/.env. Hermes reads that file for user-managed secrets and exports it into the shells it spawns for tools, so the skill’s ait.mjs inherits it — no export in an interactive shell, where the key would land in your history:
The agent discovers the skill via skills_list() and follows its instructions — creating tasks, submitting content into the human review queue, and revising after rejection.

​
Option B: remote MCP

In ~/.hermes/config.yaml:
Or from the CLI:
Hermes interpolates ${env:VAR} (and ${VAR}) in any string in a server entry, resolving from the profile’s secret scope and then the process environment — so keep the ak_… value in ~/.hermes/.env as above and out of config.yaml, which is cleartext and easy to commit by accident. Tools surface as mcp_automate-it_<tool> — the full task lifecycle, content editing, skills, files, and automations. See Worker mode for the loop an autonomous agent should run.