analytics_campaign_performance
ChatGPTGet a campaign's performance: raw volume counts plus derived acceptance, reply, and conversion rates, with the stats_datetime freshness timestamp. Rates are computed from the cached stats (which can lag live state). To resolve inputs from names: find_campaign (campaign_instance_id).
analytics_compare_campaigns
ChatGPTRank an account's campaigns by a metric (acceptance_rate, reply_rate, or conversion_rate), best first. Rates are derived from cached stats. To resolve inputs from names: find_linkedin_account (li_account_id).
analytics_funnel
ChatGPTGet a campaign's per-step funnel (lead counts per node) to see drop-off. May be empty where step counts have not been computed. To resolve inputs from names: find_campaign (campaign_instance_id).
analytics_kpi_trend
ChatGPTGet the account KPI trend timeseries for a metric type over an optional date range (start_date/end_date as YYYY-MM-DD). Data comes from the daily KPI rollup. To resolve inputs from names: find_linkedin_account (li_account_id). To pick a valid metric_type: analytics_list_kpi_metrics.
analytics_leads_behind_metric
ChatGPTList the leads behind a campaign metric (metric one of: replied, interested, not_interested, maybe). Drill-down into the same lead-level state the other MCPs read. To resolve inputs from names: find_campaign (campaign_instance_id).
analytics_list_kpi_metrics
ChatGPTList every KPI metric_type accepted by analytics_kpi_trend, with its human label and category (connection_metrics, messaging_metrics, or engagement_metrics). Call this to pick a valid metric_type before requesting a trend.
audience_add_leads
ChatGPTAdd leads to a custom lead list inside the user's outreach account by LinkedIn profile_link, each with optional placeholder key/values (enrichment on add). Existing messengers are reused (dedup via profile_link); no duplicates. Enforces the 5000-lead list limit. If the list is auto-assigned to campaigns, new leads flow into them automatically. Sending happens later under the user's limits in the outreach platform. Input: leads = [{profile_link, placeholders?}]. To resolve inputs from names: find_custom_list (list_id), find_lead (profile_link).
audience_configure_autoassign
ChatGPTConfigure auto-assign on a lead list of any type: link it to a campaign so leads added to the list are automatically assigned to that campaign. The campaign must be on the same LinkedIn account. Multiple lists can feed the same campaign. To resolve inputs from names: find_custom_list (list_id), find_campaign (campaign_instance_id).
audience_create_list
ChatGPTCreate a custom lead list (MCP-managed) for a LinkedIn account. The list can later be assigned to campaigns like any other lead list. Optionally record the selection criteria the list represents (e.g. {"title": "QA Lead", "city": "Lviv"}) so later audits can see why the list exists; the criteria are stored on the list and returned by the audience read tools. To resolve inputs from names: find_linkedin_account (li_account_id).
audience_delete_list
ChatGPTDelete a custom lead list. Only custom (MCP-managed) lead lists can be deleted. To resolve inputs from names: find_custom_list (list_id).
audience_get_list
ChatGPTGet details of a custom lead list (name, lead count, created date, assigned campaigns). If you only have a list name, call find_custom_list first to resolve the list_id.
audience_list_leads
ChatGPTList the leads in a lead list of any type (custom, LinkedIn search, Sales Nav, CSV import, etc.). Returns the same contact + messenger + placeholder payload as the lead-read tools. To resolve inputs from names: find_custom_list (list_id).
audience_remove_leads
ChatGPTRemove leads (by profile_link) from a custom lead list. To resolve inputs from names: find_custom_list (list_id), find_lead (profile_link).
audience_rename_list
ChatGPTRename a lead list of any type. To resolve inputs from names: find_custom_list (list_id).
builder_action_types
ChatGPTList the action_type codes the builder supports, each with its human label (e.g. 1 = Message, 9 = Condition). Call this to pick a valid action_type for builder_add_node.
builder_condition_types
ChatGPTList the condition_type codes with their human labels (e.g. 1 = Condition connected, 6 = Condition open inmail, 8 = Condition email exists). A condition_type qualifies a Condition node (action_type 9); it selects which branch check the node performs. Call this to pick a valid condition_type when adding a Condition node with builder_add_node.
builder_create
ChatGPTCreate a Builder (advanced flow) campaign draft (inactive) for a LinkedIn account. Optionally start from an advanced template (template_id -- call find_campaign_template to resolve it from a name) and/or set a campaign goal ({target, value_proposition, goal}). The draft is created inactive; a human must review and activate it; nothing is sent until activation. To resolve inputs from names: find_linkedin_account (li_account_id).
builder_get
ChatGPTGet a Builder (advanced flow) campaign's current flow: campaign goal, entry node, all nodes with their wiring and copy, plus validation (entry set, node-count limits). If you only have a campaign name, call find_campaign first to resolve the campaign_instance_id. RETURNS an object: {campaign_instance_id, name, active, li_account_id, campaign_goal ({target, value_proposition, goal}, or null if unset), first_action_id (the entry node's id), nodes (the step list), validation ({valid, issues, node_count})}. HOW TO READ EACH NODE: 'id' is the node's handle used in the wiring fields. 'action_type' is the human label and 'action_type_code' is the raw int (matches builder_action_types), e.g. 1 = Message, 9 = Condition. 'task_type' + 'task_type_label' are the resolved runtime queue task (matches builder_task_types), which disambiguates a Message into its concrete step (e.g. 'cr' = Connection Request, 'oi' = Open InMail, 'im' = Paid InMail, 'mr' = Mobile Connection Request, 'm' = Follow-Up Message); null for Signal nodes. 'condition_type_code' + 'condition_type_label' are set ONLY on Condition nodes (action_type_code 9) and tell you which branch check it performs (matches builder_condition_types, e.g. 1 = Condition connected, 8 = Condition email exists); both are null on non-condition nodes. A Message node (action_type_code 1) is further specialised by its boolean flags: 'flag_connector' = Connection Request, 'flag_mobile' = Mobile Connection Request, 'flag_open_inmail' = Open InMail, 'flag_inmail' = Paid InMail; a Message with none of these set is a Follow-Up Message. 'message_subtype' gives that specific name directly (null on non-message nodes). 'config' holds the node's type-specific configuration (null when a node has none, e.g. Visit/Follow): Condition -> {condition_type, condition_type_label, check_time_delta, check_time_delta_label} (the branch check plus how long it polls before the not-met branch; see builder_time_deltas). Signal (action_type_code 21) -> {rule, company_url, post_urls, post_engagement_criteria, keywords}: 'rule' is a boolean expression over signal-type codes (1 profile-visited, 2 company-visited, 3 post-engagement) joined by and/or/not; company_url applies to company signals, post_urls/post_engagement_criteria/keywords to post-engagement signals. Custom Condition (10) -> {branches:[{position, rules, following_action_id}]}: each branch's 'rules' maps checks to 0/1 (checks within a branch are ANDed), branches are evaluated in 'position' order, and 'following_action_id' is that branch's destination. ICP Filter (19) -> {branches:[{position, criteria, no_path, following_action_id}]}: 'criteria' filters on company/role attributes (location/industry/company_size/job_title and excl_* variants), 'no_path' marks the catch-all branch, 'following_action_id' the destination. Webhook (13) -> {url} (destination; credentials and the query string are redacted). Integration (18) -> {integration_type, integration_type_label, integration_source} (the selected tool and its destination, e.g. the Smartlead campaign). Transfer (20) -> {campaign_instance_id, campaign_instance_name} (the target campaign). Add Tags (17) -> {tags:[{id, name}]}. Event Invite (12) -> {event:{id, name, entity_urn, url}} (or {event:null} if unset). Company Follow Invite (15) -> {company_url} (the target company page). 'time_delta' is the raw delay code and 'time_delta_label' its human label (matches builder_time_deltas), e.g. 'c_a01' immediately, 'd01' 1 day. 'body' is the message copy ('subject' the email/InMail subject line); when 'is_using_ai' is true the body/subject are AI-generated per lead at send time from 'ai_prompt'. WIRING: 'following_action_id' is the id of the next step; on a Condition node it is the condition-met (true) branch, while 'no_following_action_id' is the not-met (false) branch. Either may be null where a branch ends. For the full step semantics and sequencing rules, read the MCP resource guide://builder/actions.
builder_prerequisites
ChatGPTList the required-upstream prerequisites per builder node. For each node you can add (an action keyed by its queue task_type, or a condition keyed by its condition_type), 'requires_upstream' is the ordered list of conditions/actions that must already exist above it on the flow -- the builder auto-prepends any that are missing. Condition prerequisites carry an 'expected' branch (true = condition-met/following_action branch, false = no_following_action branch); action prerequisites have no branch. 'satisfied_by' lists alternative upstream nodes that also satisfy the prerequisite. When an action node carries a 'flag', that boolean MUST be set to true on the node: for MESSAGE steps the flag also produces the task_type (e.g. flag_connector -> 'cr', flag_open_inmail -> 'oi', flag_inmail -> 'im'), while a Mobile Connection Request (task 'mr') requires 'flag_mobile' to be set so the step is treated as a mobile connection request. Conditions use task_type 'c' + condition_type. Use this to order builder_add_node calls into a valid flow. Nodes absent from this list have no upstream prerequisite. See builder_task_types and builder_condition_types for the full code lists.
builder_set_goal
ChatGPTSet or update the goal of an existing Builder (advanced flow) campaign draft. The goal has three fields: 'target' (target audience), 'value_proposition' (the offer/value proposition) and 'goal' (the campaign objective). This upserts the campaign's single goal record: it creates one if the campaign has none yet, otherwise it updates the existing one. Only the fields you pass are changed -- omit a field (or pass null) to leave it untouched, so you can update just the target or offer without clearing the rest. Draft only (active=false). To resolve the campaign from a name, call find_campaign or builder_get first (campaign_instance_id).
builder_task_types
ChatGPTList every queue task_type (Queue.TASK_CHOICES) with its human label and the action(s) that produce it, mirroring Action.get_queue_task_type. Each entry's 'produced_by' lists the action_type code + label and the boolean flag to set on the Action object (e.g. task 'cr' Connection request = MESSAGE action with flag_connector; 'oi' Open InMail = MESSAGE + flag_open_inmail; 'im' InMail = MESSAGE + flag_inmail; 'm' Message = MESSAGE with no flag). A null flag means no flag is required. Task types with an empty 'produced_by' are produced by the system, not by a builder action.
builder_time_deltas
ChatGPTList the valid time_delta codes with their human labels (e.g. 'c_a01' immediately, 'd01' 1 day, 'f01' 1 week). Call this to pick a valid time_delta for builder_add_node or builder_set_delay.
campaign_add_leads
ChatGPTAdd leads to a campaign inside the user's outreach account by LinkedIn profile_link, each with optional placeholder key/values. Same-account duplicates are skipped. Enforces the 5000-lead campaign limit and returns per-lead added/skipped results. Sending happens later under the user's limits in the outreach platform. Input: leads = [{profile_link, placeholders?}]. To resolve inputs from names: find_campaign (campaign_instance_id), find_lead (profile_link).
campaign_delete_lead
ChatGPTDelete (remove) a single lead from a campaign by profile_link. This is destructive: it removes the lead from the campaign and cancels its queued/future actions. Always confirm with the user before calling. To undo an accidental removal, call campaign_add_leads with the same profile_link to re-add the lead to the campaign. To transfer a lead between campaigns, combine the two tools: campaign_delete_lead on the source campaign, then campaign_add_leads on the destination campaign. To resolve inputs from names: find_campaign (campaign_instance_id), find_lead (profile_link).
campaign_get
ChatGPTGet details for a single campaign (name, type, status, lead count, assigned lead lists). If you only have a campaign name, call find_campaign first to resolve the campaign_instance_id.
campaign_get_lead_status
ChatGPTGet a lead's status in a campaign (current status, last action executed, whether a next action is scheduled, and the failure reason if any). To resolve inputs from names: find_campaign (campaign_instance_id), find_lead (profile_link).
campaign_list
ChatGPTList the campaigns for a LinkedIn account (name, type, active status, lead count). To resolve inputs from names: find_linkedin_account (li_account_id).
campaign_pause_lead
ChatGPTPause a lead in a campaign (stops scheduled actions and clears queued messages). Nothing is sent until the lead is resumed. To resolve inputs from names: find_campaign (campaign_instance_id), find_lead (profile_link).
campaign_resume_lead
ChatGPTResume a paused lead in a campaign. Sending happens later under the user's limits in the outreach platform. To resolve inputs from names: find_campaign (campaign_instance_id), find_lead (profile_link).
content_list_influencers
ChatGPTList the influencer profiles attached to a LinkedIn account for content scraping, with the last time each was reloaded (null if never scraped yet). To resolve the li_account_id from a name: find_linkedin_account.
content_list_keywords
ChatGPTList the keywords attached to a LinkedIn account for content scraping, with the last time each was reloaded (null if never scraped yet). To resolve the li_account_id from a name: find_linkedin_account.
find_campaign
ChatGPTFind campaigns by name (partial match). Optionally narrow to a single li_account_id, active status, and/or campaign_type. If no query is provided, returns all accessible campaigns. Use this to resolve a campaign_instance_id from a campaign name. To resolve the optional li_account_id from a name: find_linkedin_account. To resolve the optional campaign_type code: list_campaign_types.
find_campaign_template
ChatGPTFind campaign templates you can access by name (partial match). This includes your own templates, templates in workspaces or companies you can access, templates of any reseller you own, published marketplace templates of the reseller you belong to, and templates shared with you. If no query is provided, returns all accessible templates. Use this to resolve a template_id for builder_create. advanced_only defaults to true so only Builder-compatible (advanced flow) templates -- the ones builder_create accepts -- are returned; set it false to see all.
find_custom_list
ChatGPTFind lead lists by name (partial match) across all list types. Optionally narrow to a single li_account_id. If no query is provided, returns all accessible lead lists. Each result includes its search_type. Use this to resolve a list_id from a list name. To resolve the optional li_account_id from a name: find_linkedin_account.
find_lead
ChatGPTFind leads on a LinkedIn account by name, email, company, job title, or profile URL (partial match for text, exact for email/profile URL). Ensure a query is always present. Returns lightweight rows with the profile_link to feed into leads_get, inbox_get_messages, campaign_add_leads, etc. To resolve the li_account_id from a name: find_linkedin_account.
find_linkedin_account
ChatGPTFind LinkedIn accounts you can access by name or login email (partial match). If no query is provided, returns all accessible LinkedIn accounts.Use this to resolve an li_account_id when you only have a name/email; feed the returned li_account_id into the other tools. Each result also includes the workspace_id and workspace_name of the workspace the account belongs to (both null when the account is not in a workspace), so you can tell which workspace a LinkedIn account lives under.
find_webhook
ChatGPTFind webhooks by name (partial match) across accessible accounts. Optionally narrow to a single li_account_id. If no query is provided, returns all accessible webhooks. Use this to resolve a webhook_id from a webhook name before calling webhook_update / webhook_test / webhook_preview_payload / webhook_history. To resolve the optional li_account_id from a name: find_linkedin_account.
find_workspace
ChatGPTFind workspaces you can access by name (partial match). If no query is provided, returns all accessible workspaces. Each result includes li_account_count (how many LinkedIn accounts you can access in that workspace). Use this to resolve a workspace_id for the shared-signal tools (signals_list, signals_for_lead, signals_related_accounts).
inbox_draft_reply
ChatGPTCreates a draft reply and saves it in the user's own outreach platfrom inbox for human review. This tools does not send, publish or transmit any message, and does not contact the recipient or any external service. It only stores draft text inside the user's outreach account. Sending is a separate, manual action the user performs later in the outreach platform. Use it to prepare a suggested response the user will review, edit, and approve.You can only create draft messages to new contacts or contacts. Draft messages are flagged as API-sent and are subject to LinkedIn safety limits + queueing. To pick a valid contact_status filter value: list_contact_statuses. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
inbox_get_context
ChatGPTGet full context for a conversation: the lead (contact + messenger + placeholders, same shape as the lead-read tools), current campaign, and recent thread history. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
inbox_get_messages
ChatGPTGet recent messages in a conversation (by profile_link), most recent first, excluding queued/failed messages. Also reports the lead's current active campaign. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
inbox_list_conversations
ChatGPTList inbox conversations for a LinkedIn account, most recent first. Set unread_only=true to surface only conversations with new messages. Set retrieve_also_not_in_campaign=true to also include leads that are not part of a campaign; note the results are then not ordered (defaults to false). To resolve inputs from names: find_linkedin_account (li_account_id).
inbox_read_sentiment
ChatGPTRead the sentiment signal for a conversation. Backed by the AI Analyzer interest status (conversation-level); returns null where the outreach platform has not computed it. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
leads_add_tags
ChatGPTAssign one or more existing tags (by name) to a lead's contact by profile_link. Tags are matched against the account company's existing tags and are NEVER created -- names that do not exist are returned under 'rejected'. Idempotent: names already on the contact are returned under 'already_present'. To discover valid names: list_contact_tags. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
leads_get
ChatGPTGet a single lead by LinkedIn profile_link for a LinkedIn account. Returns the contact (LinkedIn-sourced), messenger relationship state, and dynamic placeholders. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
leads_list
ChatGPTList leads (contact + messenger + placeholder data) for a LinkedIn account. Optional filters: is_blacklisted, has_new_messages, distance (1/2/3), conversation_status, contact_status. Returns the same payload shape as webhooks. To pick a valid contact_status filter value: list_contact_statuses. To resolve inputs from names: find_linkedin_account (li_account_id).
leads_remove_tags
ChatGPTRemove one or more tags (by name) from a lead's contact by profile_link. Tags are matched against the account company's existing tags; names that do not exist are returned under 'rejected', and existing tags that were not on the contact are returned under 'not_present'. The tag itself is not deleted, only its assignment to this contact. To discover valid names: list_contact_tags. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
leads_set_placeholders
ChatGPTCreate or update dynamic placeholders (enrichment / personalization values) on a lead by profile_link. The placeholder text fields are stored on the user's own leads; no external contact data is modified. Silent overwrite of existing keys (same as CSV import). Name must be < 255 chars and value < 300 chars. Reserved keys (contact_status, conversation_status, tag, profile_link) are rejected. This is the only writable surface -- LinkedIn-sourced contact and messenger state are read-only. To resolve inputs from names: find_linkedin_account (li_account_id), find_lead (profile_link).
list_campaign_types
ChatGPTList the campaign_type codes with their human labels (e.g. 1 = connector campaign, 2 = messenger campaign, 3 = advanced campaign). Call this to pick a valid campaign_type to filter find_campaign.
list_contact_statuses
ChatGPTList the contact_status codes with their human labels (e.g. 11 = Searched, 1 = Contact, 2 = New Contact, 3 = Connect Requested, 4 = Disconnected, 21 = Imported, 34 = Revoked). Call this to pick a valid contact_status value before passing it to another tool (e.g. the contact_status filter of leads_list).
list_contact_tags
ChatGPTList the existing contact tags available on a LinkedIn account (scoped to the account's company). Returns each tag's id, name, and colors. Use this to pick a valid tag name before calling leads_add_tags / leads_remove_tags -- those tools only accept tags that already exist and never create new ones. To resolve inputs from names: find_linkedin_account (li_account_id).
list_signal_types
ChatGPTList the signal filter values the shared-signal tools accept: action_type codes with their labels (e.g. 1 = Message, 2 = Visit, 3 = Follow, 7 = Post like), status codes (9 = Sent, 10 = Received), and the named engagement_filters (replied, liked_post, visited_profile, followed). Call this to pick valid action_types / statuses / engagement_filters before passing them to signals_list.
list_webhook_events
ChatGPTList the webhook event types available on a LinkedIn account (dashboard parity), each with its code, human label, and input requirements: requires_tags (the 'Contact tagged' event needs tags), requires_interest_status (the 'Contact interest status changed' event needs an interest status), and high_volume_warning (the 'Contact added to campaign' event may trigger a high volume of hooks). Use this to suggest options and ask the user for the right data before calling webhook_create.
list_webhook_interest_statuses
ChatGPTList the interest_status codes with their human labels (All, Interested, Not interested, Maybe). Call this to pick a valid interest_status value for the 'Contact interest status changed' event before calling webhook_create / webhook_update.
reliability_account_health
ChatGPTGet account health for a LinkedIn account: connection/sync status, session validity, last successful sync timestamps, and active-campaign count. To resolve inputs from names: find_linkedin_account (li_account_id).
reliability_campaign_runway
ChatGPTGet a campaign's runway: leads remaining, leads stuck on a failure, recent daily pace, and a projected time-to-empty (pace and runway are computed, not stored). To resolve inputs from names: find_campaign (campaign_instance_id).
reliability_diagnose_gap
ChatGPTDiagnose why a campaign may not be executing as expected. Returns an attributed picture: account status, whether disconnected/restricted, whether a daily limit is reached, how many leads are available, and a failure breakdown by reason (each reason includes the count and the affected leads). To resolve inputs from names: find_campaign (campaign_instance_id).
reliability_escalate
ChatGPTRecovery: raise a structured 'human action required' escalation (e.g. reconnect account, clear restriction). This does not change anything -- it surfaces the one thing the AI cannot fix itself for human review and action. To resolve inputs from names: find_linkedin_account (li_account_id).
reliability_limit_headroom
ChatGPTGet per-action daily-limit headroom for a LinkedIn account: consumed vs cap and remaining for each action type, plus the warmup ramp bounds. To resolve inputs from names: find_linkedin_account (li_account_id).
reliability_list_failures
ChatGPTList a campaign's lead failures grouped by attributed failure reason. Each reason includes the failure count and the affected leads (contact + messenger + placeholder data, same shape as webhooks). To resolve inputs from names: find_campaign (campaign_instance_id).
reliability_restriction_state
ChatGPTGet restriction/cooldown state for a LinkedIn account (temporary restriction, fuse limit, cooldown/warmup). To resolve inputs from names: find_linkedin_account (li_account_id).
reliability_resume_leads
ChatGPTRecovery: resume paused/errored leads in a campaign (by profile_link). Sending happens later under the user's limits in the outreach platform. To resolve inputs from names: find_campaign (campaign_instance_id), find_lead (profile_link).
reliability_retry_failed
ChatGPTRecovery: retry failed actions for leads in a campaign by clearing the failure reason and re-queueing them. Sending happens later under the user's limits in Expandi. Pass profile_links to target specific leads, or omit to retry all failed leads in the campaign. To resolve inputs from names: find_campaign (campaign_instance_id), find_lead (profile_link).
reliability_trigger_topup
ChatGPTRecovery: trigger a list top-up by adding leads to a custom lead list inside the user's outreach account (delegates to the Build Audience add-leads flow, including any configured auto-assign). Sending happens later under the user's limits in the outreach platform. To resolve inputs from names: find_custom_list (list_id), find_lead (profile_link).
set_actions_in_builder_campaign
ChatGPTReplace a Builder (advanced flow) draft's entire step flow with the given nodes and connections. The flow is created inactive; a human must review and activate it; nothing is sent until activation. IMPORTANT: every call FULLY REPLACES the campaign's existing steps -- all current nodes and connections are deleted and rebuilt from scratch from this payload. This is NOT incremental: nodes you omit are removed, so ALWAYS send the complete desired flow every time (to add or change a single step, resend all the steps you want to keep plus the new/edited one). Call builder_get first if you need the current flow to modify. BEFORE calling, ALWAYS read the MCP resource guide://builder/actions (Campaign Builder step-sequencing reference: the step catalogue, what may follow what, auto-added prerequisites and save requirements), then consult builder_prerequisites to order the nodes into a valid flow (which conditions/actions must precede each node and on which branch), plus builder_action_types, builder_condition_types and builder_time_deltas to pick valid codes. CRITICAL: the nodes you create MUST ALWAYS satisfy every prerequisite returned by builder_prerequisites. For each node, ensure its required upstream conditions/actions are present earlier in the flow and placed on the correct branch; never emit a node whose prerequisites are missing or mis-ordered. If a required prerequisite is absent, add it before the dependent node rather than skipping it. Each node is an object like {element_id, action_type, time_delta, body, ...} (campaign_instance and campaign_type are set for you). In message copy, personalization placeholders use SINGLE braces (e.g. {first_name}, {company_name}), never double braces like {{first_name}}. Each node's element_id must be a UUID4 string (e.g. '3f2504e0-4f89-41d3-9a0c-0305e82c3301') that you generate; it is the handle used to wire connections. Each connection is an object with a single key 'uuids' whose value is a list of exactly two element_id port strings: [source_port, target_port]. A port string is '<element_id>_<port>', so wire nodes by element_id ports: '<id>_action_bottom' -> '<id>_action_top' for a regular next step; for a Condition (action_type 9) use '<id>_condition__true' or '<id>_condition__false' as the source and the target's '<id>_condition_top'/'<id>_action_top'. For example: {"uuids": ["<src_id>_action_bottom", "<dst_id>_action_top"]}. Draft only (active=false); this bulk-replaces any existing steps. To resolve the campaign from a name, call find_campaign first (campaign_instance_id). Each node must have ONLY ONE parent node. The first node must be either a Profile Visit or a Signal. A message node (action_type 1: connection request, follow-up, or open/paid InMail) may set 'is_using_ai': true together with a non-empty 'ai_prompt' to have its body generated per-lead by AI at send time. When 'is_using_ai' is true, 'ai_prompt' is required and 'body' may be omitted; these fields are only valid on message steps. Email steps (action_type 11) and Open/Paid InMail messages (action_type 1 with 'flag_open_inmail' or 'flag_inmail') may set a 'subject' string for the email/InMail subject line (personalization placeholders allowed, e.g. {first_name}); 'subject' is not valid on other steps. Paid InMail requires a 'subject' unless 'is_using_ai' is on (AI fills it at send time). A Mobile Connection Request (flag_mobile) cannot have a note: it sends only the connection request with no message, so omit 'body'/'subject' and do not set 'is_using_ai' on it (use a regular Connection Request if you need to send a note). ACCOUNT CAPABILITY: some steps need a premium/Sales-Navigator flag or feature on the connected account and are rejected otherwise -- Paid InMail (flag_inmail) requires the account to have Sales Navigator, and a Mobile Connection Request (flag_mobile) requires two-factor authentication set up with mobile login enabled on the account.
signals_for_lead
ChatGPTGet the shared-signal timeline for one lead across a workspace (every account you can access in it), newest first. Identify the lead by profile_link or contact_id and resolve the workspace_id with find_workspace. Each timeline row carries sent_or_received_at (date & hour), the li_account that produced it, the signal type, status (Sent/Received), the lead_name, and the company_name. Paginated with limit (max 100) + offset; next_offset is null when exhausted. To resolve inputs: find_workspace (workspace_id), find_lead (profile_link).
signals_related_accounts
ChatGPTList the LinkedIn accounts linked to one lead via shared signals in a workspace -- i.e. which of your accounts in that workspace have a signal with this lead. Identify the lead by profile_link or contact_id and resolve the workspace_id with find_workspace. Returns distinct accounts (li_account_id + name). Paginated with limit (max 100) + offset; next_offset is null when exhausted. To resolve inputs: find_workspace (workspace_id), find_lead (profile_link).
webhook_create
ChatGPTCreate an outbound webhook on a LinkedIn account to automate actions. Required: name, event, target (URL). Optional: campaign_instance_id (omit to apply to any campaign), schedule_hours (omit for instant delivery, or 1/4/8/12/24 for scheduled bulk delivery), active (defaults false, matching the dashboard -- enable it explicitly to start firing). Event-specific requirements: the 'Contact tagged' event requires tags=[...] (existing tag names), and the 'Contact interest status changed' event requires interest_status; the 'Contact added to campaign' event returns a high-volume warning. After creating, use webhook_preview_payload / webhook_test to verify. Webhooks cannot be deleted via the agent -- only from the dashboard. To resolve inputs from names: find_linkedin_account (li_account_id), find_campaign (campaign_instance_id). To pick an event: list_webhook_events; interest_status: list_webhook_interest_statuses; tags: list_contact_tags.
webhook_history
ChatGPTShow the delivery history of fired webhooks, returned in batches. Optional filters: li_account_id, webhook_name (partial match), event (event type code), campaign_instance_id, and succeeded (true/false status). Results are ordered newest-first and paginated with limit (default 25, max 100) and offset; the response includes total and next_offset for fetching the next batch. To resolve inputs from names: find_linkedin_account (li_account_id), find_campaign (campaign_instance_id). To pick an event code: list_webhook_events.
webhook_list
ChatGPTList the webhooks configured on a LinkedIn account (name, event, target URL, campaign, active state, delivery timing, tags, interest status). Webhooks cannot be deleted here -- removal is only possible from the dashboard. To resolve inputs from names: find_linkedin_account (li_account_id).
webhook_preview_payload
ChatGPTPreview the example payload a webhook would deliver, without sending any request. Returns the same example payload shape the dashboard shows. Use webhook_test to actually deliver a sample payload to the target URL. To resolve the webhook_id from a name: find_webhook.
webhook_test
ChatGPTSend a sample payload to a webhook's target URL to test it, mirroring the dashboard 'test' action. Returns whether the target responded successfully and a human-readable message. This makes a real outbound request to the configured target URL. Use webhook_preview_payload first if you only want to inspect the payload without sending. To resolve the webhook_id from a name: find_webhook.
webhook_update
ChatGPTEdit an existing webhook. Only the fields you pass are changed; omit a field to leave it as-is. Editable: name, event, target, campaign_instance_id (pass 0 to apply to any campaign), schedule_hours (pass 0 for instant, or 1/4/8/12/24 for scheduled), tags (pass [] to clear), interest_status, active. The campaign_instance_id and schedule_hours fields default to -1, which means 'leave unchanged'. Event-specific requirements still apply (the 'Contact tagged' event needs tags; the 'Contact interest status changed' event needs interest_status). Integration-managed webhooks cannot be edited. Webhooks cannot be deleted via the agent -- only from the dashboard. To resolve the webhook_id from a name: find_webhook.