Sales Execution

hubspot/agent-cli-skills/sales-execution

作者 hubspota8eea0880838無授權條款27 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫7 天前更新

Log sales activities — calls, notes, meetings, tasks — against contacts and deals, with the mandatory create-then-associate step that makes them visible in the CRM.

僅含說明Marketing & Sales

AI 產生的概覽

將 HubSpot 銷售活動（通話、備註、會議、任務）記錄到聯絡人與交易上，並包含必要的關聯步驟。

功能: 提供透過 hubspot 命令列建立 HubSpot 通話、備註、會議與任務記錄的命令模式，並將每筆新記錄關聯到對應的聯絡人或交易，使其在 CRM 中可見。內容也涵蓋查詢某聯絡人及全入口網站的未完成任務、依任務狀態篩選，以及為某階段的每筆交易批次建立後續任務。文件說明了時間戳格式、列舉值查詢方式與 API 篩選條件上限。
適用情境: 適用於需要把銷售活動登錄到 HubSpot 的情境：記錄通話、備註或會議，建立後續任務，或為多筆交易批次產生後續任務。也適用於依負責人或聯絡人查詢未完成任務。
執行需求: 需要可存取 HubSpot CRM 的 hubspot 命令列工具、jq，以及具備 date 與 paste 工具的 shell；需要 HubSpot 憑證與網路存取。此技能不附帶指令碼，只有說明文件與一份屬性參考檔案，並假定已具備 bulk-operations 技能的批次處理與試執行模式。

Resources

File	When to use
`resources/activity-properties-reference.md`	Property names and enum values for calls/notes/meetings/tasks. Keep open while writing `objects create` — for live enum values run `hubspot properties options-list --type calls <property>`, and for call outcomes `hubspot activities calls dispositions list`; the reference is the shortcut.

Read bulk-operations/SKILL.md first — this skill assumes its batching, pipe, and dry-run patterns.

The two non-obvious rules

1. Activities are invisible until associated. hubspot objects create --type calls ... alone produces a record nobody can see in the CRM UI. Always follow with hubspot associations create --from calls:<id> --to contacts:<id> (and the deal, if relevant) before stopping.

2. Timestamps differ between write and read.

Path	Field	Format
`objects create --property hs_timestamp=...`	`hs_timestamp`	Unix ms (13 digits)
`objects get --type calls <id>` returns	`properties.hs_timestamp`	Unix ms (string)
`activities list --contact <id>` returns	`timestamp` (flat, top-level)	ISO 8601 (e.g. `2024-01-15T10:00:00Z`)

Current Unix ms: $(date +%s)000 (macOS) or $(date +%s%3N) (Linux). activities list rows are {"id","type","timestamp","lastModified","title","body","status","owner_id"} — the cross-type timeline read shape, no raw property names.

Create + associate, by type

bash

# CALLcall_id=$(hubspot objects create --type calls \  --property hs_call_title="Discovery call" \  --property hs_call_body="Confirmed $50K budget, Q2 timeline." \  --property hs_call_direction=OUTBOUND \  --property hs_call_status=COMPLETED \  --property hs_call_duration=1800000 \  --property hs_timestamp=$(date +%s)000 \  --format json | jq -r '.id')hubspot associations create --from calls:$call_id --to contacts:149hubspot associations create --from calls:$call_id --to deals:456
# NOTEnote_id=$(hubspot objects create --type notes \  --property hs_note_body="Sent proposal. Follow-up Friday." \  --property hs_timestamp=$(date +%s)000 \  --format json | jq -r '.id')hubspot associations create --from notes:$note_id --to deals:456
# MEETING — start/end in Unix ms; reuse start as hs_timestampstart=$(date +%s)000; end=$(( ${start%000} + 3600 ))000meeting_id=$(hubspot objects create --type meetings \  --property hs_meeting_title="Demo — Acme" --property hs_meeting_outcome=COMPLETED \  --property hs_meeting_start_time=$start --property hs_meeting_end_time=$end \  --property hs_timestamp=$start --format json | jq -r '.id')hubspot associations create --from meetings:$meeting_id --to contacts:149
# TASK — hs_timestamp is the DUE DATE, not creation timedue=$(( $(date -v+7d +%s) * 1000 ))   # macOS; Linux: date -d '7 days' +%stask_id=$(hubspot objects create --type tasks \  --property hs_task_subject="Confirm proposal received" \  --property hs_task_priority=HIGH \  --property hs_task_status=NOT_STARTED \  --property hs_task_type=CALL \  --property hs_timestamp=$due \  --format json | jq -r '.id')hubspot associations create --from tasks:$task_id --to deals:456

