Documentation

Changelog

Notable changes to the Needle Agents REST API and MCP server.

One inbox for your whole team's conversations, built privacy-first.

Unified Smart Inbox

Teams and agencies can now work leads together across many sender accounts without anyone's personal messages leaving their hands. Your team sees conversations with your leads from Needle's first contact onward. Everything before that, and every chat with people who aren't leads, stays with the account's owner.

Account access

  • Whoever connects an account owns it. Choose Manage access to share it with the whole workspace or only with chosen members.
  • Only members with access can run campaigns from the account, send as it, and read its lead conversations.
  • Remove someone's access and their campaigns on that account pause.

See Who can do what.

Draft approvals

  • A campaign step can hold the drafted message until someone reviews it.
  • Members with access to the account see those drafts in the inbox and approve them there. The approval is logged as an event with the member who approved it.

See Campaigns and List drafts.

Event visibility

  • Events that show what an account said or did are only visible to members with access, in the app, the API, and webhooks.

See Who sees an event.

Accountability

  • Every action on Needle is logged as an event with the member who did it (actorUserId, actorName): sends, approvals, campaign changes, and access changes.
  • Filter events by member on the events page or with Search events.

See Events.

Receive every outbound event at your own URL as it happens.

Webhooks

  • Add up to 5 webhooks per workspace in Settings, with /api/v1/webhooks, or with the webhook MCP tools.
  • Each request is signed with the webhook's secret, following Standard Webhooks.
  • Failed events are tried again 10 minutes and 1 hour after the first try.

See Webhooks.

Introducing the Needle outbound engine for agents to run multi-channel campaigns.

Agent-native Outbound Engine

Agents should be able to run outbound without wiring five tools together. This release is that engine: source people, run LinkedIn and Instagram campaigns, and call the same work from any agent over API or MCP.

Sends stay on the rails these channels need: per-account cadence, suppressions for people and companies you should not contact, and API keys bound to one user and one workspace.

Leads

  • Build lead lists from LinkedIn and the Places API.

Campaigns

  • Run multi-channel, multi-account outreach on LinkedIn and Instagram.

API

  • REST API at /api/v1.
  • MCP server at /mcp/v1.
  • Works with Claude Code, Cowork, Codex, Cursor, Hermes, or any other agent.

Search docs

Search documentation, API reference, and MCP tools

We use cookies to enhance your experience on Needle and keep your data secure. Privacy Policy