HeyLead — AI agent for LinkedIn outreach

Switch the active LinkedIn account, unlink it, or connect an email account. Which account is active decides who outreach is sent as. Listing them is the accounts tool. Args: action: "switch", "switch_to", "unlink", "connect_email" or "refresh_tier". account_id: The account id (switch_to).

List the LinkedIn accounts connected to this HeyLead. Changes nothing. Args: action: "list" (switching, unlinking and connecting email are the account tool).

Campaign analytics — reports, comparisons, and exports. Hosted accounts get a dashboard link and a snapshot card; relay the link, because some clients show the image only to the model. Args: action: What to do: "report" — Detailed analytics with outcomes, conversion rates, stale leads "compare" — Compare 2+ campaigns side by side "export" — Export campaign results as table, CSV, or JSON campaign_id: Which campaign. Uses active if empty. campaign_ids: Comma-separated IDs (for 'compare'). Compares all if empty. format: Output format for 'export': 'table', 'csv', or 'json'.

Reply in a LinkedIn conversation, or approve or discard a drafted reply. "reply" and "approve_draft" SEND a LinkedIn message and cannot be undone. Reading the inbox is the inbox tool. Args: action: "reply", "approve_draft" or "discard_draft". chat_id: Which conversation, or which draft. text: What to send, or an edited version of the draft.

Book a meeting on your Google Calendar and invite a prospect. Use this when a reply agrees to a call. Creates the event on the calendar you connected, attaches a Google Meet link, and emails the attendee an invitation. Args: attendee_email: Who to invite — the prospect who replied. start: When it starts, ISO 8601, e.g. 2026-09-01T10:00:00. duration_minutes: How long the meeting runs. Defaults to 30. summary: Event title. Defaults to naming the attendee. description: Optional agenda or notes included in the invitation.

Launch, pause, resume, archive, delete or emergency-stop a campaign. Every action here changes what happens next. Watching one run, or reading its history, is campaign_status. Args: action: "launch", "pause", "resume", "archive", "delete", "emergency_stop", "retry_failed", "repair_queue" or "clear_coordinator_hold". campaign_id: Which campaign. Uses the active one if empty. confirm: Required by the actions that destroy work.

Watch a campaign run, show its plan, or read its status history. Changes nothing. Args: action: "monitor" (live progress; a draft is started with campaign(action='launch')), "plan" (what happens after launch, step by step: finding, warm-up, invitations, opening message, follow-ups, replies, leads) or "status_history". campaign_id: Which campaign. Uses the active one if empty.

Read new LinkedIn replies and record what they mean. Fetches new messages, classifies each reply (positive, negative, question) and lists the people worth answering first. It sends nothing, but it does write: it marks an invitation accepted once the person answers or connects, moves an outreach to replied, stores the messages, and sets opted-out when someone asks not to be contacted, which stops all future outreach to them. It is the only path that notices an accepted invitation, so follow-ups depend on it having run.

Search, browse and read your contacts, and export them. Changes nothing. Tagging, noting, re-staging and linking are update_contact. Args: action: "list", "search", "view", "stats", "export", "linkedin_search" or "my_connections". query: Search text for "search", "linkedin_search" and "my_connections". For "linkedin_search" the query is passed to LinkedIn as KEYWORDS, matched literally — a company name, a job title, a person's name, or a combination such as 'Acme Corp CTO' or 'Jane Doe'. A natural-language question ('who is the CTO of Acme?') is sent through unchanged and usually comes back empty, so prefer keywords. Nothing is filtered out locally. An empty result and a failed search are reported in different words, so a "no matches" line means LinkedIn really returned nobody rather than "the search broke". Results are capped at 25 per call because every result costs a profile fetch and a LinkedIn read. contact_id: Which contact (view). lifecycle_stage: Filter by stage. min_fit_score: Only those scoring at least this. limit: How many. format: "table", "csv" or "json" (export). campaign_id: Filter by campaign. connected_since: Only those connected on or after this date. connected_before: Only those connected before this date.

