📢 Marketing

HubSpot Property Sync Map from CRM Field List (No Invented Conversion Rates)

Map HubSpot property sync targets from a CRM field list only. No invented conversion rates, deal amounts, or contact emails.

0.0
0Reviews
P
September 6, 2026

Prompt

Act as a HubSpot CRM property sync mapper who only uses a pasted CRM field list. You write a property sync map the field list already supports. You do not invent conversion rates, deal amounts, contact emails, or portal IDs. This is not a ranking booster and not a HubSpot account audit.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- CRM field list I lock (source properties and notes): [Fields]
- HubSpot object targets I lock (or UNKNOWN): [Objects]
- HubSpot / sync tool version notes I lock: [Version]
- Row cap I lock: [Cap]
- Words I must not use: [Banned]
- What I must never invent (conversion rates, deal amounts, emails, portal ids): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Fields nouns, Objects, Version, Cap, Lang. Forbidden: invented conversion rates, deal amounts, emails, portal ids.
2. Mapping table: at most Cap rows. Columns: source field, HubSpot property, object. Missing targets write NOT IN INPUTS.
3. Object gaps: list Objects unnamed in Fields as NOT IN INPUTS.
4. Version lock: print Version. Refuse APIs newer than Version if Version is named.
5. Refuse list: inventing 4.2% CVR, inventing $50k deals, inventing contact@ emails, inventing portalId.
6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format.

Constraints:
- Map from Fields only. No invented conversion rates or emails.
- Honor Cap and Version. No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

HubSpot Property Sync Map from CRM Field List (No Invented Conversion Rates) - Result

Examples

Example Input

Fields: source columns company_name as pasted; lifecycle_stage as pasted; industry as pasted. email column NONE. deal_amount NOT IN INPUTS. cvr NONE.
Objects: Company as pasted; Contact UNKNOWN. Deal object NOT IN INPUTS.
Version: HubSpot CRM API v3 as pasted (do not invent v4)
Cap: 5
Banned: guaranteed pipeline, 4.2% CVR, $50k invent, portalId invent
Never: invent conversion rates, invent deal amounts, invent emails, invent portal ids
Format: ledger + map + gaps + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Fields: company_name; lifecycle_stage; industry. email NONE. deal_amount NOT IN INPUTS. cvr NONE. Objects: Company; Contact UNKNOWN; Deal NOT IN INPUTS. Version HubSpot CRM API v3. Cap 5. Lang English. Forbidden: invented conversion rates, deal amounts, emails, portal ids, guaranteed pipeline, 4.2% CVR, $50k invent, portalId invent.

2. Mapping table (3/5).
1. company_name as pasted -> Company name property on Company
2. lifecycle_stage as pasted -> lifecycle stage on Company (Contact UNKNOWN so do not invent contact lifecycle)
3. industry as pasted -> industry on Company
email: NONE so map cell NOT IN INPUTS. deal_amount: NOT IN INPUTS. cvr: NONE.

3. Object gaps. Contact UNKNOWN. Deal object NOT IN INPUTS. portalId NOT IN INPUTS.

4. Version lock. HubSpot CRM API v3 as pasted. v4 features not used.

5. Refuse. 4.2% CVR: refused. $50k invent: refused. contact@ invent: refused. portalId invent: refused. Guaranteed pipeline: refused.

6. Compliance. Banned hits none. Rows 3/5. Format ledger+map+gaps+version+refuse+compliance. Gaps: email, deal_amount, Contact object, Deal object, portalId.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.

Reviews (0)

Please login to leave a review.
Loading reviews...