Hydra logoHydra · Hydra Support

Configuration

API & Integrations

Overview of Hydra's API surface — REST, MCP, and webhooks — and where to go for the deep guide on each one.

API & Integrations

Hydra exposes three programmatic surfaces, each with its own dedicated guide. This page is the map.

REST API

A versioned HTTP API at /api/v1/* for reading and writing leads, contacts, accounts, conversations, and tickets. Bearer-token auth, scope-gated, rate-limited. Best fit for Zapier, n8n, custom server-side integrations, or anywhere you want straightforward request/response semantics.

See Public REST API for endpoints, scopes, pagination, error shapes, and rate-limit headers.

MCP server

Hydra ships an official Model Context Protocol server at https://mcp.hydra-help.com and via the @hydra-help/mcp npm package. 57 tools spanning support, CRM, automation, and analytics — read tools execute immediately, write tools surface a confirm-before-execute preview to block prompt injection. Best fit for Claude Desktop, Claude Code, Cursor, or any MCP-aware AI client that should operate your workspace conversationally.

See Connect Claude Desktop for the install + first-run walkthrough, and API Keys for minting, scoping, and revoking the keys both REST and MCP authenticate with.

Webhooks

Subscribe an HTTPS endpoint to Hydra events (ticket.created, account.health_score_changed, etc.). Hydra POSTs a signed JSON envelope every time the event fires, with retries on non-2xx responses and a per-subscription failure log. Best fit for real-time syncing into Zapier / n8n / a custom system without polling.

See Webhooks for the event catalog, signing scheme, retry policy, and delivery guarantees.

Inbound adapters

Inbound adapters are the inverse of webhooks: external systems POST events into Hydra to trigger your deployed Flows. Each adapter has its own URL with a path-embedded secret, so no auth header is needed.

Creating an adapter

  1. Go to Settings → Inbound Adapters.
  2. Click New Adapter.
  3. Give it a name and select the external event type.
  4. Map the external event to a Hydra trigger event.
  5. Copy the generated webhook URL — keep it private.

POST to that URL with your event payload. The adapter maps the payload to the appropriate Hydra event and fires any deployed Flows that match.

Monitoring

Each adapter shows a count of events received. If expected events aren't triggering Flows, confirm the Flow is deployed (not just in testing) and that the adapter's event mapping points at the right trigger.

Bidirectional email on tickets

Hydra threads customer email replies back into the originating ticket via a [Ticket #xxxxxxxx] reference tag in the subject line. When the customer replies, Hydra matches the tag, appends the reply to the ticket thread, and re-opens the ticket if it had been in Waiting status.

See Email Channels for the channel-side setup and Custom email domains for verifying your own sender domain.