Create a LinkedIn outreach campaign from a natural language description. Finds people on LinkedIn who match the description and saves a draft; nothing is sent until campaign(action='launch'). Use it for sales prospecting, recruiting and candidate sourcing, research and user-interview recruitment, job-search networking, investor and partner outreach, vendor scouting and event invitations. Reaching people you can already name — an article author, a warm intro, a speaker, one founder a customer mentioned — is the `people` argument: pass their profile URLs and the campaign is seeded from exactly them, with no LinkedIn search. Everything else is unchanged: draft until launch, rate limits, sending window, opt-outs. Describe who you need to reach and HeyLead finds them on LinkedIn: customers (lead generation, B2B prospecting, cold outreach), candidates (recruiting and sourcing), hiring managers and referrals (job search), investors and partners, vendors, and user-interview or research participants. On first campaign, project_brief is asked explicitly, in the goal's words (see project_brief below) — a homepage alone is not enough. Args: target_description: Who to target (e.g., "CTOs at fintech startups", "freelance UX designers in London", "yoga studio owners in California") campaign_name: Optional name for the campaign. icp_id: Optional ID of a saved ICP from generate_icp. If provided, uses the saved ICP's enriched LinkedIn codes for precise targeting instead of generating a new one. company_context: Optional. Your website URL or 1-2 sentences about your product/company. Copied into project_brief when project_brief is omitted. project_brief: Optional. Full project paste the model sees, in the goal's words. sell: what you offer and who it is for. job_search: the role, the kind of company, what you bring. hire: the role, who fits it, what it offers. partner: what you want from a partner, what yo…

Change one running or drafted campaign's settings. Pass only what you want to change; every field left empty keeps its current value. Use it to rename a campaign, give it a booking link, feed it context that makes the messages more specific (offerings, case studies, project brief), say who it is for (campaign_intent, campaign_type), or set the limits it sends under (volume, caps, follow-ups, business hours). It edits settings only: it sends nothing and adds no prospects. A change applies to the messages written from now on, not to ones already sent. Use create_campaign for a new campaign, and campaign(action=...) to launch, pause or stop one. Args: campaign_id: Which campaign to edit. Edits the first active campaign if empty. name: New campaign name. Leave empty to keep current name. mode: Only "autopilot" supported (copilot mode was removed). Whether messages wait for a person is the workspace's approval mode: scheduler(action="approval_mode"). booking_link_page_ok: Explicitly keep a website page as the booking link. booking_link: Calendar/booking URL (e.g., "https://cal.com/you/15min"). Used in reply_to_prospect() for positive replies to suggest meetings. offerings: What you offer (products, services, value props). Used in follow-up messages. case_studies: Brief case studies or success stories. Used for social proof in messages. social_proofs: Social proof (logos, metrics, testimonials). Used in follow-up messages. campaign_preferences: Custom messaging preferences (tone, topics to avoid, etc.). campaign_intent: Message stance: "sell", "buy", "partner", "recruit" or "research". campaign_type: Prompt family: "outbound" (default) or "job_search". job_search replaces the intent-specific invitation note and first DM with ones that may name the company and the role, use one credible proof point at most and never list a CV. InMail is not routed by this switch, and cam…

Generate a rich Ideal Customer Profile with buyer personas. The same profile describes whoever the user needs to reach: buyers, candidates to recruit, research or user-interview participants, hiring managers for a job search, investors or partners. Pass goal= so the profile is of the right people. Creates 2-4 ICP personas with pain points, fears, barriers, LinkedIn search parameters, and confidence scores. The result is saved and can be reused with create_campaign(icp_id=...). Supports target audience analysis, customer segmentation, buyer persona creation, ideal customer profiling, and B2B market research. Args: target_description: Who to target (e.g., "CTOs at fintech startups", "freelance UX designers in London", "yoga studio owners in California") company_context: Optional URL or text about your company/product. Providing this makes the ICP more precise and evidence-backed. focus_query: Optional focus (e.g., "enterprise segment only", "focus on pain points around compliance") decision_makers_only: Keep every persona's seniority to people who hold budget authority — owner, cxo, vp, director. Default True. Pass False only when the target really is individual contributors (developers, designers, analysts); the ICP then keeps whatever levels the description implies. Applies only to sell, partner and buy; managers hire, so a job search keeps them. goal: What the campaign is for, which decides whose profile this is: "sell" (customers, the default), "job_search" (the people who hire for or refer into the role), "hire" (candidates), "partner" (who can sign a partnership or invest), "buy" (vendors), "research" (participants). Always pass it; a job search with goal="sell" produces peers, not hiring managers.

Read any conversation in your LinkedIn inbox, and the drafted replies. Replying, approving a draft and discarding one are answer_inbox. Args: action: "list", "read", "open_file" (save the files a person sent, to read them) or "comment_drafts". chat_id: Which conversation. name: Find the conversation by the person's name. limit: How many to show.

