Integration

Reachkit integration

Reachkit is a cold email outreach platform. An agent can create, launch, pause and delete campaigns, write their sequence steps and A/B variants, set the sending schedule and options, attach sending inboxes, add and remove leads, read campaign analytics and inbox warmup stats, manage the blocklist, and read, label and answer unibox conversations (replies and new conversations send real emails). Connecting new inboxes is done in the Reachkit app. API access needs the Scale plan. Authentication is an API key created under Settings, Integrations, sent in the X-API-Key header.

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Reachkit

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Campaign, 5 operations

  • create_campaignCreate campaignPOSTAgents: ask firstCreates a campaign in draft status (nothing is sent) with an empty first step and variant. Then add steps, leads, inboxes and a schedule, and launch it with update_campaign status active.
  • delete_campaignDelete campaignDELETEAgents: ask firstPermanently deletes a campaign with its schedule, sequences, variants and leads, and cancels its queued sends. Cannot be undone.
  • get_campaignGet campaignGETAgents: ask firstReturns one campaign: name, status (draft, active, paused, completed), options, sending schedule, full stats with daily and per-step figures, and attached inboxes.
  • list_campaignsList campaignsGETAgents: ask firstLists the workspace's campaigns with status, options, schedule, headline stats and attached inboxes, paginated (page_size up to 100). For daily and per-step stats use get_campaign or get_campaign_analytics.
  • update_campaignUpdate campaignPATCHAgents: ask firstUpdates a campaign's name, options or status: status active LAUNCHES or resumes sending emails to its leads, paused stops it. Omitted fields keep their value; if one field is invalid nothing is saved.

