Skip to main content
When released in your workspace, Send LinkedIn InMail (send-linkedin-inmail) can initiate a conversation in one selected Recruiter project. Use AI Chat or an authorized MCP app, including ChatGPT. The new project option is unavailable in Workflow Actions, Workflow Agents, Records columns and programs. Existing profile-based messaging keeps its supported surfaces. For example: “Send Alice in the Engineering project’s applicants an InMail about the role, from Sam’s Recruiter account.” Connie asks which account, project or person you mean when the selection is ambiguous. Select the connected account with connector-list-accounts, then use list-recruiter-projects and get-recruiter-project. Choose a saved candidate with list-recruiter-pipeline-candidates, or an applicant with list-recruiter-applicants and get-recruiter-applicant. Copy their full bindings into recruiterContext; candidate IDs, application IDs and User Profile IDs are different. Connie rechecks project access and the selected person’s relationship to that project before sending. Missing or restricted identity evidence stops the send. Through MCP, discover send-linkedin-inmail with search-tools and inspect its schema with get-tool. Keep an opaque account reference in the host envelope. For project initiation:
  • Set senderUrl to the exact connected account and apiType to recruiter.
  • Set messageMode to manual; supply the final message and subject.
  • Set recruiterContext.project to the complete {accountId,id,name} binding.
  • For a pipeline candidate, use recipient: {kind:"candidate",candidate:...} with the complete candidate returned by the pipeline reader. For an applicant, use recipient: {kind:"applicant",applicant:...} with the full applicant binding.
  • Include the sender’s signature inside recruiterContext.
Omit recipientUrl, attachment, prompt and template placeholders with this option. To personalize a project message, first draft its final text in Chat, then review and send that exact text. No provider token or credential is an input. This option does not email candidates, schedule follow-ups, change applicant decisions or perform bulk outreach. A working Recruiter seat and the intended selected contract are required; Classic or Sales Navigator alone does not qualify. Current project permissions, InMail eligibility, daily account limits and warm-up still apply. LinkedIn’s InMail credits are separate from Connie credits. An unavailable balance is unknown, not zero; Open Profile does not guarantee free delivery. Chat’s approval shows the exact account, project, recipient, subject, signature and message. Cancel or Escape sends nothing. An authenticated MCP invocation uses the host’s existing explicit-call authorization. Connie never switches to a personal inbox, another account, another project or another recipient. Accepted means LinkedIn acknowledged the message; it does not confirm delivery. Refused means the provider rejected the attempt. Uncertain means the message may have been accepted: inspect that exact project’s conversation before deciding what to do, and never automatically resend. Accepted, refused and uncertain receipts suppress matching replays for the existing 24-hour receipt period; changing invocation keys does not authorize a duplicate. Recovered receipts and definite refusals report zero actual Connie tool credits. Configured tool pricing applies to the first accepted send. Uncertain outcomes use the existing failure settlement; no completed send charge is invented.