resources/activity-properties-reference.md

objects create

hubspot properties get

Read first — this skill assumes its batching, pipe, and dry-run patterns.

1. Activities are invisible until associated. alone produces a record nobody can see in the CRM UI. Always follow with (and the deal, if relevant) before stopping.

objects create --property hs_timestamp=...

hs_timestamp

objects get --type calls <id>

properties.hs_timestamp

activities list --contact <id>

timestamp

2024-01-15T10:00:00Z

Current Unix ms: (macOS) or (Linux). rows are — the cross-type timeline read shape, no raw property names.

call_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:149 hubspot associations create --from calls:$call_id --to deals:456

note_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

start=$(date +%s)000; end=$(( ${start%000} + 3600 ))000 meeting_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

due=$(( $(date -v+7d +%s) * 1000 )) # macOS; Linux: date -d '7 days' +%s task_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

undefined

emits per row; reads from stdin in one batch call (see "Read in batch").

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")'

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.

due=$(( $(date -v+7d +%s) * 1000 ))

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

jq -c '.payload' /tmp/deal_tasks.jsonl
| hubspot objects create --type tasks > /tmp/created_tasks.jsonl

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

For >100 rows, apply the dry-run / digest / confirm pattern from `bulk-operations/SKILL.md`.

Activities must be associated immediately or they're invisible in the CRM UI. doesn't return enum option values for activity types — use the reference. No sequences/cadences in the CLI.