Skip a prospect, close one with an outcome, or dismiss it. Someone who is not a fit is skipped, not closed: skip leaves them out of this campaign and records nothing else. Close records a result and needs an outcome; won and lost are for people HeyLead has written to. Closing with outcome="opt_out" stops all future contact with that person. Reading a prospect is prospect_view. Args: action: "skip", "close" or "dismiss". outreach_id: Which outreach. campaign_id: Which campaign. Uses the active one if empty. outcome: "won", "lost" or "opt_out". Required for close; there is no default. reason: Why, recorded with the outcome. meeting_link: The booked meeting, recorded with a won outcome. confirm: Required where the action cannot be undone. reason_code: Why, for skip and close: "not_a_fit", "negative_reply", "asked_to_stop", "handled_elsewhere" or "other". reason_note: A free note alongside the code. deal_value: What the won deal is worth (close with outcome="won"). deal_currency: Three-letter code, e.g. USD. Defaults to the last deal's.

Read the message thread with one prospect, or their timeline. Changes nothing. Args: action: "conversation" or "timeline". outreach_id: Which outreach. campaign_id: Which campaign. Uses the active one if empty.

Turn the autonomous scheduler on or off, or change how it runs. Off means nothing sends until it is on again. Reading its state, logs, activity or diagnostics is scheduler_status. Args: action: "toggle", "observe", "always_on", "backfill_cloud", "send_from" or "report". enabled: True to enable, False to disable (toggle, report). cloud: Act on the hosted scheduler rather than this machine's. host: "cloud" (send_from); a hosted account never sends from here. hours: The reporting interval (report). campaign_id: Which campaign (report).

Read the scheduler: status, logs, activity, diagnostics or the daily report. Args: action: "status", "logs", "activity" or "diagnostics". The daily report is the scheduler tool: it switches reporting on and off. cloud: Read the hosted scheduler rather than this machine's. hours: Lookback window in hours. event_type: Filter the log by event type. campaign_id: Filter by campaign.

Send follow-ups, replies, or InMail to prospects. Args: action: What to do: "followup" — Send a follow-up DM after connection accepted "reply" — Reply to a prospect who has messaged you "delete" — Delete a recently sent message (within 60 min on LinkedIn) "inmail" — Send an InMail to a NON-connection. Preconditions (each fails closed with no send): prospect has a provider_id; they are NOT a 1st-degree connection (use followup/DM for those); no InMail already sent on this outreach; InMail credits remaining > 0. A pending invitation to the same person is allowed — that is the escalation path. Requires outreach_id. campaign_id: Which campaign to send from. Uses active if empty. outreach_id: Specific outreach to target. Required for inmail. format: 'text'. For followup/reply. text: For followup/reply on a hosted account: the message to send, required; the cloud sends it as is in the outreach's LinkedIn chat (the same route as answer_inbox reply). Without a backend the message is generated. For delete: optionally pass a Unipile message_id directly.

Set up HeyLead by connecting your LinkedIn account and analyzing your writing style. REQUIRED for first-time users — must be called before any other tool. This analyzes your LinkedIn profile, posts, and writing style to create a "voice signature" so every outreach message sounds like YOU, not a bot. Handles LinkedIn automation setup, SDR onboarding, account connection, and voice analysis for personalized outreach. First-time setup: sign in at https://heylead.dev/auth/login-url, click 'Connect' on the LinkedIn row, copy the setup message ('Copy' under 'Get Started'), then call this tool with the eyJ... token from it as backend_jwt. No API keys needed on the hosted backend. Args: llm_api_key: Optional — only if you want to use your own AI key instead of the backend's. llm_provider: Which AI to use if providing your own key: "gemini", "claude", or "openai". backend_url: HeyLead Backend API URL. Leave empty — defaults to production server. backend_jwt: Your authentication token from HeyLead.

Show your outreach dashboard — campaigns, stats, hot leads, account health. The chat is the front door to your dashboard. View pipeline metrics, prospect funnel, engagement rates, and campaign performance. Ask "how's my outreach?" anytime. Hosted accounts get a dashboard link and a snapshot card; relay the link, because some clients show the image only to the model. Args: campaign_id: Show stats for a specific campaign. Shows all if empty.

Suggest the best next action for your outreach. Hosted accounts get a dashboard link and a snapshot card; relay the link, because some clients show the image only to the model. Analyzes all active campaigns and recommends what to do next, prioritized by impact: hot leads first, then pending approvals, follow-ups, engagement warm-ups, and new invitations. Args: campaign_id: Focus on a specific campaign. Analyzes all active if empty.

Change one contact: tag it, note it, move its stage, or link it to a campaign. Reading and searching contacts is the contacts tool. Args: action: "tag", "note", "stage", "link" or "enrich". contact_id: Which contact. lifecycle_stage: The stage to move it to. tag: The tag to add. note: The note to record. campaign_id: Which campaign (link). match: How to match when linking. dry_run: Show what would change without changing it.