Integration

Hedy integration

Hedy is an AI meeting assistant that records and transcribes conversations in its app. Read your meeting sessions with their transcript, recap and meeting minutes, list highlights and to-dos (and mark a to-do done or change its due date), organize sessions into topics, manage reusable session contexts that guide how Hedy analyzes meetings, read or replace the custom vocabulary, and create, list or delete webhook subscriptions. Sessions cannot be started or stopped through the API (that happens in the Hedy app), and the Zapier flat-array response format is not exposed. Authentication is a Hedy API key (Pro plan, generated in the app's Account Settings) sent as a Bearer token, plus the API host of your account's region: api.hedy.bot for US accounts or eu-api.hedy.bot for EU accounts.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Hedy.Built from the 27 Hedy tools below, on the connection you add once.

What you can do with Hedy

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Context, 5 operations

  • create_contextCreate contextPOSTCreates a new session context. Free tier users are limited to 1 context. If isDefault is true, any existing default context will be unset.
  • delete_contextDelete contextDELETEDeletes a session context. If the deleted context was the default, the most recently updated remaining context will be promoted to default.
  • get_contextGet contextGETReturns a specific session context by its identifier.
  • list_contextsList contextsGETReturns all saved session contexts for the authenticated user, ordered by most recently updated.
  • update_contextUpdate contextPATCHUpdates an existing session context. Only provided fields will be modified. If isDefault is set to true, any existing default will be unset.

Topic, 5 operations

  • create_topicCreate topicPOSTCreates a new topic for organizing meeting sessions. Optionally include custom instructions (topicContext) that will be used for sessions under this topic.
  • delete_topicDelete topicDELETEDeletes a topic and unlinks all associated sessions. Sessions are NOT deleted, only disassociated from the topic (their topicId is set to null).
  • get_topicGet topicGETReturns detailed information about a specific topic, including its topicContext if set and topic insights (sessionCount, dominantSessionType, overview, lastSessionDate).
  • list_topicsList topicsGETReturns a list of all topics for the authenticated user, ordered by last update time (descending). Each topic includes insights such as sessionCount, dominantSessionType, and overview when available.
  • update_topicUpdate topicPATCHUpdates an existing topic. Only provided fields will be modified. Set topicContext to null to clear it.

Session, 4 operations

  • get_sessionGet sessionGETReturns detailed information about a specific meeting session, including transcript, conversations, and meeting minutes.
  • list_sessionsList sessionsGETReturns a list of meeting sessions. Sessions are sorted by start time, newest first.
  • list_topic_sessionsList topic sessionsGETReturns a page of sessions associated with a specific topic, ordered by start time (descending); use the `startAfter` cursor to retrieve subsequent pages. Each session includes its own details and the parent topic's information.
  • update_sessionUpdate sessionPATCHMoves a cloud-synced session into a topic, or removes it from its topic when topicId is null or an empty string. Repeating the current assignment succeeds without a change.

Todo, 4 operations

  • get_todoGet todoGETReturns details for a specific user to-do item within a session, identified by its unique ID.
  • list_session_todosList session todosGETReturns the to-do items Hedy extracted for one session, with their text, due date, completion state and the session's topic.
  • list_todosList todosGETRetrieves a list of all to-do items across all sessions for the authenticated user. Results are eventually consistent: session changes normally appear within seconds, while failed updates are repaired by a rebuild after 7 days.
  • update_todoUpdate todoPATCHUpdates completion, due date, or both for a stable-id to-do item without replacing the session's to-do array. An empty dueDate clears the due date.

Highlight, 3 operations

  • get_highlightGet highlightGETReturns detailed information about a specific highlight, including the original quote, cleaned quote, and AI insights.
  • list_highlightsList highlightsGETReturns a list of highlights. Highlights are sorted by timestamp, newest first.
  • list_session_highlightsList session highlightsGETReturns every highlight of one session: the quote as spoken and cleaned up, its main idea, the AI insight and its time offset in the session.

Webhook, 3 operations

  • create_webhookCreate webhookPOSTSubscribes an HTTPS URL to Hedy events (session.created, session.ended, session.exported, highlight.created, todo.exported, suggestion.created). At most 50 webhooks per account. The signing secret is not passed back.
  • delete_webhookDelete webhookDELETEDeletes a webhook subscription.
  • list_webhooksList webhooksGETReturns a list of configured webhooks for the authenticated user.

Vocabulary, 2 operations

  • list_vocabularyList vocabularyGETReturns the complete account custom vocabulary list and whether vocabulary matching is enabled.
  • update_vocabularyUpdate vocabularyPUTReplaces the complete account custom vocabulary list. Any stored terms omitted from the supplied list are removed; omit enabled to preserve its current value.

Me, 1 operation

  • get_meGet meGETReturns the profile of the user the API key belongs to.

Use Hedy from Claude Code, Cursor or Codex

Connect Hedy in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Hedy operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Hedy

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Hedy once

    Add your Hedy connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Hedy integration FAQ

What can you do with the Hedy integration?

LiveContext exposes 27 operations on Hedy, covering context, topic, session and todo.

Popular integrations

Browse the whole catalog