Documentation
Notable changes to the Needle Agents REST API and MCP server.
One inbox for your whole team's conversations, built privacy-first.

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.
See Who can do what.
See Campaigns and List drafts.
See Who sees an event.
actorUserId, actorName): sends, approvals, campaign changes, and access changes.See Events.
Connect sender accounts without adding their owners to your Needle workspace.

Agencies run outreach from their clients' LinkedIn and Instagram accounts. Until now, the client had to join your workspace or share their password with you. With connect links, you send a link and the client signs in on their own. They don't need a Needle account, and their password never goes through you.
Receive every outbound event at your own URL as it happens.

/api/v1/webhooks, or with the webhook MCP tools.See Webhooks.
Introducing the Needle outbound engine for agents to run multi-channel campaigns.

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.
/api/v1./mcp/v1.Search documentation, API reference, and MCP tools
We use cookies to enhance your experience on Needle and keep your data secure. Privacy Policy