CRM Push Prep
Previews exactly what will be created versus updated, how duplicates are handled, and the estimated cost, then requires you to confirm the list by name before anything gets written.
The safe way to move a finished Firmable list into your CRM. Previews exactly what will be created versus updated, how duplicates are handled, and the estimated cost, then requires you to confirm the list by name before anything gets written.
This is the only skill in the library that writes to an external system, so it’s built around a full preview and a named confirmation rather than a quiet one-click push.
What It Does
- Auto-detects your CRM: Works with HubSpot, Salesforce, or Pipedrive without you specifying which.
- Full push preview: Shows record counts, created versus updated, duplicate handling, and estimated cost before anything happens.
- Named confirmation required: Never writes without you explicitly confirming the list name and the action.
- Never charges on a preview: Cost is only incurred on the actual push, not on reviewing it.
- Contactability visibility: Surfaces contactability flags in the preview so you know what you’re actually pushing.
Use Cases
Finalizing a Target List for Outbound
Push a quality-checked ABM or prospecting list into the CRM once list-readiness checks are done.
Syncing an Enriched Segment
Move a segment you’ve cleaned up in Firmable into the CRM without manually re-entering records.
Controlled Handoff Between Teams
Use the preview step to confirm exactly what a marketing-built list will do to CRM records before RevOps signs off on the push.
Skill Definition
The raw markdown the agent uses when this skill is invoked.
--- 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. --- # CRM Push Prep Use when the user has a finished, quality-checked Firmable list ready to hand to the CRM. Always preview before writing, and require a named confirmation before any push. ## Procedure 1. Read the named list: record count and contactability. 2. Detect the connected CRM. 3. Build a push preview: records created versus updated, duplicate handling, and estimated cost. 4. Require the user to confirm the list name and the action before calling the push. Do not proceed without an explicit, named yes. 5. Execute the push only on confirmation, and return the result. Never charge on a preview.
Ready to run this skill?
Install the Firmable MCP and run CRM Push Prep from Claude, Codex, or any agent.