Menu
Push Saber signal results back to HubSpot as contact or company properties, keeping your CRM up to date with the latest intent data.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Activate 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.
| name | sync-to-hubspot |
| description | Push Saber signal results back to HubSpot as contact or company properties, keeping your CRM up to date with the latest intent data. |
Use this skill to write Saber signal results back to HubSpot, so sales reps can see intent data directly on contact and company records without leaving their CRM.
Before doing anything else, check if a HubSpot MCP is available by looking for HubSpot-related tools in your available tool list (e.g. tools with hubspot in the name for updating contacts, companies, or properties).
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:
Also check if the Saber CLI is available (saber --help). It is needed to fetch signal results.
If not available: ask the user to provide signal results directly (paste output or CSV from the Saber dashboard).
Ask the user:
Fetch the subscriptions:
saber subscription list
saber subscription get <subscriptionId>
For each signal question, decide how to represent it in HubSpot. Common mappings:
| Signal | HubSpot property type | Example property name |
|---|---|---|
| Boolean signal (yes/no) | Checkbox or single-line text | saber_hiring_signal |
| Signal result with detail | Multi-line text | saber_signal_notes |
| Signal run date | Date | saber_last_signal_date |
Overall score (from score-accounts) | Number | saber_intent_score |
Ask the user if these HubSpot properties already exist or need to be created. If they need to be created, use the HubSpot MCP to create them first.
Recommend using a consistent prefix (e.g. saber_) for all Saber-sourced properties so they're easy to filter and report on in HubSpot.
For each company in the signal results, find the matching HubSpot record:
For contact records: search by LinkedIn URL or email address.
Note any records that don't have a HubSpot match — present these to the user at the end.
For each matched record, update the mapped properties using the HubSpot MCP:
Confirm each write succeeded. If any writes fail, note them and continue — don't abort the whole sync.
Present a sync summary:
## HubSpot Sync Complete
✓ Updated: [N] company records
✓ Updated: [N] contact records
⚠ No HubSpot match found: [list of unmatched companies]
✗ Failed writes: [list of any errors]
Properties written: saber_hiring_signal, saber_funding_signal, saber_last_signal_date
Suggest next steps:
saber_intent_score > 7 to build a prioritised outreach viewsaber_hiring_signal = true to auto-enroll high-intent accounts in a sequence