# CALLcall_id=$(hubspot objects create --type calls \  --property hs_call_title="Discovery call" \  --property hs_call_body="Confirmed $50K budget, Q2 timeline." \  --property hs_call_direction=OUTBOUND \  --property hs_call_status=COMPLETED \  --property hs_call_duration=1800000 \  --property hs_timestamp=$(date +%s)000 \  --format json | jq -r '.id')hubspot associations create --from calls:$call_id --to contacts:149hubspot associations create --from calls:$call_id --to deals:456
# NOTEnote_id=$(hubspot objects create --type notes \  --property hs_note_body="Sent proposal. Follow-up Friday." \  --property hs_timestamp=$(date +%s)000 \  --format json | jq -r '.id')hubspot associations create --from notes:$note_id --to deals:456
# MEETING — start/end in Unix ms; reuse start as hs_timestampstart=$(date +%s)000; end=$(( ${start%000} + 3600 ))000meeting_id=$(hubspot objects create --type meetings \  --property hs_meeting_title="Demo — Acme" --property hs_meeting_outcome=COMPLETED \  --property hs_meeting_start_time=$start --property hs_meeting_end_time=$end \  --property hs_timestamp=$start --format json | jq -r '.id')hubspot associations create --from meetings:$meeting_id --to contacts:149
# TASK — hs_timestamp is the DUE DATE, not creation timedue=$(( $(date -v+7d +%s) * 1000 ))   # macOS; Linux: date -d '7 days' +%stask_id=$(hubspot objects create --type tasks \  --property hs_task_subject="Confirm proposal received" \  --property hs_task_priority=HIGH \  --property hs_task_status=NOT_STARTED \  --property hs_task_type=CALL \  --property hs_timestamp=$due \  --format json | jq -r '.id')hubspot associations create --from tasks:$task_id --to deals:456

Open tasks for a contact — two CLI calls, no xargs

associations list emits {"id": …} per row (plus label/associationType fields); objects get reads from stdin in one batch call (see bulk-operations/SKILL.md "Read in batch").

bash

hubspot associations list --from contacts:149 --to tasks \| hubspot objects get --type tasks \    --properties hs_task_subject,hs_task_status,hs_task_priority,hs_timestamp \| jq -c 'select(.properties.hs_task_status != "COMPLETED")'

hubspot associations list --from contacts:149 --to tasks \| hubspot objects get --type tasks \    --properties hs_task_subject,hs_task_status,hs_task_priority,hs_timestamp \| jq -c 'select(.properties.hs_task_status != "COMPLETED")'

Open tasks portal-wide — exclude statuses server-side with `@!=`

@!= is NOT_IN: one condition for the whole excluded list. Do not spend one --filter flag per excluded status — the search API caps a request at 5 filter groups, 6 conditions per group, and 18 conditions total.

@!= matches only records that have the property, so replicating a real HubSpot task view's "status is none of … or is empty" needs two groups (OR'd), with the shared conditions repeated in each:

bash

hubspot objects search --type tasks \  --filter "hubspot_owner_id=123 AND hs_task_status@!=COMPLETED,DEFERRED" \  --filter "hubspot_owner_id=123 AND !hs_task_status" \  --properties hs_task_subject,hs_task_status,hs_task_priority,hs_timestamp

hubspot objects search --type tasks \  --filter "hubspot_owner_id=123 AND hs_task_status@!=COMPLETED,DEFERRED" \  --filter "hubspot_owner_id=123 AND !hs_task_status" \  --properties hs_task_subject,hs_task_status,hs_task_priority,hs_timestamp

Inverse (only these statuses) is @= (IN): --filter "hs_task_status@=NOT_STARTED,IN_PROGRESS,WAITING".

Bulk: follow-up task per deal in a stage

The deal ID and the task ID must travel together. Persist the deal payload to a file, create tasks (output order matches input order — see bulk-operations), then zip the two ID lists line-by-line and stream association pairs in one call.

bash

