hubspot-log-call_skill

This skill logs a HubSpot call engagement with title, optional body and duration to streamline CRM records.
  • Python

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill abdullahbeam/nexus-design-abdullah --skill hubspot-log-call

  • SKILL.md2.3 KB

Overview

This skill logs call engagements directly into HubSpot CRM from a command or prompt. It requires a call title and accepts optional notes, duration, direction, and status so interactions are recorded accurately. It returns the HubSpot call object and a friendly display summary after a successful log.

How this skill works

Before use, run the included configuration check to ensure API credentials and scopes are valid. When invoked with the required title and optional parameters, the skill creates a call engagement via the HubSpot API and returns the created object with properties like title, body, direction, duration (ms), status, and timestamp. It surfaces common API errors and provides actionable messages for authentication, permissions, and rate limits.

When to use it

  • After completing a sales or support call to capture what was discussed.
  • When you need a record of call duration, direction, and outcome for reporting.
  • To log missed or failed call attempts for follow-up workflows.
  • When linking a call to contacts or deals in HubSpot for activity tracking.

Best practices

  • Always run the configuration check before logging calls to verify authentication and scopes.
  • Provide a concise, descriptive title and include next steps or action items in the notes.
  • Use duration in minutes; the skill converts to milliseconds for HubSpot storage.
  • Set the proper status (COMPLETED, NO_ANSWER, BUSY, etc.) to keep activity reporting accurate.
  • Handle rate limit (429) responses by retrying after a brief wait and respecting backoff.

Example use cases

  • Log a completed discovery call with notes and a 30-minute duration for the sales record.
  • Record a missed outbound follow-up attempt with status NO_ANSWER for later outreach.
  • Track inbound support calls with body notes summarizing the issue and resolution steps.
  • Add call activities before linking them to related contacts or deals for timeline context.

FAQ

Only a title is required. Notes (body), duration, direction, and status are optional.

What do I do if I get a 401 or 403 error?

401 indicates invalid credentials—re-run the configuration setup. 403 means the integration lacks the crm.objects.calls.write scope; update credentials and scopes.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
hubspot-log-call skill by abdullahbeam/nexus-design-abdullah | VeilStrat