Skip to main content
1

Install zombiectl

npm install -g @usezombie/zombiectl
zombiectl --version
2

Log in

zombiectl login
Opens your browser for authentication. Your session is stored locally.
3

Install a zombie template

zombiectl install lead-collector
This creates a lead-collector.md file in your current directory — a YAML + markdown config that defines your zombie: its trigger (inbound webhook), skills (agentmail), and instructions (what the agent should do when an event arrives).Open the file to see what’s inside:
lead-collector.md
---
name: lead-collector
trigger:
  type: webhook
  source: email
  token: your-webhook-token
skills:
  - agentmail
credentials:
  agentmail_api_key: op://your-vault/agentmail/api_key
budget:
  max_tokens_per_event: 4000
  max_wall_seconds: 60
---

You are a lead qualification agent. When an email arrives:
1. Read the sender and subject line.
2. If it looks like a real sales inquiry, reply with a short acknowledgement.
3. Log what you did in the activity stream.
4

Add credentials

zombiectl credential add agentmail --key api_key
Credentials are stored encrypted in the UseZombie vault — your agent never sees them. The firewall injects them per-request, outside the sandbox boundary.
5

Start the zombie

zombiectl up
This uploads your config, provisions a webhook endpoint, and starts the persistent agent process in the UseZombie cloud. Within seconds your zombie is live and waiting for events.You will see output like:
✓ zombie created  id=019abc12-8d3a-7f13-8abc-2b3e1e0a6f11
✓ webhook live    POST https://hooks.usezombie.com/v1/webhooks/019abc12-8d3a-7f13-8abc-2b3e1e0a6f11
✓ agent running   status=alive
6

Send a test event

curl -X POST https://hooks.usezombie.com/v1/webhooks/<your-zombie-id> \
  -H "Authorization: Bearer your-webhook-token" \
  -H "Content-Type: application/json" \
  -d '{"event_id":"test-001","type":"email.received","data":{"from":"[email protected]","subject":"Demo request"}}'
7

Check status and logs

zombiectl status
zombiectl logs
zombiectl logs streams the activity log — every event received, every action taken, every credential used — with timestamps and token counts.
8

Kill it when you're done

zombiectl kill lead-collector
The zombie stops immediately. No lingering processes, no billing after the kill.

​
What’s next?

How it works

Understand the credential firewall and sandbox model.

Key concepts

Zombies, triggers, skills, credentials, and the kill switch.

CLI reference

Full command reference for zombiectl.