Skip to content
Daeda Daeda Docs

Custom Objects

Summary

Section titled “Summary”

The Automation Suite can reliably work with existing custom objects in your HubSpot portal, but creating brand-new custom object schemas is not currently a supported default path through the public OAuth app.

What works:

  • Sync existing custom objects
  • Query existing custom objects
  • Add properties to existing custom objects
  • Create and update records in existing custom objects

What is currently blocked:

  • Creating new custom object schemas through the app OAuth flow

Why

Section titled “Why”

Live HubSpot execution logs show that custom object schema creation still requires the granular scope crm.schemas.custom.write.

However, HubSpot rejects that same scope during app install or re-auth with:

The scope crm.schemas.custom.write could not be recognized.

This means the practical blocker is not normal portal re-auth drift. It is a HubSpot platform entitlement issue around requesting crm.schemas.custom.write from this app.

Product Position

Section titled “Product Position”

For now, the supported workflow is:

  1. Create the custom object stub manually in HubSpot.
  2. The Automation Suite extends and uses that object afterward.

This keeps things aligned with what HubSpot currently allows for the Daeda AI app.

What To Do When You Need A New Custom Object

Section titled “What To Do When You Need A New Custom Object”
  1. Create the custom object shell manually in HubSpot.
  2. Once the object exists, use the Automation Suite to:
    • add properties
    • create records
    • update records
    • build workflows, lists, and automation around that object

In plain English:

Create the custom object stub in HubSpot first. Once it exists, the Daeda AI Automation Suite can add fields, create records, and automate against it.

How The Automation Suite Behaves

Section titled “How The Automation Suite Behaves”

The Automation Suite treats custom object schema creation as a restricted path and prefers a clear workaround over a misleading scope failure. If you ask the AI to create a brand-new custom object schema, the Automation Suite will:

  • Fail fast on create_custom_object with a specific message
  • Explain that existing custom objects are fully supported
  • Direct you to create the object shell manually first

Evidence

Section titled “Evidence”

Observed in live testing:

  • Existing custom object property creation succeeded
  • Existing custom object record creation path validated successfully
  • New custom object schema creation failed at execution time with requiredGranularScopes: ["crm.schemas.custom.write"]
  • Re-auth failed because HubSpot said crm.schemas.custom.write was not recognised

Revisit Trigger

Section titled “Revisit Trigger”

Revisit this guidance if any of the following become true:

  • HubSpot enables crm.schemas.custom.write for the app or developer account
  • HubSpot publishes a stable public path for custom object schema creation from project/public apps
  • We add a separate supported private-app or admin credential path for schema creation