Menu
Pull a HubSpot company list, view, or segment into Saber as a target account or contact list, ready for signal activation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | import-from-hubspot |
| description | Pull a HubSpot company list, view, or segment into Saber as a target account or contact list, ready for signal activation. |
Use this skill to pull companies or contacts from HubSpot into Saber as a list, so you can run signals against your existing CRM data.
Before doing anything else, check if a HubSpot MCP is available by looking for HubSpot-related tools in your available tool list (tools with hubspot in the name for reading contacts, companies, or lists).
If a HubSpot MCP is available: proceed with the full workflow below.
If no HubSpot MCP is detected: inform the user and offer two options:
saber list company import or saber list contact create to bring it into SaberAlso verify the Saber CLI is available (saber --help). It is needed to create the Saber list.
If not available: inform the user and direct them to saber.app.
Ask the user what they want to import:
Use the HubSpot MCP to browse available lists if the user isn't sure:
List all HubSpot company lists / contact lists
Using the HubSpot MCP, fetch the companies or contacts from the selected list/view. For each record, collect:
For companies:
For contacts:
Paginate through the full result set if the list is large.
For a company list:
saber list company create --name "<descriptive name, e.g. HubSpot - Tier 1 Accounts>"
If the companies have consistent attributes (industry, size, country), consider using those as filters instead so Saber can also discover similar companies:
saber list company create --name "<name>" --industry "<industry>" --country "<country>" --size "<size>"
For a contact list: Create the list using the LinkedIn URLs from HubSpot:
saber list contact create --name "<name>" \
--company-linkedin <url> \
--company-linkedin <url> \
[--title "<title>"]
Show the user a summary:
saber list company get <listId>
# or
saber list contact get <listId>
Once the list is in Saber:
signal-discovery if signal definitions don't exist yetcreate-company-signals or create-contact-signals to activate signal tracking against the imported listscore-accounts after signals complete to prioritise the imported accountsActivate company-level signal tracking. Runs signals via the Saber CLI if available; without it, outputs a research playbook and suggests alternative tracking methods.
Generate 12–15 structured, weighted research signals from a structured ICP, ready to activate in Saber. Each signal includes answer type, weight, and interpretation rules for automatic scoring.
Deep research on a single company — signals, hiring, news, tech stack, and LinkedIn presence. Uses the Saber CLI for signal data and any available MCP tools for broader research.
End-to-end guided workflow — take one prospect domain, run your saved research signals, find named contacts on the buying committee, and write a hyper-personalised cold email and LinkedIn DM grounded in the signal answers. First run defines the source-company ICP, contact-search targets, and ≤5 weighted signals (saved to disk); every subsequent run reuses them. Use when you want full SDR research-and-write for a single prospect, not write-outreach in isolation.
End-to-end guided workflow — build a Saber company list, run research signals across every company in parallel, find named contacts, and export a combined CSV to the desktop. Walks the user through each stage with confirmations and a credit-discipline guard. Use when you want one signed-off CSV instead of running build-account-list, create-company-signals, and build-contact-list separately.
Build a target account list and run company signals against it. Works with the Saber CLI, Apollo, HubSpot, or any available prospecting tool — with a manual fallback.