due=$(( $(date -v+7d +%s) * 1000 ))
# 1. Per-deal payload, deal_id retained alongside the create payload.hubspot objects search --type deals --filter "dealstage=appointmentscheduled" \  --properties dealname \| jq -c --argjson due "$due" '{deal_id: .id, payload: {properties: {    hs_task_subject: ("Follow up: " + .properties.dealname),    hs_task_priority: "HIGH", hs_task_status: "NOT_STARTED", hs_task_type: "CALL",    hs_timestamp: ($due|tostring)  }}}' > /tmp/deal_tasks.jsonl
# 2. Create tasks; one CLI call for the whole batch.jq -c '.payload' /tmp/deal_tasks.jsonl \| hubspot objects create --type tasks > /tmp/created_tasks.jsonl
# 3. Zip and stream association pairs through stdin.paste \  <(jq -r '.deal_id' /tmp/deal_tasks.jsonl) \  <(jq -r '.id'      /tmp/created_tasks.jsonl) \| jq -Rc 'split("\t") | {from:("tasks:"+.[1]), to:("deals:"+.[0])}' \| hubspot associations create

due=$(( $(date -v+7d +%s) * 1000 ))
# 1. Per-deal payload, deal_id retained alongside the create payload.hubspot objects search --type deals --filter "dealstage=appointmentscheduled" \  --properties dealname \| jq -c --argjson due "$due" '{deal_id: .id, payload: {properties: {    hs_task_subject: ("Follow up: " + .properties.dealname),    hs_task_priority: "HIGH", hs_task_status: "NOT_STARTED", hs_task_type: "CALL",    hs_timestamp: ($due|tostring)  }}}' > /tmp/deal_tasks.jsonl
# 2. Create tasks; one CLI call for the whole batch.jq -c '.payload' /tmp/deal_tasks.jsonl \| hubspot objects create --type tasks > /tmp/created_tasks.jsonl
# 3. Zip and stream association pairs through stdin.paste \  <(jq -r '.deal_id' /tmp/deal_tasks.jsonl) \  <(jq -r '.id'      /tmp/created_tasks.jsonl) \| jq -Rc 'split("\t") | {from:("tasks:"+.[1]), to:("deals:"+.[0])}' \| hubspot associations create

These are objects create calls (Additive) — creates are never digest-gated, so --dry-run is a plain preview and you execute by dropping it (no digest/confirm). The digest flow only applies to the irreversible writes (update/upsert/delete/merge) in bulk-operations/SKILL.md.

Known constraints

Activities must be associated immediately or they're invisible in the CRM UI. For enum option values on activity properties, run hubspot properties options-list --type calls <property> (and for call outcomes, hubspot activities calls dispositions list); the reference is the shortcut. Sales Hub sequences are read-only in the CLI (hubspot sequences list / get / enrollments, automation.sequences.read scope) — the CLI cannot enroll a contact in a sequence, so drive outreach via tasks/activities above. This surface grows; recheck hubspot --help / CHANGELOG.md before assuming an API is missing.

來源與署名

來源：hubspot/agent-cli-skills位於sales-execution提交a8eea08

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

Sales Execution

Resources

The two non-obvious rules

Create + associate, by type

Open tasks for a contact — two CLI calls, no xargs

Open tasks portal-wide — exclude statuses server-side with `@!=`

Bulk: follow-up task per deal in a stage

Known constraints

來源與署名

更多來自 hubspot/agent-cli-skills 的技能

Workflow Automation

Ticket Resolution

Team Ownership

Sales Reporting

Deal Management

Quote To Cash

更多Marketing & Sales技能

Deal Sourcing

Investment Proposal

Content Strategy

Call List

Lead Triage

Draft Outreach

Sales Execution

Resources

The two non-obvious rules

Create + associate, by type

Open tasks for a contact — two CLI calls, no xargs

Open tasks portal-wide — exclude statuses server-side with @!=

Bulk: follow-up task per deal in a stage

Known constraints

來源與署名

更多來自 hubspot/agent-cli-skills 的技能

Workflow Automation

Ticket Resolution

Team Ownership

Sales Reporting

Deal Management

Quote To Cash

更多Marketing & Sales技能

Deal Sourcing

Investment Proposal

Content Strategy

Call List

Lead Triage

Draft Outreach

Open tasks portal-wide — exclude statuses server-side with `@!=`