Integrations

Every LinkedIn action, as an endpoint.

MCP, a REST API and webhooks. Connections, messages, sequences and reply drafts, all callable by the agent you already run.

Read the docs

A native MCP server

Claude, Cursor, Codex, Clay, n8n, or an orchestrator you wrote yourself. Create and launch sequences, read threads, post drafts, move stages. It is first-party, so it moves when the product moves, and it speaks the same objects the interface does.

A REST API for everything else

The same surface over HTTP: sending, drafting, enrollment, stages, sequences. Feature parity on every plan, the Sandbox included, so nothing you write against the Sandbox breaks when you connect a real account.

Webhooks on every event

Every reply, draft and stage change fires a webhook. Stage a thread as Booked and it lands in your CRM, Clay table or n8n flow before you switch tabs.

There is a pipeline here too: a kanban board beside the master inbox, and plenty of teams work their deals in it. It just does not ask to be your system of record.

Discover more of Sprootal.

Master inboxYour agent opens the conversation. You carry itQueue engineOne call in. Weeks of safe outreach out

Connect an agent and put your outbound in motion.

Sign up

Talk to a founder

Thirty minutes with one of the two people who build this.

Opening the calendar