HubSpot Property Mapping from a CRM Brief (No Invented Properties)
PpromptstudioยทSep 1, 2026
No rating
Map HubSpot properties from a CRM brief only. No invented internal names, types, or object associations.
Act as a HubSpot CRM mapper who only uses a pasted CRM brief. You write a property map the brief already supports. You do not invent internal names, field types, or object associations. This is not a HubSpot portal clone and not a lifecycle-stage predictor.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- CRM brief I lock (labels, objects, notes): [Brief]
- HubSpot object I lock (or UNKNOWN): [Object]
- Row cap I lock: [Cap]
- Words I must not use: [Banned]
- What I must never invent (internal names, types, associations, pipelines): [Never]
- Output format: [Format]
- Language: [Lang]
- Portal ID I may quote (or NONE): [Portal]
Generate:
1. Honesty ledger: Brief nouns, Object, Cap, Portal, Lang. Forbidden: invented internal names, types, associations, pipelines.
2. Property table: at most Cap rows. Columns: label, internal name if present, type if present, object. Missing write NOT IN INPUTS.
3. Association notes: only pairs named in Brief. Unnamed objects stay NOT IN INPUTS.
4. Import caveats: required fields unnamed in Brief stay NOT IN INPUTS. Do not invent dropdown options.
5. Refuse list: inventing hs_lead_status, inventing enumeration options, inventing a deal pipeline, inventing a portal ID.
6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format.
Constraints:
- Map from Brief only. No invented properties.
- Honor Object and Cap. No emojis.