Conversation, 4 operations

  • create_conversationCreate conversationPOSTAgents: ask firstSENDS an email: starts a new unibox conversation with to recipients, subject and content, from inbox_id (or the workspace's first active inbox when left out). Returns the conversation.
  • get_conversationGet conversationGETAgents: ask firstReturns one unibox conversation: label, positive flag, lead, unsent draft and its attachments, and every message (oldest first) with bodies, recipients and attachments. Personal data.
  • list_conversationsList conversationsGETAgents: ask firstLists unibox conversations with labels, positive flag, lead, draft and every message (oldest first), paginated (page_size up to 100, default 20), optionally searched or limited to the primary or others folder. Personal data.
  • update_conversationUpdate conversationPATCHAgents: ask firstChanges a conversation's label override, read state, unsent draft or draft attachments (nothing is sent). Send at least one field; omitted fields are unchanged.

Lead, 4 operations

  • create_leadCreate leadPOSTAgents: ask firstAdds a lead (email, names, merge-tag variables) to a campaign; in an active campaign the sequence starts emailing it. if_exists: fail (default), skip, or update (overwrites the existing lead).
  • delete_leadDelete leadDELETEAgents: ask firstDeletes a lead from a campaign (it is no longer emailed by the sequence).
  • get_leadGet leadGETAgents: ask firstReturns one lead of a campaign: email, names, status (uncontacted, contacted, replied), bounce and unsubscribe flags, detected email provider and merge-tag variables. Personal data.
  • list_leadsList leadsGETAgents: ask firstLists a campaign's leads: email, names, status (uncontacted, contacted, replied), bounce and unsubscribe flags, detected email provider and merge-tag variables, paginated. Personal data.

Sequence, 4 operations

  • create_sequence_stepCreate sequence stepPOSTAgents: ask firstAdds a step at the end of a campaign's sequence, with an empty variant A to fill with update_sequence_variant. delay_days (vendor default 3) is the wait before the next step.
  • delete_sequence_stepDelete sequence stepDELETEAgents: ask firstDeletes a sequence step and all its variants; later steps move up so step numbers stay contiguous.
  • list_sequencesList sequencesGETAgents: ask firstLists a campaign's sequence steps in order, each with delay_days (null on the last step) and its variants (letter, subject, HTML and text body, enabled).
  • update_sequence_stepUpdate sequence stepPATCHAgents: ask firstSets a sequence step's delay_days: the number of days to wait after this step before the next one is sent.

Blocklist, 3 operations

  • add_blocklist_entryAdd blocklist entryPOSTAgents: ask firstAdds one email or domain (value) or several (entries) to the workspace blocklist, so campaigns stop emailing them. Send exactly one of value or entries. The kind (email or domain) is inferred from the @.
  • delete_blocklist_entryDelete blocklist entryDELETEAgents: ask firstRemoves a blocklist entry, so campaigns can email that address or domain again. An automatic entry (unsubscribe, negative reply) can be removed only while its blocklist setting is off; otherwise 422.
  • list_blocklistList blocklistGETAgents: ask firstLists the workspace's blocklist entries (email or domain, source manual, unsubscribe or negative_reply), paginated, with an optional value search and sort.

Inbox, 3 operations

  • get_inboxGet inboxGETAgents: ask firstReturns one sending inbox with its settings, limits, connection status and the campaigns it is attached to.
  • list_inboxesList inboxesGETAgents: ask firstLists the workspace's sending inboxes: address, provider, connection status, sender names, reply-to, active and warmup flags, daily campaign and warmup limits and ramp settings, paginated.
  • update_inboxUpdate inboxPATCHAgents: ask firstChanges a sending inbox's settings: is_active false pauses its campaign sending, plus warmup, sender names, reply-to, daily limits and ramp-up. Omitted fields are unchanged.

Variant, 3 operations

  • create_sequence_variantCreate sequence variantPOSTAgents: ask firstAdds an A/B variant (subject, HTML body, enabled) to a sequence step. HTML is normalized, the unsubscribe link is kept and merge tags are validated (unbalanced braces return 422).
  • delete_sequence_variantDelete sequence variantDELETEAgents: ask firstDeletes a sequence variant. Refused (422) when it is the step's last enabled variant or once it has sent emails: then disable it with update_sequence_variant enabled false.
  • update_sequence_variantUpdate sequence variantPATCHAgents: ask firstUpdates a sequence variant's subject, HTML body or enabled flag; omitted fields are unchanged. The last enabled variant of a step cannot be disabled. Merge tags and spintax are supported.

Analytics, 1 operation

  • get_campaign_analyticsGet campaign analyticsGETAgents: ask firstReturns a campaign's analytics: progress, leads, sent, contacted, replies, positive replies, bounces and their rates, a 30-day daily series, and per-step and per-variant performance.

Attach, 1 operation

  • attach_campaign_inboxesAttach campaign inboxesPOSTAgents: ask firstAttaches sending inboxes to a campaign (idempotent) and returns the full set now attached. If any inbox id is unknown or from another workspace, nothing changes (404).

Attachment, 1 operation

  • download_conversation_attachmentDownload conversation attachmentGETAgents: ask firstDownloads one attachment of a conversation (from a sent message or the unsent draft) and returns the stored file. Get attachment ids from get_conversation.

Check, 1 operation

  • check_blocklistCheck blocklistGETAgents: ask firstChecks whether an email is blocked: true when it matches an email entry, a domain entry, or a parent domain entry (blocking acme.com also blocks its subdomains).

Detach, 1 operation

  • detach_campaign_inboxesDetach campaign inboxesPOSTAgents: ask firstDetaches sending inboxes from a campaign (idempotent) and returns the inboxes still attached. If any inbox id is unknown or from another workspace, nothing changes (404).

Reply, 1 operation

  • reply_to_conversationReply to conversationPOSTAgents: ask firstSENDS a reply email in a conversation, addressed to its lead. cc left out replies to everyone else in the thread; an empty list replies to the lead only. Staged draft attachments go out with it and the draft is cleared.

Schedule, 1 operation

  • update_campaign_scheduleUpdate campaign schedulePATCHAgents: ask firstUpdates a campaign's sending schedule: timezone, default daily window and per-day overrides or days off. Omitted fields are unchanged; times are 24-hour HH:MM rounded to the nearest 30 minutes (23:30 at most).

Stats, 1 operation

  • get_inbox_warmup_statsGet inbox warmup statsGETAgents: ask firstReturns an inbox's warmup statistics for the last 7 days: warmup emails sent and received, saved from spam, health score (0 to 100), ramp-up progress and a daily series.

Use Reachkit from Claude Code, Cursor or Codex

Connect Reachkit in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Reachkit 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 Reachkit

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Reachkit once

    Add your Reachkit 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.

Reachkit integration FAQ

What can you do with the Reachkit integration?

LiveContext exposes 34 operations on Reachkit, covering campaign, conversation, lead and sequence.

Popular integrations

Browse the whole catalog