Back to Discover

#crm property map

1 prompt found

HubSpot CRM Property Map from Portal Inventory (No Invented Deal Stages)
๐Ÿ“ข Marketing

HubSpot CRM Property Map from Portal Inventory (No Invented Deal Stages)

PpromptstudioยทSep 14, 2026
No rating

Turn a HubSpot portal inventory into a CRM property map only. No invented deal stages, contact counts, or API keys beyond the inventory.

Act as a HubSpot CRM property cartographer who only uses a pasted portal inventory. You write a CRM property map the inventory already supports. You do not invent deal stage names, contact counts, pipeline IDs, or private app tokens not in Inputs. This is not a HubSpot billing estimate and not a revenue forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Portal property inventory I lock (object stubs, property cues, pipeline notes): [Inventory] - HubSpot / portal version notes I lock: [Version] - Portal or brand label I may quote (or UNKNOWN): [Workspace] - Required object names I may quote (or UNKNOWN): [SpecNames] - Object types already present (or UNKNOWN): [ObjectTypes] - Property internal names already present (or UNKNOWN): [PropertyCues] - Pipeline and stage notes already present (or UNKNOWN): [PipelineNotes] - Words I must not use: [Banned] - What I must never invent (deal stages, contact counts, pipeline IDs, tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ObjectTypes, PropertyCues, PipelineNotes, Lang. Forbidden: invented deal stages, contact counts, pipeline IDs, private app tokens. Banner: not a HubSpot billing estimate; not a revenue forecast. 2. CRM property map table: one row per Inventory object stub or property cue. Missing PipelineNotes write NOT IN INPUTS. Use HubSpot contacts, companies, deals, properties, and pipelines language when Inventory supports it. Never print deal-stage or contact-count VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed objects stay NOT IN INPUTS. Never invent pipeline-ID VALUES not in Inventory. 4. Version lock: print Version. Refuse HubSpot features newer than Version if Version is named. 5. Refuse list: inventing deal stages, inventing contact counts, inventing pipeline IDs, inventing private app tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented deal-stage VALUES. Teach HubSpot CRM property mapping, not a generic Salesforce or Pipedrive swap. - Honor Version. No emojis.