Skip to Content
IntegrationsZapier Integration

Zapier Integration

Connect your Hatcher agents to 6,000+ apps using Zapier . Automate workflows like forwarding emails to your agent, posting agent responses to Slack, or triggering actions when an agent starts or stops.

Authentication

All Zapier triggers and actions authenticate with your Hatcher API key.

  1. Go to Dashboard > Settings > API Keys and generate a key (starts with hk_).
  2. When adding the Hatcher app in Zapier, paste your API key when prompted.
  3. Zapier will verify the key by calling the Hatcher API. If it fails, double-check the key has not been revoked.

Search for Hatcher in Zapier’s app directory, or use the invite link provided in your dashboard.

Available Triggers

Triggers fire automatically when something happens with your agents.

TriggerDescription
Agent MessageFires when an agent receives a new message and responds. Includes the user message, agent response, source platform, and timestamp.
Agent StartedFires when an agent’s container starts running.
Agent StoppedFires when an agent’s container stops (manual stop or auto-sleep).
Agent ErrorFires when an agent encounters an error (container crash, LLM failure, etc.).

Trigger data fields

The Agent Message trigger provides:

  • event — Event type (e.g., message)
  • agentId — The agent’s unique ID
  • agentName — The agent’s display name
  • message — The user’s message
  • response — The agent’s reply
  • userId — ID of the user who sent the message
  • platform — Source platform (api, telegram, discord, web)
  • timestamp — When the event occurred

Available Actions

Actions let you control your agents from any Zapier workflow.

ActionDescription
Send MessageSend a message to an agent and receive its response. Requires agentId and message.
Create AgentCreate a new agent. Requires name and framework. Optionally set description and config.
Start AgentStart an agent’s container. Requires agentId.
Stop AgentStop an agent’s container. Requires agentId.

Searches

SearchDescription
Find AgentLook up an agent by ID. Returns agent details including name, framework, status, and message count.

Example Zaps

Forward emails to your agent

  1. Trigger: Gmail — New Email
  2. Action: Hatcher — Send Message
    • Agent ID: your agent’s ID
    • Message: {{email_body}}
  3. Action: Gmail — Send Email (reply with the agent’s response)

Post agent responses to Slack

  1. Trigger: Hatcher — Agent Message
  2. Filter: Only continue if platform = “telegram” (or any platform)
  3. Action: Slack — Send Channel Message
    • Channel: #agent-activity
    • Message: Agent {{agentName}} replied: {{response}}

Alert on agent errors

  1. Trigger: Hatcher — Agent Error
  2. Action: Slack — Send Direct Message
    • Message: Agent {{agentName}} ({{agentId}}) encountered an error. Check the dashboard.

Auto-restart stopped agents

  1. Trigger: Hatcher — Agent Stopped
  2. Delay: Wait 30 seconds
  3. Action: Hatcher — Start Agent
    • Agent ID: {{agentId}}

Create agents from a Google Sheet

  1. Trigger: Google Sheets — New Row
  2. Action: Hatcher — Create Agent
    • Name: {{column_A}}
    • Framework: {{column_B}}
    • Description: {{column_C}}
  3. Action: Hatcher — Start Agent

Setting Up Webhooks

The message and lifecycle triggers use webhooks. When you create a Zap with a Hatcher trigger:

  1. Zapier generates a unique webhook URL.
  2. Hatcher registers that URL against your agent.
  3. Events are sent to Zapier in real-time as they happen.

No manual webhook configuration is needed — Zapier handles the setup automatically when you connect your account.

Tips

  • Use Zapier’s Filter step to narrow triggers (e.g., only messages from Telegram, or only specific agents).
  • The Send Message action returns the agent’s response, so you can chain it into further steps.
  • Agent IDs are available in the dashboard URL: https://hatcher.host/dashboard/agents/{agent-id}.
  • Hosted LLM usage spends AI Credits; BYOK usage is metered only by your provider.
WhatsApp IntegrationKnowledge Base