ai-voice-agents

n8n community node for the AI Voice Agent from SuperHippo — create leads, trigger calls, and react to call outcomes.

Documentation

@superhippo/n8n-nodes-ai-voice-agents

n8n community node for the SuperHippo AI Voice Agents platform. Manage leads and outbound calls, fetch call recordings, transcripts and summaries, and react to call outcomes directly from your n8n workflows.

This package contains two nodes:

  • SuperHippo AI Voice Agents — an action node for leads and calls.
  • SuperHippo AI Voice Agents Trigger — a webhook trigger that starts a workflow on call events.

Installation

In n8n: Settings → Community Nodes → Install and enter:

@superhippo/n8n-nodes-ai-voice-agents

Credentials

Create a SuperHippo AI Voice Agents API credential:

  • Base URL — your SuperHippo API root, e.g. https://ai.hippochat.io
  • API Key — sent as the X-API-KEY header on every request.

Saving the credential runs a test request against GET /api/accounts/me.

Action node — SuperHippo AI Voice Agents

Lead operations

Operation Method & endpoint Notes
List Leads GET /api/leads Page, Page Size + filters (status, source, agent, timezone, search text, date range, include deleted)
Create Lead POST /api/leads Name, Phone Number, Timezone required; optional Email, Agent ID, Lead Metadata
Create Lead and Call POST /api/leads/call Same fields plus Call Delay (Seconds) — creates the lead and enqueues a call
Get Lead GET /api/leads/{id}
Update Lead PUT /api/leads/{id} All fields optional
Delete Lead DELETE /api/leads/{id}
Assign Agent to Lead POST /api/leads/assign-agent Comma-separated Lead IDs + Agent ID
Unassign Agent to Lead POST /api/leads/unassign-agent Comma-separated Lead IDs

Call operations

Operation Method & endpoint Notes
List Calls GET /api/calls Page, Page Size + filters (lead, agent, status, timezone, search text, date range, include deleted)
List Queued Calls GET /api/calls/queued Queued and scheduled calls
Bulk Instant Calls POST /api/calls/bulk Comma-separated Lead IDs — one ID for a single call, up to 1000
Bulk Schedule Calls POST /api/calls/schedule/bulk Lead IDs plus scheduling options (see below)
Get Call GET /api/calls/{id}
Delete Call DELETE /api/calls/{id}
Get Call Recording GET /api/calls/{id}/recording
Get Call Transcript GET /api/calls/{id}/transcript
Get Call Summary GET /api/calls/{id}/summary
Get Call Action Items GET /api/calls/{id}/action-items

Bulk Schedule Calls has three mutually exclusive scheduling modes, checked in order:

  1. Custom window — set Window Start Hour + Window End Hour; each lead gets a random time in that window.
  2. Per-lead random — leave all time fields empty; each lead gets a random time in its own 9–18 window.
  3. Explicit time — set Scheduled Time + Timezone; all leads are scheduled at the same local time.

Trigger node — SuperHippo AI Voice Agents Trigger

Starts a workflow when the platform reports a call event. The output is the call object from the event payload (call_id, summary, call_outcome, call_status, duration, action_items, metadata.lead_id, …).

Setup:

  1. Add the trigger node and select the SuperHippo AI Voice Agents API credential.
  2. Pick an Event (default call.ended).
  3. Activate the workflow — the node registers its webhook URL with the platform automatically via POST /api/custom-webhook, and removes it again when the workflow is deactivated.

Only call.ended currently fires from the backend. call.started, call.joined, and call.billed are listed for forward-compatibility but are not emitted yet.

Example workflow

A common pattern — call every new lead and store the summary:

  1. SuperHippo AI Voice Agents → Create Lead and Call — create the lead and start the call.
  2. SuperHippo AI Voice Agents Trigger → wait for call.ended.
  3. SuperHippo AI Voice Agents → Get Call Summary — using {{ $json.call_id }} from the trigger.
  4. Send the summary to Slack, a CRM, or a spreadsheet.

Compatibility

  • Requires n8n with community nodes enabled.
  • No external runtime dependencies.

Resources

Maintainers

Maintained by Jungleworks. SuperHippo is a Jungleworks product, which is why the npm scope (@superhippo) and the GitHub organization (Jungle-Works) differ.

License

MIT

Discussion