Simple LinkedIn Sales navigator Lead list export avatar
Simple LinkedIn Sales navigator Lead list export

Deprecated

Pricing

$6.99/month + usage

Go to Store
Simple LinkedIn Sales navigator Lead list export

Simple LinkedIn Sales navigator Lead list export

Deprecated

Developed by

Andrew Koumoudjian

Andrew Koumoudjian

Maintained by Community

Extracts comprehensive information about leads (people) Captures detailed company/account information Exports all data to CSV format Handles pagination automatically

0.0 (0)

Pricing

$6.99/month + usage

0

Total users

7

Monthly users

7

Runs succeeded

>99%

Last modified

2 months ago

You can access the Simple LinkedIn Sales navigator Lead list export programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.

{
"mcpServers": {
"local-actors-mcp-server": {
"command": "npx",
"args": [
"-y",
"@apify/actors-mcp-server",
"--actors",
"andrewthecube/salesnav"
],
"env": {
"APIFY_TOKEN": "<YOUR_API_TOKEN>"
}
}
}
}

Configure MCP server with Simple LinkedIn Sales navigator Lead list export

You can interact with the MCP server via standard input/output - stdio (as shown above), which is ideal for local integrations and command-line tools such as the Claude desktop client, or you can interact with the server through Server-Sent Events (SSE) to send messages and receive responses, which looks as follows:

{
"mcpServers": {
"remote-actors-mcp-server": {
"type": "sse",
"url": "https://mcp.apify.com/sse?actors=andrewthecube/salesnav",
"headers": {
"Authorization": "Bearer <YOUR_API_TOKEN>"
}
}
}
}

You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other supported MCP client of your choice.

If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.