Prompt Tips for Schema

The schema agent responds best to specific, actionable prompts. Here are techniques and examples to help you get the most out of it.

Single-Object Prompts

When you have one object selected, try prompts like:

“Review the properties on this object and suggest any that are redundant or could be consolidated.”

“What associations is this object missing? Are there related objects it should be linked to?”

“Suggest property groups to better organize the fields on this object.”

“Are there any properties that should be marked as required or unique?”

All-Objects Prompts

In All Objects mode, the agent can analyze your entire data model:

“Review my full schema and identify any missing associations between objects.”

“Check for inconsistent naming conventions across all objects and properties.”

“Are there any custom objects that overlap in purpose? Suggest how to consolidate them.”

“Review my pipeline stages across deals and tickets — are the stages consistent and well-structured?”

Asking About Specific Elements

You can ask about particular properties, groups, or associations by name:

• “What is the hs_lead_status property used for and should I keep it?”
• “Explain the association between contacts and companies.”
• “Which properties are in the contactinformation group?”

Planning New Schema Elements

Ask the agent to propose new structures:

“Design a custom object for tracking customer projects, including properties, groups, and associations to contacts and companies.”

“Plan a set of properties for a subscription management workflow on the deal object.”

“Suggest a pipeline structure for our customer onboarding process.”

Requesting Change Proposals

Be explicit about what you want changed and why:

“Create a new property group called ‘Billing’ on the company object with properties for billing address, payment terms, and invoice frequency.”

“Add an association between the deals object and a custom ‘Projects’ object, with labels for ‘Primary Project’ and ‘Related Project’.”

General Tips

• Start with analysis prompts before requesting changes — understanding your current schema helps you make better decisions
• Reference specific object and property names when possible
• Ask the agent to explain its reasoning if a recommendation is unclear
• Use All Objects mode for big-picture reviews, then switch to a specific object for targeted changes