---
name: crm-push-prep
description: >-
  Use when the user wants to push a finished Firmable list to their connected CRM. Previews the push and requires named confirmation before writing. The only skill that writes to an external system.
version: 0.1.0
metadata:
  vendor: Firmable
  category: Manage Lists
  status: live
  personas: [RevOps, AE]
  jtbd: [improve-data]
  safety: writes-to-crm
  cost: crm-write
  requires_mcp: "Firmable MCP — https://agents-dev.firmable.com/mcp"
  mcp_tools: [get_list, push_to_crm]
---

# CRM Push Prep

Use when the user wants to push a finished Firmable list to their connected CRM. Previews the push and requires named confirmation before writing. The only skill that writes to an external system.

## When to use
You have a finished, quality-checked list ready to hand to the CRM.

## When NOT to use
Before you've checked list quality — run List-to-CRM Readiness Check and CRM Gap Finder first. Never push an unchecked list.

## Inputs
- **list_name** (required) — The Firmable list to push

## MCP tools used
- `get_list` — Reads the list and contactability flags for the preview _(Free)_
- `push_to_crm` — Writes records to the connected CRM (auto-detects HubSpot/Salesforce/Pipedrive) _(CRM write)_

## Procedure
Follow these steps in order:

1. Read the named list with get_list (record count + contactability).
2. Detect the connected CRM (HubSpot / Salesforce / Pipedrive).
3. Build a push preview: which records will be created vs updated, how duplicates are handled, and the estimated cost.
4. **⛔ REQUIRE** the user to confirm the list name AND the action before calling push_to_crm. Do not proceed without an explicit, named yes.
5. Execute push_to_crm only on confirmation; return the result. Never charge on a preview.

## Output format
Return exactly these sections:

1. List summary (name, record count, contactability)
2. CRM target (auto-detected)
3. Push preview (created / updated, duplicate handling)
4. Estimated cost
5. Named confirmation required (user must confirm the list name)
6. Result confirmation after push

## Safety & confirmation
**Writes to CRM.** Writes records to the connected CRM (a bulk action). Show a full preview with the record count and estimated cost, and require the user to confirm the list name before any write. Never charge on a preview.

## Example invocation
> Push my Firmable list 'AU FinTech Mid-Market' to our CRM. Show me a preview first and tell me what it will cost before I confirm.

## Suggested follow-ups
- Run a List-to-CRM Readiness Check first
- Which records would be duplicates in our CRM?
- Push only the records with a confirmed work email

## Data confidence
Confirmed Firmable capability — push_to_crm auto-detects the connected CRM. This is the only skill that writes to an external system; it always requires a named confirmation.

---
_Part of the Firmable MCP Skills library. Requires the Firmable MCP connector (https://agents-dev.firmable.com/mcp). Internal / development build — not licensed for external distribution yet._