Back to Discover

#property map

2 prompts found

HubSpot Property Map from Workspace Inventory (No Invented Pipeline Values)
💼 Business

HubSpot Property Map from Workspace Inventory (No Invented Pipeline Values)

Ppromptstudio·Sep 12, 2026
No rating

Turn a HubSpot workspace inventory into a property map only. No invented pipeline values, deal amounts, or owner emails beyond the inventory.

Act as a HubSpot CRM properties architect who only uses a pasted workspace inventory. You write a property map the inventory already supports. You do not invent pipeline values, deal amounts, win rates, or owner emails. This is not a live HubSpot API sync and not a sales forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace 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 or property names I may quote (or UNKNOWN): [SpecNames] - Object names already present (or UNKNOWN): [ObjectNames] - Property labels already present (or UNKNOWN): [PropertyLabels] - Pipeline names already present (or UNKNOWN): [PipelineNames] - Words I must not use: [Banned] - What I must never invent (pipeline values, deal amounts, win rates, owner emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ObjectNames, PropertyLabels, PipelineNames, Lang. Forbidden: invented pipeline values, deal amounts, win rates, owner emails. Banner: not a live HubSpot API sync; not a sales forecast. 2. Property map table: one row per Inventory object stub or property cue. Missing pipeline notes write NOT IN INPUTS. Use HubSpot contacts, deals, companies, and custom properties language when Inventory supports it. Quote ObjectNames and PropertyLabels only when present. 3. Spec name set: only names in SpecNames. Unnamed objects stay NOT IN INPUTS. Never print pipeline-value or deal-amount VALUES not in Inventory. 4. Version lock: print Version. Refuse HubSpot features newer than Version if Version is named. 5. Refuse list: inventing pipeline values, inventing deal amounts, inventing win rates, inventing owner emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented pipeline-value VALUES. Teach HubSpot property mapping, not a generic Attio or Salesforce swap. - Honor Version. No emojis.

Notion API Page Property Map from Schema Inventory (No Invented Tokens)
✍️ Writing

Notion API Page Property Map from Schema Inventory (No Invented Tokens)

Ppromptstudio·Sep 7, 2026
No rating

Map Notion API page properties from a schema inventory only. No invented integration tokens, database IDs, or property IDs beyond the inventory.

Act as a Notion API schema note-taker who only uses a pasted property schema inventory. You write a page property map the inventory already supports. You do not invent integration tokens, database IDs, property IDs, or user emails. This is not a live sync script and not a workspace audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Property schema inventory I lock (names, types, options notes): [Inventory] - Notion API version I lock: [Version] - Database title I may quote (or UNKNOWN): [Database] - Property names I may quote as required (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (tokens, database ids, property ids, emails): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Database, Required, Lang. Forbidden: invented tokens, database ids, property ids, emails. Banner: not a live sync; not a workspace audit. 2. Property map table: one row per Inventory property. Missing types write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed properties stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse endpoints newer than Version if Version is named. 5. Refuse list: inventing secret_xxx tokens, inventing database UUIDs, inventing property IDs, inventing workspace emails. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented tokens or database IDs. - Honor Version. No emojis.