Prospection · send_linkedin_message
Message LinkedIn
Envoie un message ou une invitation LinkedIn (Unipile ou Chrome de l'utilisateur).
- Prix
- inclus
- Prérequis
- LinkedIn (Unipile) ou LinkedIn (Chrome)
- à brancher dans Paramètres → Intégrations
- Validation humaine
- Oui, par défaut
- écriture vers l'extérieur : un humain valide
Entrée
| Champ | Type | Description |
|---|---|---|
| messages | array | Batch send: the FULL list of LinkedIn messages/invites to send in one call (preferred whenever there is more than one recipient). Each item takes the same fields as a single message. When provided, the top-level single-message fields are ignored. |
| linkedinUrl | string | Recipient's full LinkedIn profile URL (e.g. https://www.linkedin.com/in/john-doe). Optional in browser mode when recipientName is given: the user's Chrome finds the profile itself — NEVER search LinkedIn with the browser tools. |
| message * | string | Personalised message text. Max 300 chars for connection requests. Use first name and company name. |
| type | message | connection_request | auto | Default "auto": the sender checks the profile — connected → direct message, otherwise invitation with the text as note. Set "message" or "connection_request" only when the user said which one. Never ask the user. |
| recipientName | string | Recipient's full name (e.g. 'Jean Dupont'). Required when linkedinUrl is omitted. |
| accountId | string | Unipile account ID for the LinkedIn account to use (auto-detected if not provided) |
Appeler cet outil
Via l'API HTTP, ou depuis le serveur MCP avec le méta-outil run.
curl https://api.ezyagents.fr/gateway/v1/run \
-H "Authorization: Bearer ezk_…" -H "Content-Type: application/json" \
-d '{"tool":"send_linkedin_message","input":{"messages":[],"linkedinUrl":"…","message":"…","type":"message"}}'$
run({ "tool": "send_linkedin_message", "input": {"messages":[],"linkedinUrl":"…","message":"…","type":"message"} })