菜单
Pushes Hunter leads to a connected CRM (e.g. HubSpot, Salesforce, Pipedrive). Use when the user wants to sync leads to their CRM, export contacts to HubSpot/Salesforce, or send a list to their connected sales tool.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Builds and runs email outreach sequences end to end — create a sequence, add follow-up steps and message templates, add recipients from your leads, then start, pause, resume, or check its stats. Use when the user wants to set up outreach, build an email sequence, add recipients, launch a drip, or check sequence performance.
Reports the Hunter account's plan, remaining credits, and usage. Use when the user asks how many credits they have left, what plan they're on, or how much of their quota they've used.
Retrieves detailed company information including industry, size, location, and description from a domain name. Use when the user asks about a company, wants company details, or says "tell me about [company]".
Saves companies and organizes them into Hunter company lists — save a company, add/remove companies to lists, create and manage lists and folders, and bulk copy/move/delete companies. Use when the user wants to save companies from a search, build a target-account list, or organize companies into lists and folders.
Finds companies matching criteria (industry, size, location, technologies), estimates how many contacts exist across them, and manages saved searches. Use when the user wants to find companies, build a target-account list, or size a prospecting batch before spending credits. Browsing is free.
Finds all publicly available email addresses and contacts at a company domain. Use when the user asks who works at a company, wants to find contacts at a domain, or needs email addresses for an organization.
| name | push-to-crm |
| description | Pushes Hunter leads to a connected CRM (e.g. HubSpot, Salesforce, Pipedrive). Use when the user wants to sync leads to their CRM, export contacts to HubSpot/Salesforce, or send a list to their connected sales tool. |
| user-invocable | true |
| argument-hint | Push my Q2 leads to HubSpot |
Send leads from Hunter to a connected CRM.
/hunter:push-to-crm Push my Q2 leads to HubSpot"Send these contacts to Salesforce""Sync the fintech list to my CRM""Which CRMs do I have connected?"List-Connected-Apps to show the user's connected integrations; Get-Connected-App for details on one.Determine which leads to push. Push-Leads-To-CRM accepts only saved lead_ids or a leads_list_id — so if the "current selection" is unsaved Domain Search / finder results, first save them as leads (with the user's OK, via Create-Lead-If-Missing) and push those IDs. You can't push unsaved rows. lead_ids is capped at 100: for larger selections, save them to a leads list and push the leads_list_id instead (or batch the IDs in groups of 100 after confirming the total). Note: Create-Lead-If-Missing leaves an already-existing lead out of the new list, so pushing that new leads_list_id would skip those contacts — collect the full set of lead_ids (existing + new, via Lead-Exists / List-Leads) and push those IDs. Don't reach for Create-Or-Update-Lead just to force list membership — it overwrites the existing lead's fields; use it only if the user explicitly wants to update them.
State the target app and how many records will be sent, and wait for explicit confirmation, because this writes data into an external system:
"This will push 40 leads to HubSpot. Confirm?"
Only after a "yes", call Push-Leads-To-CRM with the leads and the target app.
Push-Leads-To-CRM is asynchronous — it returns a queued status and the lead count, not per-record results. Report that; do not invent created/updated/skipped numbers.
# Push queued → HubSpot
**Leads queued:** 40 | **Status:** queued
The sync runs in the background — check HubSpot in a few moments to confirm the records.
## Next Actions
1. Push another list
2. Review the leads in HubSpot shortly
Push-Leads-To-CRM commits data to an external system — always confirm the target app and the record count before executing. Never push silently or by default. The call only queues the sync (it returns queued + count, not per-record results), so report it as queued and point the user to the CRM to verify the outcome.
Free — pushing leads to a connected CRM does not consume credits.