Skip to Content
IntegrationsMake (Integromat) Integration

Make (Integromat) Integration

Connect your Hatcher agents to Make  (formerly Integromat) to build visual automation workflows. Send messages to agents, react to agent events, and integrate with hundreds of other apps.

Authentication

Get your API key

Go to Dashboard > Settings > API Keys and generate a key (starts with hk_).

Add Hatcher to Make

  1. In your Make scenario, click + to add a module.
  2. Search for Hatcher.
  3. Select any Hatcher module and click Create a connection.
  4. Paste your API key and click Save.

Make will verify the key by calling GET /api/v1/me. If it fails, check that your key is valid and has not been revoked.

Available Modules

Actions

ModuleDescriptionRequired Fields
Send Message to AgentSend a message and receive the agent’s response. Supports optional conversation history for context.Agent ID, Message
Create AgentCreate a new agent on your account.Name, Framework
List AgentsRetrieve all agents on your account with their status and metadata.—
Start AgentStart an agent’s container.Agent ID
Stop AgentStop an agent’s container.Agent ID

Triggers (Webhooks)

ModuleDescription
Watch for New MessagesFires when an agent receives and responds to a message. Provides event type, agent info, user message, agent response, platform, and timestamp.
Watch EventsFires on agent lifecycle events (started, stopped, error).

Module Details

Send Message to Agent

Sends a message to a specified agent and returns the response.

Inputs:

  • Agent ID (required) — The agent to message. Use “List Agents” to find IDs.
  • Message (required) — The text message to send.
  • Conversation History (optional) — Array of previous messages (role + content) for multi-turn context.

Outputs:

  • content — The agent’s text response.
  • model — The LLM model that generated the response.

Watch for New Messages

Webhook-based trigger that fires in real-time when your agent receives a message.

Outputs:

  • event — Event type (e.g., message)
  • agentId — Agent ID
  • agentName — Agent display name
  • message — The user’s message
  • response — The agent’s reply
  • userId — Sender’s user ID
  • platform — Source platform (api, telegram, discord, web)
  • timestamp — Event timestamp

Example Scenarios

Customer support pipeline

  1. Webhook — Receive customer message from your website
  2. Hatcher: Send Message — Forward to your support agent
  3. Router:
    • If response contains “escalate” -> Email: Send to support team
    • Otherwise -> HTTP: Respond with agent’s answer

Daily agent health check

  1. Schedule — Every day at 9 AM
  2. Hatcher: List Agents — Get all agents
  3. Iterator — Loop through agents
  4. Filter — Only agents with status != “active”
  5. Slack: Send Message — Alert: “Agent {{name}} is {{status}}”

Log all agent conversations

  1. Hatcher: Watch for New Messages
  2. Google Sheets: Add Row
    • Timestamp: {{timestamp}}
    • Agent: {{agentName}}
    • User Message: {{message}}
    • Agent Response: {{response}}
    • Platform: {{platform}}

Webhook Setup

When you add a Hatcher trigger module to your scenario:

  1. Make generates a webhook URL automatically.
  2. Click Register webhook — Make calls the Hatcher API to set it up.
  3. Events flow in real-time once the scenario is active.

Webhooks only fire while your Make scenario is active. If the scenario is paused, events are not queued.

Tips

  • Use Make’s Router module to branch logic based on agent responses or event types.
  • The Send Message module returns the full response, so you can parse it with Make’s text functions and route accordingly.
  • Combine with Make’s HTTP module to call the Hatcher API directly for operations not yet covered by dedicated modules.
  • Agent IDs are visible in your dashboard URL: https://hatcher.host/dashboard/agents/{agent-id}.
Last updated on
GitHub ActionSlack Integration