Once your LinkedIn account is connected, you're ready to run something. How you do that depends on how you're using We-Link.
Using an AI assistant
If you're running We-Link from Claude, ChatGPT or another assistant, connect it first, then just ask in plain language.
Connect your assistant to We-Link. See We-Link MCP (AI assistants) and follow the guide for the assistant you use.
Ask for something simple to confirm it's working, for example:
Search LinkedIn for heads of RevOps at Series B SaaS companies in the US and summarize each one.
3. Your assistant runs the search and hands back a list. That's your first action done.
For more prompts to try, see Things to try with We-Link MCP, or browse real scenarios on the MCP use cases page.
Using the API
If you're building on the REST API, your first call needs three things: your API key, your API secret, and the account ID of the LinkedIn account you connected.
Remember that We-Link is asynchronous: a call returns a request ID straight away, and the result comes back over a webhook rather than in the immediate response. The API reference and the Quick Start walk through a first call end to end.
What to expect
Actions are paced. If something is queued rather than instant, that's normal, We-Link spreads work out to keep your account safe.
LinkedIn may ask you to verify. The first time an account acts, you might be asked for a code. That's expected, see When LinkedIn asks you to verify.
Every action uses credits. You start with 100 free trial credits, enough to test real actions before you commit. See How credits work with We-Link MCP.
Something not working? See Fixing common problems.